Comments
Code comments and annotations
no-type-in-docs
by marius-townhouse
Use when writing comments about types. Use when documenting function parameters. Use when naming variables.
turn-this-feature-into-a-blog-post
by GhostScientist
Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".
liquidity-and-price-dynamics-explainer
by SanctifiedOps
Explain Solana AMM liquidity, slippage, volatility, and LP mechanics for tokens. Use to brief teams or design initial liquidity.
commit
by trancong12102
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages. Triggers on phrases like 'commit', 'commit and push', 'make a commit', 'git commit', or when commit is part of a compound action (e.g., 'bump version and commit').
brainstorming
by trancong12102
"Collaboratively explore ideas and design solutions through guided dialogue before implementation. Use this skill when creating features, building components, adding functionality, designing systems, or when the user says \"brainstorm\", \"design this\", \"help me think through\", or \"let's plan\"."
SKILL.md — Paper2Protocol Skill Definition
by ChrisLou-bioinfo
🦞 Claw (AI Research Assistant)
avoid-inferable-annotations
by marius-townhouse
Use when writing type annotations on variables. Use when TypeScript can infer the type. Use when code feels cluttered with types.
database-indexing
by 1Mangesh1
Database indexing strategies and query optimization. Use when user asks to "optimize queries", "create indexes", "database performance", "query analysis", "explain plans", "index selection", "slow queries", "database tuning", "schema optimization", or mentions database performance and query optimization.
writing-docs
by C0ntr0lledCha0s
Expert at writing high-quality documentation for code, APIs, and projects. Auto-invokes when generating docstrings, creating README files, writing API documentation, adding code comments, or producing any technical documentation. Provides language-specific templates and best practices for effective documentation writing.
evolving-types
by marius-townhouse
Use when types change as code executes. Use when arrays are built incrementally. Use when working with any[] that narrows.
unslop
by HugoRCD
Remove AI-generated "slop" from codebases by deleting redundant comments and unused code, tightening formatting, and normalizing styling patterns (e.g., Tailwind class consistency, Nuxt UI color tokens). Use when a user asks to clean up code, remove unnecessary comments, reduce unused imports/variables, or align Tailwind/Nuxt UI conventions.
coco-workspace
by zylos-ai
COCO Workspace 任务代理 (Guided Autonomy)。凡通过 coco-workspace 收到的用户消息， 处理任务前必须先加载并遵守本 skill：先判断是任务还是问话/闲聊；是任务则必须走完整流程—— 确认归属项目 + 知识库 → 登记 Issue→Task（谁执行谁建，Issue owner=发起人）→ 执行 → owner 发起人验收通过才算完成/归档， 不要跳过流程直接开干。含效率捷径 / 状态机 / 行为护栏 / 记忆触发点。 Config at ~/zylos/components/coco-workspace/config.json. Service: pm2 zylos-coco-workspace.
review-pr
by corygabrielsen
Thorough, educational PR review process. Gathers context, explains changes, identifies issues systematically, and drafts constructive feedback collaboratively before submitting.
python-guidelines
by viktor-ferenczi
Guiding principles for writing clear, concise, human readable and maintainable Python code.
terraform-aws-annotated-blueprint
by Donngi
全プロパティに詳細な解説が付いたTerraform AWSテンプレートを作成する。ユーザーが「/terraform-annotated-aws-blueprint」コマンドで構築したいインフラの概要を入力すると、Terraform Providerスキーマに基づいた正確な属性一覧と、AWS公式ドキュメントに基づく解説を含むテンプレートを生成する。
ocean-paper-writer
by 441837297
helps ocean science researchers turn proposals, figures, code, data descriptions, target-journal plans, Zotero-supported literature, and advisor feedback into staged manuscript materials through prepare, methods, structure, writing, review, and polish workflows.
pr-review-loop
by xpepper
Use when addressing open PR review comments from any reviewer (human or bot) within the current agent session. For a fresh-context-per-comment approach, use ralph-wiggum-loop instead.
terraform-aws-annotated-reference
by Donngi
単一のTerraform AWSリソースに対する全プロパティ解説付きリファレンステンプレートを生成する。ユーザーがリソース名（例：aws_s3_bucket, aws_lambda_function）を指定すると、Providerスキーマに基づいた正確な属性一覧とAWS公式ドキュメントに基づく解説を含むテンプレートを出力する。「aws_xxxのテンプレートを作成して」「aws_xxxの全プロパティを教えて」などのリクエストで使用。
git-commits
by octivi
Draft, rewrite, and review Git commit messages using Conventional Commits and commit hygiene rules. Use whenever the user asks for commit text, commit message fixes, type/scope selection, breaking-change notation, trailers (for example See or Co-authored-by), splitting work into atomic commits, or commit readiness before a PR, even if they ask in informal terms like "polish this commit message".
agentic-cadence
by Chef-Code
Manage durable agent handoffs, Cadence state, pickup signatures, and clean-square shutdowns for long-running or self-evolving workflows.
skill-name
by feed-mob
A clear, complete description of what this skill does and when Claude should use it
jira-worklog
by krzysztofkrolikowski
Generate bash scripts for bulk logging work hours to Jira. Use when user asks to log hours, create worklog script, or automate Jira time tracking for a specific month. Handles task discovery via JQL, existing worklog detection, hour distribution, skip days (holidays/vacation), and API authentication.
deepwiki
by lambda610
"AI-powered local codebase documentation generator. Use for: (1) Deep code analysis with business logic extraction, (2) Comprehensive API documentation with signatures, (3) Architecture diagrams and data flow mapping, (4) Code patterns identification and design decisions. Not for: Simple file listings or code comments only."
pdd
by dtinth
'Skills for Puzzle Driven Development (PDD). Refer to this skill when a project uses PDD or the operator mentions PDD or puzzle-driven development. Use this skill when: (1) Breaking a large feature into incremental deliverables, (2) Writing @todo stub comments to mark unimplemented code, (3) Picking up an existing @todo puzzle to implement, (4) Deciding whether to wrap up a task with a stub or keep working.'