Create, validate, and publish a new skill in one pipeline.
When you have an idea for a skill and want to take it from concept to published capability, skill-launch orchestrates the entire workflow. It drafts the skill with Draft-Skill (confirming purpose, checking siblings, writing structure), validates and tunes it with Tune-Skill (fixing triggers, resolving overlaps, validating with check_skill.py), then audits discoverability and polishes it with Findable-Polish (improving SEO, refining descriptions). You get a production-ready skill with all three phases handled sequentially.
/skill-launch "I want a skill that checks if my code is production-ready"
/skill-launch "a skill that turns support tickets into release notes"
Create a skill that audits repos before deployment.
- You have an idea for a skill and want to build it completely
- (If you have a batch of prompts instead of an idea, that is prompts-to-skill's job.)
- Someone says "make me a skill for X" and you want it done end-to-end
- You want triggering, validation, and discoverability all handled
- You're creating multiple skills and want a consistent pipeline
- You need a skill that's ready to publish without manual cleanup
- A drafted SKILL.md with correct frontmatter and structure (from Draft-Skill)
- Validated triggers and resolved sibling overlaps (from Tune-Skill)
- check_skill.py validation (FAIL/WARN/PASS)
- Polished descriptions and improved discoverability (from Findable-Polish)
- A production-ready skill folder ready to commit and push
npx skills add arm-pz/skill-launchRequires draft-skill, tune-skill, findable-polish (which needs findable + wordsmith) to be installed.
- Editing existing skills → use tune-and-polish
- Just drafting without polishing → use draft-skill alone
- draft-skill — Create skills from ideas (phase 1)
- tune-skill — Validate and fix triggers (phase 2)
- findable-polish — Audit and polish discoverability (phase 3)
- tune-and-polish — Tune + polish existing skills
MIT © Abdul Rahman P Z