Context
There is no scaffolding command. Users manually create directories, write frontmatter, add sections. The prescriber (src/prescriber.ts) already knows the recommended structure per skill type, but this knowledge is only used for fixing existing skills.
Proposed
pulser init my-skill --type analysis
Generates:
~/.claude/skills/my-skill/
SKILL.md # Valid frontmatter + Gotchas + structure
eval.yaml # Test skeleton
What to do
- Add
init subcommand in src/index.ts
- Create
src/init.ts with template logic
- Reuse constants from
src/prescriber.ts (RECOMMENDED_TOOLS, GOTCHAS_TEMPLATES) to generate valid SKILL.md per type
- Accept
--type flag (analysis, research, generation, execution, reference) or prompt for it
- Generate an
eval.yaml skeleton with one example test
Why this matters
The recommended workflow is: create skill → run pulser → fix issues. But step 1 has zero tooling. This closes the loop.
Files to modify
src/index.ts (subcommand)
- New:
src/init.ts
- Reuse:
src/prescriber.ts constants
Difficulty: Medium-Hard
Context
There is no scaffolding command. Users manually create directories, write frontmatter, add sections. The prescriber (
src/prescriber.ts) already knows the recommended structure per skill type, but this knowledge is only used for fixing existing skills.Proposed
Generates:
What to do
initsubcommand insrc/index.tssrc/init.tswith template logicsrc/prescriber.ts(RECOMMENDED_TOOLS, GOTCHAS_TEMPLATES) to generate valid SKILL.md per type--typeflag (analysis, research, generation, execution, reference) or prompt for iteval.yamlskeleton with one example testWhy this matters
The recommended workflow is: create skill → run pulser → fix issues. But step 1 has zero tooling. This closes the loop.
Files to modify
src/index.ts(subcommand)src/init.tssrc/prescriber.tsconstantsDifficulty: Medium-Hard