← ClaudeAtlas

skill-creatorlisted

Interactively scaffold new Claude Code skills with correct frontmatter, trigger clauses, sub-files, and linter compliance. TRIGGER when: user asks to create a new skill, scaffold a skill, add a skill to agent-skills, or says "new skill" or "skill creator". DO NOT TRIGGER when: user is editing an existing skill, writing CLAUDE.md instructions, or building an MCP server (use mcp-server-builder skill).
DROOdotFOO/agent-skills · ★ 1 · AI & Automation · score 75
Install: claude install-skill DROOdotFOO/agent-skills
# Skill Creator Scaffold new Claude Code skills that pass `./scripts/skills-lint.sh` on the first try. Walk the user through naming, trigger design, sub-file structure, and quality review. ## What is a skill? A skill is a directory under `skills/<name>/` containing markdown files with YAML frontmatter. The entry point is always `SKILL.md`. Skills provide context-injection for Claude Code sessions -- they load automatically when trigger conditions in the description match the user's task. Skills are NOT agents, NOT plugins, NOT code libraries. They are structured knowledge documents that shape Claude's behavior for a specific domain. ## Scaffolding workflow ### Step 1: Choose a name - Lowercase, hyphenated: `my-skill-name` - Short but specific: prefer `database-designer` over `db` or `database-schema-design-and-optimization-tool` - Check for overlap with existing skills before creating ### Step 2: Write trigger clauses The description field in SKILL.md frontmatter MUST include both: - **TRIGGER when:** -- enumerate concrete conditions (imports, file types, user phrases) - **DO NOT TRIGGER when:** -- exclude adjacent domains to prevent false activation Good triggers are specific and observable: ``` TRIGGER when: user asks to design a REST API, define endpoint schemas, or working with OpenAPI spec files (.yaml/.json with openapi: field). DO NOT TRIGGER when: user is implementing API handlers (use the language-specific skill), or configuring an API gateway. ``` Bad t