# Gentle AI Skill Creator

Trigger: /skill-creation, skill creation, skill creator, create skill, new skill.

- Repository: https://github.com/Gentleman-Programming/gentle-shell (1519 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-skill-creator -g -a claude-code -y`
Codex: `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-skill-creator -g -a codex -y`
Cursor: `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-skill-creator -g -a cursor -y`
Gemini CLI: `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-skill-creator -g -a gemini-cli -y`

## Description

Trigger: /skill-creation, skill creation, skill creator, create skill, new skill. Create LLM-first skills with valid frontmatter.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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.md` as the normative source for skill structure and style.
- A skill is an LLM runtime contract, not human-facing docs.
- Keep `SKILL.md` concise: target 180, 450 tokens, max 1000.
- Use imperative instructions and concrete gates; avoid tutorials and background prose.
- Frontmatter `description` must be one physical YAML-safe line and include trigger words first.
- Do not add a `Keywords` section; put essential trigger words in `description`.
- 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:refresh` when 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

1. Read `docs/skill-style-guide.md` before creating or updating skills.
2. Inspect existing skills and confirm the new skill does not duplicate one.
3. Choose a kebab-case skill name that matches the user-facing trigger.
4. Create or update this structure:

The rest: https://github.com/Gentleman-Programming/gentle-shell/blob/HEAD/skills/skill-creator/SKILL.md