Skill Forge
Every instruction your AI reads cites a file, a line, and a commit SHA.
The problem
Section titled “The problem”AI agents hallucinate API calls. They invent function names, guess parameter types, and produce code that doesn’t compile.
The fix
Section titled “The fix”Skill Forge reads the source and hands your agent the truth — with receipts. Every function signature, every parameter type, every usage pattern traces back to a file, a line, and a commit SHA in the upstream repository.
A receipt looks like
[AST:cognee/api/v1/search/search.py:L26]
✓
If SKF can’t cite a source, it doesn’t include the instruction.
Verify any claim in 60 seconds →
How SKF compares
Section titled “How SKF compares”| Approach | What it does well | Where it falls short |
|---|---|---|
Skill scaffolding (npx skills init) | Generates a spec-compliant skill file | The file is empty — you still have to write every instruction by hand |
| LLM summarization | Understands context and intent | Generates plausible-sounding content that may not match the actual API |
| RAG / context stuffing | Retrieves relevant code snippets | Returns fragments without synthesis — no coherent skill output |
| Manual authoring | High initial accuracy | Drifts as the source code changes, doesn’t scale across dependencies |
| IDE built-in context (Copilot, Cursor) | Convenient, zero setup | Uses generic training data, not your project’s specific integration patterns |
| Skill Forge | Every instruction cites upstream file:line at a pinned commit. Falsifiable in 60 seconds. | Coverage depends on which tools you’ve installed (Quick / Forge / Forge+ / Deep tiers). |
Quick install
Section titled “Quick install”Requires Node.js >= 22, Python >= 3.10, and uv.
npx bmad-module-skill-forge installThen generate your first skill:
@Ferris SF # Set up your forge@Ferris QS <package> # Generate a skill in under a minuteSee Getting Started for platform support, tier selection, and troubleshooting.