$ man context-wiki/skill-trees

I built a skill tree that scans my entire repo. Content pieces, GTM operations, voice system, agent skills, infrastructure. It maps everything to an RPG progression tree. Not because it is useful for AI. Because it is useful for me. Seeing your capabilities mapped out as a tree shows you where you are strong and where you have gaps. It also makes the whole system tangible. You can show someone your skill tree and they immediately understand the scope of what you have built. It turns an abstract repo of markdown files into a visual inventory of capabilities.

PATTERN

The /skilltree skill scans the repo and categorizes everything it finds. Content is counted by type: blog posts, LinkedIn drafts, X posts, Substack articles. GTM operations are counted by workflow: partner onboards, campaign launches, web reveal setups. Skills are counted and listed by category: content skills, deployment skills, partner skills, data skills. Infrastructure is assessed: monorepo structure, deployment pipeline, cron jobs, MCP integrations. Each category gets a level based on volume and depth. 0-5 pieces of content might be Level 1. 50+ pieces with multiple formats might be Level 10. The levels are not scientific. They are motivational. Seeing "Content: Level 7" makes you want to hit Level 8.

PRO TIP

The biggest value of a skill tree is making your progress visible to yourself. When you are building every day, it is easy to lose track of how much you have actually created. The repo grows. The skills multiply. The content stacks up. But unless you visualize it, it all feels like background noise. The skill tree turns that noise into signal. 40+ skills. 100+ content pieces. 5 MCP integrations. 3 websites. RPG progression with animated sprites. When I look at the tree, I see the system I have built. When someone else looks at it, they see the system they could build. That is the real value. Not the data. The visibility.