Comments
Code comments and annotations
ponytail
by 8-Sync-Dev
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
pitwall
by laneworkapp
Pitwall — a live watch on one Lanework board: arm a persistent Monitor on the board's files, wake on every change, respond to the owner's new comments, and farm action-calling comments out to model-tiered subagents, until the user says stop. Use this skill whenever the user asks to watch a Lanework board, watch a board for changes, respond to board comments live, "sit on the board", "man the pitwall", or wants this session to react to comments as they arrive — even if they don't name the skill. Not for one-shot board sweeps or filing cards (that's the pitlane skill; pitwall is the standing watch).
conductor
by medTech-group
Run an unattended build run - ask the owner the run charter's questions once, then hand each ready ticket to its own cloud session, check in on a schedule, keep PRs moving to merge, release as the charter allows, and write the final report. Also resumes or stops a run. Use for "run the backlog unattended", "work over the weekend", "conductor resume", "stop the run".
fire-patterns
by vanman2024
Auto-generated CLI patterns using Google Fire with class-based structure, docstring parsing, and nested classes. Use when building Python CLI applications, creating Fire CLIs, implementing auto-generated commands, designing class-based CLIs, or when user mentions Fire, Google Fire, CLI generation, docstring commands, nested command groups, or Python command-line tools.
github-code-review
by polarfruit
Comprehensive GitHub code review with AI-powered swarm coordination
observational-reframe
by sethmblack
Transform political, social, or cultural observations into Trevor Noah-style comedy by applying the outsider's lens to reveal inherent absurdities and contradictions.
music-processing-skills
by TommyDucx
批量下载高品质FLAC音乐（GD音乐台多音源），自动按音乐风格分文件夹管理， 并为每首歌内嵌完整元数据（歌名、歌手、专辑、风格、年份、歌词）的完整工作流。 当用户要求「下载歌曲」「批量下载音乐」「整理音乐库」「内嵌元数据」「给歌曲加歌词/信息」时使用。
ratios
by The-Interdependency
"Self-declaring module composition ratios on msdmd — a single comment line on a file's first and last line (never a fenced block). The canonical seal is The-Interdependency/a0's compact positional N:M C:D I:O annotation (code:comment · consumed:declared · fan-in:fan-out), computed by a0's scripts/annotate.py; the named loc_comments=… imports_exports=… calls_definitions=… line is a portable, per-file adaptation for standalone libraries, verified by the stdlib ratios_check.py (drift/misplacement failures, visible gaps). JSON/Markdown are out of scope. Load this when recording a module's composition ratios, when authoring or extending the ratio registry, or when wiring ratio verification into CI."
project-conventions
by ddaanet
Project prose and output conventions for sub-agents. Injected via skills: frontmatter — not user-invocable. Bundles deslop (prose quality), token economy, and tmp-directory rules.
prompt-queue
by 011matthias
Queue prompts to run after the current task. Append prompts to .claude/queue/pending.md while a chat is busy; when invoked, the agent drains the queue FIFO (one prompt at a time), records each in done.md, then stops. Use for "queue this prompt", "add to the queue", "drain the queue", "run my queued prompts", "queue mode".
ticket-lifecycle
by nullvoidundefined
Use to open, advance, close, or report on the external tracker ticket (Jira, Notion, or Asana) that tracks a task. Triggers at task classification, at every state change in the work, at task close, and on "what did I ship this week" or "how long does this tier take".
loom-doctor
by rjwalters
"Addresses review feedback on PRs labeled loom:changes-requested"
poc-builder
by SRIKANTHBHAGYANAGARAJ
"Go from zero to a working POC with any Snowflake guide, blog post, doc link, social post, GitHub repo, or topic name. Deep-dives the content, extracts a full demo spec, finds matching data in your account, and builds a working POC interactively. Use when: poc builder, build this, build a poc, zero to poc, try this, teach me, walk me through, prototype this, implement this guide, follow along, run this guide, quickstart guide."
implement-isolation-tmux
by SjB
"Dispatch a child agent in an isolated git worktree to implement a piece of work based on a PRD or set of issues."
file-generator-issue
by specfuse
"File a GitHub issue against the Specfuse generator repo for a code-generation bug, then start a background monitor that polls for resolution and auto-verifies the fix when the generator agent resolves it. Use when generated code is wrong and you need to report the symptom (never propose template fixes) and resume work once fixed; supports a --verify-only mode."
github-code-review
by niyatna
"Review PRs: diffs, inline comments via gh or REST."
storyboard-creation
by nachopalmeri
"Film and video storyboarding with shot vocabulary, continuity rules, and panel layout. Covers shot types, camera angles, movement, 180-degree rule, and annotation format. Use for: video planning, film pre-production, ad storyboards, music video planning, animation. Triggers: storyboard, storyboarding, shot list, film planning, video planning, pre production, shot composition, camera angles, scene planning, visual script, animatic, storyboard panels, video storyboard"
issue-create
by terrylica
Create well-formatted GitHub issues with intelligent AI-powered label suggestions and content type detection. Use whenever the user wants to.
sync-project
by spacedock-dev
Use when reconciling Cargento's Linear project, milestone and issue surfaces after a merge, before picking work, or whenever a tracker description has grown past what a reader needs to act.
run-team
by feigi
Run an agent fleet — implementers, reviewers (default 2 and 6), one merge bot — over the ready-for-agent queue. Invoke-only; the fleet writes to a live repo and must never start unasked.
mechanisms
by nitedani
"Using or fixing the mechanisms that enforce the rules: the watcher, the hooks, gate-pass, post-lint, pr-steps."
learning-docker
by dvdksn
Load automatically when user asks to learn Docker (e.g., "teach me docker", "guide me through docker", "I want to learn docker", "docker tutorial"). Interactive guided tutorial where Claude acts as a coding bootcamp instructor, teaching step-by-step with checkpoints and verification.
docx
by thiguchi125-debug
"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers Claude's own dedicated document or page skill or connector, use that instead, even if they will email or print it. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation."
Skill: Furnace Agent — SKILL.md (agent-customization)
by Tucan4U
(Comments: This SKILL.md is workspace-scoped and written to be concise; it instructs contributors to include short, descriptive comments in code according to coding principles.)