Loading...
Loading...
Found 12,075 Skills
Use when the user wants an agent to explore an unfamiliar repository, synthesize candidate work, ask structured direction questions, generate a bounded Claude Code /goal or equivalent implementation goal, or safely prepare a doctrine-gated autonomous request.
Turn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.
Organize, desensitize, and report GitHub bugs for chengfeng-videocut. Use this when the user requests to report a bug, provide feedback on clip voiceover issues, submit a GitHub Issue, inform developers about the problem, or request to continue submitting a pre-viewed bug draft. Do not use it for feature suggestions, general troubleshooting, code submissions, or automatic reporting without user confirmation.
Burn the edited voiceover into a final video file: integrate edit segments (from ledger), zoom-ins, subtitles, and HTML visual layers into an MP4 file in one go. This is to be used when the user requests actions such as export, final video generation, subtitle burning, rendering, video export, or final file creation. Do NOT use it for generating word deletion candidates, creating subtitles, or making visual animations.
Compare this fork with its upstream and merge upstream in. Use when the user asks whether upstream has changes, wants the upstream diff reviewed, or wants upstream merged into the fork.
When the user struggles with a task that a known skill could handle, suggest installing it.
Create or edit a provenance-safe visual skin for an existing validated Peekling pack while preserving all behavior, geometry, states, timing, mapping, and locomotion. Use only when a legal derivative base exists, and route identity, shape, or behavior changes to create-peekling-character.
Add or refine complete animation states for an existing original or licensed Peekling character while preserving identity and compiling valid timing/mapping. Use for motion/state work, not surface-only skins.
Prepare and dry-run a validated Peekling pack release, metadata, files, provenance, licence, and npm tarball. Actual publish, push, remote, account, or registry mutation requires fresh explicit authorization immediately before it.
Auto-categorize uncategorized transactions using vendor pattern matching.
Use when the user wants to make a GitHub pull request mergeable, resolve PR review comments, failing checks, merge conflicts, or update a branch from main. Invoke as /fix-pr [PR_NUMBER] [--auto].
Design a prospective Scientific Map and scientific architecture before implementation; target code stays read-only.