Loading...
Loading...
Found 2,038 Skills
Skill for researching best practices. Triggered when you need to understand methodologies, tools, and best practices in a specific field. Trigger words: research, learn about, what methods are there, best practices.
Read Codex logs for this repo and synthesize docs in docs/.
This is a skill to check whether the content of CHANGELOG.md in a framework intended for external release is appropriate. It is used when updating or reviewing CHANGELOG.md.
Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.
Create or update repository README.md files with concise, human-skimmable structure and verified metadata. Use when writing or refreshing README content, adding or correcting badges, documenting stack and deployment/services, and explicitly reporting testing coverage (unit, integration, e2e api, e2e web) plus CI execution status.
Close a PRD that is already implemented or no longer needed
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Write, audit, and improve AGENTS.md files for AI coding agents. Use when creating or improving agent context for a codebase.
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
Help users organize weekly reports, presenting work value and boundaries in a complete logical manner. Triggered when users say "write weekly report", "weekly report", "organize weekly report", or "sort out work".
Datadog docs lookup using docs.datadoghq.com/llms.txt and linked Markdown pages.
Elevate a working PR: hindsight review, refactor, simplify, test audit, docs, quality gates. Composes: hindsight-reviewer agent, /refactor, /simplify, /update-docs, /check-quality, /distill. Use when: PR works but could be better. "How would we do this knowing what we know now?"