๐ฆ๐๐ผ๐ฝ ๐ฅ๐ฒ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐ง๐ต๐ฒ ๐ฆ๐ฎ๐บ๐ฒ ๐๐ ๐ฆ๐ธ๐ถ๐น๐น๐
Your team is wasting time.
One person builds an AI coding skill to run tests. Two weeks later, someone else builds a different version for the same task. They did not know the first one existed.
This creates chaos. You get different results on different machines. You get inconsistent standards. You get entropy instead of progress.
The solution is not more discipline. The solution is a shared catalog.
A good catalog must be easy to use. If adding a skill feels like a chore, your team will not do it. The catalog will die.
I use a single repo for my catalog. It follows a simple structure:
- engineering: development, testing, and automation
- productivity: writing and planning
- misc: everything else
At the root, a master table acts as the single source of truth. If a skill is not in the table, it does not exist.
To keep the catalog alive, I turned the bookkeeping into a skill. I call it "catalog-a-skill."
Instead of manual updates, the agent does the boring work:
- It reads the skill details.
- It picks the right category.
- It resolves the source link and commit hash.
- It updates the README files.
- It regenerates the master table.
The agent handles the tedious parts. The human does the fun part: writing useful skills.
To make this work for your team, follow this pattern:
- Create a catalog repo with simple categories.
- Set a clear source of truth, like a master table.
- Write a meta-skill to handle the updates.
- Add gates. The agent should refuse to add a skill if data is missing or names do not match.
A catalog survives only when contributing costs nothing. Let your agent keep the books so your team can keep building.
Optional learning community: https://t.me/GyaanSetuAi