skill-designer
- Repo stars 1,568
- Author updated Live
- Author repo claude-trading-skills
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tradermonty · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python >=3.9
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-designer
description: Design new Claude skills from structured idea specifications. Use when the skill auto-generation…
category: design
runtime: Python
---
# skill-designer output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / When to Use / Prerequisites” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Overview / When to Use / Prerequisites” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/tmp`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Overview / When to Use / Prerequisites”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-designer
description: Design new Claude skills from structured idea specifications. Use when the skill auto-generation…
category: design
source: tradermonty/claude-trading-skills
---
# skill-designer
## When to use
- Design new Claude skills from structured idea specifications. Use when the skill auto-generation pipeline needs to pro…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / When to Use / Prerequisites” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-designer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / When to Use / Prerequisites
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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 namedescription: What the skill doescategory: 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:
python3 skills/skill-designer/scripts/build_design_prompt.py \
--idea-json /tmp/idea.json \
--skill-name "my-new-skill" \
--project-root .The script:
- Loads the idea JSON
- Reads all three reference files (structure guide, quality checklist, template)
- Lists existing skills (up to 20) to prevent duplication
- Outputs a complete prompt to stdout
Step 3: Feed Prompt to Claude CLI
The calling pipeline pipes the prompt into claude -p:
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,GrepStep 4: Validate Output
After Claude creates the skill, verify:
skills/<skill-name>/SKILL.mdexists 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 conventionsreferences/quality-checklist.md-- Dual-axis reviewer 5-category checklist (100 points)references/skill-template.md-- SKILL.md template with YAML frontmatter and standard sectionsscripts/build_design_prompt.py-- Prompt builder script (CLI interface)
Decide Fit First
Design Intent
How To Use It
Boundaries And Review