Skill Forge
When Claude discovers a non-obvious solution, unusual pattern, or hard-won insight during a session, automatically forge it into a new skill. Don't just note the learning - create the actual skill file so future sessions benefit immediately. This is the flywheel: work → discovery → skill → smarter future sessions → repeat.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill skill-forgegit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/skill-forge ~/.claude/skills/skill-forgePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill Forge <purpose> Knowledge that stays in one session is wasted. When Claude discovers something non-obvious - a debugging technique, a gotcha, a pattern that works - it should become a skill automatically. Not "maybe document this later" but "forge it now." This is the flywheel that makes the skill library self-improving. </purpose> ## When To Activate Trigger when: - Claude solves a problem that took multiple attempts - Claude discovers a non-obvious pattern or gotcha - A debugging session reveals something others would hit - User says "we should remember this" or "make this a skill" - Claude catches itself about to make a mistake it's made before - A workaround is found for a tool/library limitation - The solution was counter-intuitive Do NOT trigger for: - Obvious solutions anyone would find - Project-specific knowledge (not generalizable) - Things already covered by existing skills - Minor learnings not worth the overhead ## Instructions ### Step 1: Identify the Insight Capture what was learned: ``` Discovery: [One sentence summary] Context: [What task/problem led to this] Why non-obvious: [Why someone else would miss this] Generalizable: [YES/NO - is this useful beyond this specific case?] ``` If not generalizable, stop - add to breadcrumbs instead, not a skill. ### Step 2: Extract the Pattern Generalize from the specific case:
Details
- Skill name
skill-forge- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/skill-forge/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Skill Forge skill do?
When Claude discovers a non-obvious solution, unusual pattern, or hard-won insight during a session, automatically forge it into a new skill. Don't just note the learning - create the actual skill file so future sessions benefit immediately. This is the flywheel: work → discovery → skill → smarter future sessions → repeat.
How do I install the Skill Forge skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill skill-forge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Skill Forge popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Continuous Learning V2
32joneqian/claude-skills-suite
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
Learn From This
62ElliotJLT/Claude-Skill-Potions
When a session contains a significant failure, misunderstanding, or repeated mistake, analyse the root cause and draft a new skill that would have prevented it. The skill library should grow from real failures, not hypothetical improvements. Every painful debugging session is a skill waiting to be written.
Learn
51aviz85/claude-skills-library
Teach Claude ANY topic - code libraries, APIs, concepts, tools, methodologies, or domains. Researches via web and docs, then retains knowledge as a permanent skill. Use when user says "/learn <topic>", "learn about X", "teach yourself Y", "become an expert on Z". Examples - "/learn stripe" for payments, "/learn GTD" for productivity, "/learn israeli-tax-law" for domain knowledge.
Browse the most popular Claude skills, all learning & education skills, or write your own with the skills generator.