gsd-skill-creator

Why use it

Key features

Six-step adaptive cycle: observe, detect, suggest, apply, learn, compose
3-repetition threshold before suggesting a skill — avoids noise
Learning guardrails: 3-correction minimum, 7-day cooldown
GSD-OS desktop app (Tauri, retro UI) for managing the framework
Chipset architecture for resource coordination (Amiga-inspired)

Live Demo

What it looks like in practice

gsd-skill-creator-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use gsd-skill-creator

Let GSD detect your repeating workflow and codify it as a skill

👤 Heavy Claude Code users who keep redoing the same steps ⏱ ~30 min intermediate

When to use: You've done 'clone repo -> run tests -> fix lint -> open PR' enough times that muscle memory should be code.

Flow

Run with observation mode on

Enable gsd-skill-creator in observe mode. Run my normal PR flow a few times over the next week.✓ Copied

→ Silent logging of tool sequences
Review suggestions

Show me detected patterns with 3+ occurrences, ranked by confidence.✓ Copied

→ Ranked list with proposed skill names

Outcome: Your actual workflow becomes a reusable skill, grounded in data.

Pitfalls

Approving every suggestion — Promote only the top 1–2 — skill bloat hurts the picker

Combine with: skill-forge-skill

Compose co-activating skills into an agent team

👤 Engineers whose skills consistently fire together ⏱ ~30 min advanced

When to use: After a month of use, the skill picker keeps selecting the same 3 skills in sequence.

Flow

Review co-activation report

Show skill co-activation report — which skills fire within the same task 80%+ of the time?✓ Copied

→ Cluster diagram
Compose team

Compose the top cluster into a named agent team.✓ Copied

→ Team definition that orchestrates the cluster

Outcome: A higher-level orchestrator that triggers the full cluster in one shot.

Resume a long project without repeating old mistakes

👤 Teams doing multi-week Claude-driven work ⏱ ~15 min beginner

When to use: You're picking up a project Claude has lost context on.

Flow

Resume with skill history

Resume project X using gsd-skill-creator memory — what patterns and corrections have I applied so far?✓ Copied

→ Summary of prior skills and corrections

Outcome: Claude starts where it left off, not from zero.

Combine with: planning-with-files-skill

Combinations

Pair with other MCPs for X10 leverage

gsd-skill-creator-skill + skill-forge-skill

GSD detects the pattern; skill-forge scaffolds the formal skill

Hand the top detected pattern to skill-forge build for proper structure.✓ Copied

gsd-skill-creator-skill + planning-with-files-skill

GSD observes sessions; planning-with-files persists state across them

Use both — GSD for pattern learning, planning-with-files for session state.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
observe_start	session id or none	Start of the adoption period
detect_patterns	min_occurrences?	Weekly review
promote_to_skill	pattern id, name	After user approval
compose_team	cluster id	When clusters are stable
learn_from_correction	correction context	After 3+ corrections in cooldown window

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Observation is cheap; generation phases are moderate
Monetary: Free, BSL 1.1 (converts to GPL 3.0 in 2030)
Tip: Only run detection weekly, not per-session

Security

Permissions, secrets, blast radius

Credential storage: Observation data is local

Data egress: None by default

Troubleshooting

Common errors and fixes

No patterns detected after weeks of use

Your sessions may vary too much; loosen the pattern-matching threshold

GSD-OS desktop app won't launch

Rebuild Tauri bundle for your platform; check Rust toolchain

Verify: cargo --version

Alternatives