I have started my new insta page .Where, I post my digital clothing. Best thing you can do is follow the page and love the post and least is to relax and drink water😂
https://t.co/bsbGB2efK1
This is so inspiring. 👍🏼
I don’t know who this boy is, but he deserves all the love and recognition for being an inspiration to so many of us who struggle with various limitations or inhibitions.
Let’s make him famous 😊
Skill Graphs > SKILL .md
Everyone's talking about skills for AI agents.
But almost nobody is talking about how to structure them.
Right now, the default approach is simple. You write one skill file that captures one capability. A skill for summarizing. A skill for code review. A skill for writing tests.
One file, one job, and it works.
But I recently came across an idea that made me rethink this entirely.
What if skills weren't flat files? What if they were graphs?
Let me explain what I mean.
Think about how a senior engineer onboards you to a large codebase. They don't hand you one giant document and say "read this." They give you a map. They point you to the right modules. They explain how pieces connect. Then they let you go deeper only where you need to.
That's the mental model behind a skill graph.
Instead of one big file, you build a network of small, composable skill files connected through wikilinks. Each file captures one complete thought, technique, or concept. The links between them tell the agent when and why to follow a connection.
Here's what changes with this approach.
The agent doesn't load everything upfront. It scans an index, reads short descriptions, follows relevant links, and only reads full content when it actually needs to. Most decisions happen before reading a single complete file.
Each node is standalone but becomes more powerful in context. A "position sizing" node in a trading skill graph works on its own. But link it to risk management, market psychology, and technical analysis, and now you have context flowing between concepts.
And suddenly, domains that could never fit in one file become navigable. Company knowledge. Legal compliance. Product documentation. Org structure. All traversable from a single entry point.
The building blocks are surprisingly simple.
Wikilinks embedded in prose so they carry meaning, not just references. YAML frontmatter so the agent can scan nodes without reading them. Maps of content that organize clusters into navigable sub-topics.
Markdown files linking to markdown files, and nothing more.
If you want to dig deeper or try building one yourself, check out arscontexta. It's an open-source plugin that sets up the structure and helps you build skill graphs with your agent.
I have shared the link in the next tweet.