From darkroom
Scaffolds new cc-settings skills by generating SKILL.md frontmatter and body, registering in setup.ts and MANUAL.md, and running validation tests. Triggers on 'create a skill' prompts.
npx claudepluginhub darkroomengineering/cc-settingsThis skill uses the workspace's default tool permissions.
cc-settings has 38+ skills. The native `Skill` tool auto-invokes them based on the `description` frontmatter — so the description is **the only thing the agent sees** when deciding whether to load yours. That's where most of the work goes.
Guides creation of new Claude Code skills from scratch, covering SKILL.md anatomy, YAML frontmatter best practices, trigger phrases, and optional resources like scripts. Triggers on 'create a skill', 'new skill', 'scaffold skill'.
Guides development of Claude Code SKILL.md files with best practices, structure, YAML frontmatter rules, categories, patterns, references, and testing.
Guides creation or updating of skills extending Codex with specialized knowledge, workflows, and tool integrations. Use when building new or modifying existing skills.
Share bugs, ideas, or general feedback.
cc-settings has 38+ skills. The native Skill tool auto-invokes them based on the description frontmatter — so the description is the only thing the agent sees when deciding whether to load yours. That's where most of the work goes.
Gather requirements. Ask the user:
/fix, /build, /explore, /review, etc.)SKILL.md enough?bun "$HOME/.claude/src/scripts/<name>.ts".Draft the skill. Create skills/<name>/SKILL.md. Match the cc-settings convention:
---
name: skill-name
description: |
Use when:
- User says "<phrase 1>", "<phrase 2>"
- <situational trigger>
- <another trigger>
<One-paragraph summary of what the skill does, what it produces,
and how it relates to other cc-settings skills.>
---
# skill-name
<Body — see structure below>
Register it. Add "<name>" to MANAGED_SKILLS in src/setup.ts (alphabetical order).
Document it. Add a row to MANUAL.md in the appropriate section (Daily Workflows / Quality / Planning / Maintenance / etc.) and the "All Skills" table at the bottom.
Validate. bun test && bun run typecheck. Tests should still pass — the schemas in src/schemas/skill.ts validate frontmatter shape.
name — kebab-case. Must match the directory name.description — multi-line description: | block. The cc-settings convention starts with bullet Use when: triggers and ends with a one-paragraph summary.Match the existing skills (skills/fix/SKILL.md, skills/cc-sync/SKILL.md, skills/consolidate/SKILL.md are good models):
## Phase 1 — …) for multi-step workflows.Split content across additional files in the skill's directory only when:
SKILL.md exceeds ~150 lines and has distinct sub-domainsCONTEXT-FORMAT.md, ADR-FORMAT.md)DOMAIN-AWARENESS.md)Reference from SKILL.md with a relative link: [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).
Add a TypeScript helper in src/scripts/ when:
Reference from the skill: bun "$HOME/.claude/src/scripts/<name>.ts".
Before committing:
description includes specific Use when: triggersbun testMANAGED_SKILLS (alphabetical)