Best use case
Skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using Skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cli/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Skill Compares
| Feature / Agent | Skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
 ## `ctx skill` Manage reusable instruction bundles that can be installed into `.context/skills/`. A skill is a directory containing a `SKILL.md` file with YAML frontmatter (`name`, `description`) and a Markdown instruction body. Skills are loaded by the agent context packet when `--skill <name>` is passed to `ctx agent`. ```bash ctx skill <subcommand> ``` ### `ctx skill install` Install a skill from a source directory. ```bash ctx skill install <source> ``` **Arguments**: - `source`: Path to a directory containing `SKILL.md` **Examples**: ```bash ctx skill install ./my-skills/code-review # Installed code-review → .context/skills/code-review ``` ### `ctx skill list` List all installed skills. **Examples**: ```bash ctx skill list ``` ### `ctx skill remove` Remove an installed skill. **Arguments**: - `name`: Skill name to remove **Examples**: ```bash ctx skill remove code-review ``` **See also**: [Building Project Skills recipe](../recipes/building-skills.md).
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.