ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
Best use case
ctx-skill-creator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
Teams using ctx-skill-creator 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-skill-creator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-skill-creator Compares
| Feature / Agent | ctx-skill-creator | 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?
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
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
Create new skills or improve existing ones through a structured
workflow.
## When to Use
- Creating a new skill from scratch
- Improving an underperforming skill
- Porting a skill from one integration to another
## When NOT to Use
- Quick one-off automations (just script it)
- When the need is too vague (brainstorm first)
## Process
### 1. Intent capture
Gather:
- What should this skill do?
- When should it trigger?
- What tools does it need?
- What's the expected output?
### 2. Draft the SKILL.md
Use the standard structure:
```yaml
---
name: ctx-{name}
description: "..."
tools: [bash, read, write, ...]
---
```
Sections: When to Use, When NOT to Use, Process, Quality Checklist.
### 3. Validate
Check against skill audit dimensions:
- Positive framing
- Clear scope
- Good examples
- No phantom references
- Overtriggering guard
### 4. Test
If possible, do a dry run of the skill's workflow to verify
it works end-to-end.
### 5. Deploy
Write the file to the appropriate skills directory:
- Claude: `internal/assets/claude/skills/{name}/SKILL.md`
- Copilot CLI: `internal/assets/integrations/copilot-cli/skills/{name}/SKILL.md`
### 6. Build
Run `go build ./cmd/ctx/...` to verify the embed compiles.
## Quality Checklist
- [ ] Frontmatter is complete (name, description, tools)
- [ ] When to Use / When NOT to Use sections exist
- [ ] Process has numbered, actionable steps
- [ ] Quality Checklist at the end
- [ ] No phantom references
- [ ] Build passes with new skill embeddedRelated Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
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.
ctx-add-convention
Record a coding convention. Use when a repeated pattern should be codified so all sessions follow it consistently.