skill-forge

왜 쓰나요

핵심 기능

5-stage workflow: plan, build, review, evolve, publish
0-100 health score across 6 quality categories
Four tiers: single-file, multi-file, agent-assisted, enterprise
3-layer architecture: Directive + Orchestration + Execution
Packages to .skill archives with install scripts

라이브 데모

실제 사용 모습

skill-forge-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: skill-forge

Go from idea to published skill in one session

👤 Developers who keep copy-pasting the same prompt and want to ship it as a reusable skill ⏱ ~90 min intermediate

언제 쓸까: You have a workflow you repeat (e.g. code review, PR description writing) and want it automated into a skill.

흐름

Plan

/skill-forge plan — I want a skill that does structured code review comments on PRs. Use cases, sub-skills, I/O.✓ 복사됨

→ Architecture with sub-skills enumerated
Build

/skill-forge build code-review-commenter — scaffold the tree per the plan.✓ 복사됨

→ SKILL.md + sub-files generated
Review

/skill-forge review code-review-commenter — give me the 100-point audit.✓ 복사됨

→ Score + findings per category
Evolve + publish

Fix each finding then /skill-forge publish — make a .skill archive.✓ 복사됨

→ Installable archive

결과: A shippable skill in your skills directory that passes the audit.

함정

Over-scoping — trying to make a monster skill — Start at tier 1 (single-file). Promote tiers only when real needs push you there

함께 쓰기: filesystem · github

Audit and improve a skill someone else wrote

👤 Platform engineers curating an internal skills library ⏱ ~45 min beginner

언제 쓸까: You inherited a skill and want to know if it meets the bar.

흐름

Run the audit

/skill-forge review path/to/skill — give me the scorecard and top 5 issues.✓ 복사됨

→ Score + prioritized fix list
Evolve

/skill-forge evolve — fix the top 5 findings and re-score.✓ 복사됨

→ Higher score, changelog

결과: An upgraded skill with measurable quality improvement.

Design a coordinated pack of skills for a domain

👤 Teams standardizing how AI agents work in their domain ⏱ ~180 min advanced

언제 쓸까: You need 5–10 related skills that hand off cleanly to each other.

흐름

Plan ecosystem

/skill-forge plan domain=customer-support — design 6 coordinated skills with clear hand-off boundaries.✓ 복사됨

→ Diagram + per-skill spec
Build in parallel

/skill-forge build — all 6 skills, same sprint.✓ 복사됨

→ Skills generated with shared conventions

결과: A consistent pack rather than a collection of mismatched skills.

함정

Duplicating capabilities across skills — The plan step detects overlap — revisit if flagged

조합

다른 MCP와 조합해 10배 효율

skill-forge-skill + filesystem

Edit the generated skill files directly in the same session

After /skill-forge build, hand-edit the SKILL.md tone — the filesystem skill keeps Claude editing in-place.✓ 복사됨

skill-forge-skill + github

Publish skill to a public GitHub repo for distribution

Publish and push the .skill archive to a new GitHub release.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
/skill-forge plan	domain or use case	Start of any new skill project
/skill-forge build	skill name (+ plan)	After plan is approved
/skill-forge review	skill path	After any significant change
/skill-forge evolve	findings to fix	Improvement loop
/skill-forge publish	skill path	Ready to ship

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Large — scaffolding and review are token-heavy (15–40k per phase)
금액: Free
팁: Plan in a cheap model, then switch to Opus for build and review

보안

권한, 시크릿, 파급범위

자격 증명 저장: None in the skill itself

데이터 외부 송신: None

Generated skills are your responsibility — run the review step before shipping and never auto-publish without human sign-off.

문제 해결

자주 발생하는 오류와 해결

Review score stays low despite fixes

Read the findings carefully — some are structural (tier mismatch) and need redesign, not patching

대안

skill-forge 다른 것과 비교

대안	언제 쓰나	단점/장점
gsd-skill-creator	You want skills to be auto-suggested from observed patterns	More framework, higher learning curve
Hand-authoring SKILL.md	Single, simple skill you understand fully	No review layer, easy to miss conventions