
Gentle AI Skill Creator
Trigger: /skill-creation, skill creation, skill creator, create skill, new skill.
Install
npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-skill-creator -g -a claude-code -y- Repository
- Gentleman-Programming/gentle-shell1.5k
- Category
- AI and agents
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 732 tokens
- Runs scripts
- No, instructions only
What it does
Trigger: /skill-creation, skill creation, skill creator, create skill, new skill. Create LLM-first skills with valid frontmatter.
Activation Contract
Use this skill when creating or updating a reusable AI skill for Pi or another agent runtime.
Create a skill when:
- a workflow or convention is reused across sessions;
- generic agent behavior needs project-specific constraints;
- a decision tree helps the agent choose safely;
- examples, templates, or references would make future execution more reliable.
Do not create a skill for a one-off task, generic documentation, or rules that belong in code/tests.
Hard Rules
- Follow
docs/skill-style-guide.mdas the normative source for skill structure and style. - A skill is an LLM runtime contract, not human-facing docs.
- Keep
SKILL.mdconcise: target 180, 450 tokens, max 1000. - Use imperative instructions and concrete gates; avoid tutorials and background prose.
- Frontmatter
descriptionmust be one physical YAML-safe line and include trigger words first. - Do not add a
Keywordssection; put essential trigger words indescription. - Put templates, schemas, and generated examples in
assets/. - Put longer rationale or local doc links in
references/. - After changing project skills, refresh the registry with
/skill-registry:refreshwhen available.
Decision Gates
| Need | Action |
|---|---|
| Small reusable behavior | Create skills/{skill-name}/SKILL.md only |
| Templates, schemas, fixtures | Add skills/{skill-name}/assets/ |
| Longer explanation or edge cases | Add skills/{skill-name}/references/ |
| Existing skill covers it | Update the existing skill instead |
| Skill affects delegation discovery | Ensure trigger words appear in description |
Execution Steps
- Read
docs/skill-style-guide.mdbefore creating or updating skills. - Inspect existing skills and confirm the new skill does not duplicate one.
- Choose a kebab-case skill name that matches the user-facing trigger.
- Create or update this structure:

