Design new Claude skills from structured idea specifications. Use when the skill auto-generation pipeline needs to produce a Claude CLI prompt that creates a complete skill directory (SKILL.md, references, scripts, tests) following repository conventions.
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
What it does
Design new Claude skills from structured idea specifications
When to use it
- The skill auto-generation pipeline selects an idea from the backlog and needs
How agents load it
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Skill Designer; Overview; When to Use; Prerequisites; Workflow; Step 1: Prepare Idea Specification. It includes spec-recommended sections: step-by-step instructions.
File analysis
File analysis: besides SKILL.md, the body references scripts/build_design_prompt.py, references/skill-structure-guide.md, references/quality-checklist.md, references/skill-template.md. Those resources load on demand.
Skill DesignerOverviewWhen to UsePrerequisitesWorkflowStep 1: Prepare Idea SpecificationStep 2: Build Design PromptStep 3: Feed Prompt to Claude CLIStep 4: Validate OutputOutput FormatResources
Design new Claude skills from structured idea specifications. Use when the skill auto-generation pipeline needs to produce a Claude CLI prompt that creates a complete skill directory (SKILL.md, references, scripts, tests) following repository conventions.
DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
scripts/build_design_prompt.py
references/skill-structure-guide.md
references/quality-checklist.md
references/skill-template.md
These paths are extracted from the text. Check the upstream package to verify the files exist.
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Ask your Agent to install
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "skill-designer" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-5957e880860b8bdc-Skill-Designer.html
Save it as .cursor/skills/skill-designer/SKILL.md or .claude/skills/skill-designer/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/tradermonty/claude-trading-skills instead of creating only a SKILL.md.
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
---
name: skill-designer
description: Design new Claude skills from structured idea specifications. Use when the skill auto-generation pipeline needs to produce a Claude CLI prompt that creates a complete skill directory (SKILL.md, references, scripts, tests) following repository conventions.
---
# Skill Designer
## Overview
Generate a comprehensive Claude CLI prompt from a structured skill idea
specification. The prompt instructs Claude to create a complete skill directory
following repository conventions: SKILL.md with YAML frontmatter, reference
documents, helper scripts, and test scaffolding.
## When to Use
- The skill auto-generation pipeline selects an idea from the backlog and needs
a design prompt for `claude -p`
- A developer wants to bootstrap a new skill from a JSON idea specification
- Quality review of generated skills requires awareness of the scoring rubric
## Prerequisites
- Python 3.9+
- No external API keys required
- Reference files must exist under `references/`
## Workflow
### Step 1: Prepare Idea Specification
Accept a JSON file (`--idea-json`) containing:
- `title`: Human-readable idea name
- `description`: What the skill does
- `category`: Skill category (e.g., trading-analysis, developer-tooling)
Accept a normalized skill name (`--skill-name`) that will be used as the
directory name and YAML frontmatter `name:` field.
### Step 2: Build Design Prompt
Run the prompt builder:
```bash
python3 skills/skill-designer/scripts/build_design_prompt.py \
--idea-json /tmp/idea.json \
--skill-name "my-new-skill" \
--project-root .
```
The script:
1. Loads the idea JSON
2. Reads all three reference files (structure guide, quality checklist, template)
3. Lists existing skills (up to 20) to prevent duplication
4. Outputs a complete prompt to stdout
### Step 3: Feed Prompt to Claude CLI
The calling pipeline pipes the prompt into `claude -p`:
```bash
python3 skills/skill-designer/scripts/build_design_prompt.py \
--idea-json /tmp/idea.json \
--skill-name "my-new-skill" \
--project-root . \
| claude -p --allowedTools Read,Edit,Write,Glob,Grep
```
### Step 4: Validate Output
After Claude creates the skill, verify:
- `skills//SKILL.md` exists with correct frontmatter
- Directory structure follows conventions
- Score with dual-axis-skill-reviewer meets threshold
## Output Format
The script outputs a plain-text prompt to stdout. Exit code 0 on success,
1 if required reference files are missing.
## Resources
- `references/skill-structure-guide.md` -- Directory structure, SKILL.md format, naming conventions
- `references/quality-checklist.md` -- Dual-axis reviewer 5-category checklist (100 points)
- `references/skill-template.md` -- SKILL.md template with YAML frontmatter and standard sections
- `scripts/build_design_prompt.py` -- Prompt builder script (CLI interface)