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.
Best use case
ctx-prompt is best used when you need a repeatable AI agent workflow instead of a one-off 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.
Teams using ctx-prompt 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/ctx-prompt/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-prompt Compares
| Feature / Agent | ctx-prompt | 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?
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.
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.
Related Guides
SKILL.md Source
Apply reusable prompt templates from `.context/prompts/`. ## When to Use - User says "use the code-review prompt" or "apply the refactor template" - User asks to list, create, or manage prompt templates - User mentions "prompt template" or "reusable prompt" ## When NOT to Use - For structured context entries (use `ctx add` instead) - For full workflow automation (use a dedicated skill instead) - For scratchpad notes (use `ctx pad` instead) ## Command Mapping | User intent | Command | |----------------------------------|---------------------------------| | "list my prompts" | `ctx prompt list` | | "show the code-review prompt" | `ctx prompt show code-review` | | "create a new prompt" | `ctx prompt add <name> --stdin` | | "delete the debug prompt" | `ctx prompt rm debug` | ## Execution **When no name is given:** ```bash ctx prompt list ``` **When a name is given:** ```bash ctx prompt show <name> ``` Read the prompt content, then follow the instructions in the prompt applied to the user's current context. ## Quality Checklist - [ ] Used correct subcommand for user intent - [ ] Prompt content was applied, not just displayed - [ ] If prompt not found, suggested `ctx prompt list`
Related Skills
ctx-prompt-audit
Audit prompting patterns. Use periodically to help users improve prompt quality and reduce clarification cycles.
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-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.