vault-router
Skill0 starsChanged 8 days agoMITView on GitHub
Entry point for the skill-vault collection. Use FIRST whenever a user makes a task request and any skill-vault skills are installed: read the request, analyze what the actual task and deliverable are, then route to the one matching vault skill and follow it. Also use when the user asks which skill can do something, or when a request does not obviously belong to any single skill.
In this repository15 other files it gives its agents.
- cloudflare-workerSkill
- oss-contributorSkill
- small-briefsSkill
- councilSkill
- title-cardSkill
- repo-auditSkill
- vps-deploySkill
- interactive-figureSkill
- lab-reportSkill
- net-labSkill
- study-notesSkill
- html-videoSkill
- manim-explainerSkill
- caption-craftSkill
- proofread-idSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 68
Interactive figure vs video: If the user wants to click and explore, it is interactive-figure.
- Distinctive: line 72
The right skill is not installed: Do not invent it and do not fake its workflow.
- Distinctive: line 85
Do not route based on one keyword while ignoring the deliverable.
- Distinctive: line 86
Do not load two full skills "just in case".
- Distinctive: line 88
Do not mention this router's mechanics at length.
- Distinctive: line 93
When a skill is added to or removed from the vault, add or remove its row in the catalog above in the same change.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vault Router
You are the front door of the skill-vault. The user should never have to know skill names. They describe what they want; you figure out which vault skill does it, load that skill, and follow it.
How to route
- Read the whole request first. Identify the task by its verb, its object, and above all its final deliverable (a file, a video, a PR, a deployed service). The deliverable is the strongest routing signal, stronger than any single keyword.
- Match against the catalog below. Each row lists a skill, what it produces, and typical signal phrases in English and Indonesian.
- Check it is actually installed. Route only to skills present in the current environment (your available-skills list, or sibling folders in the skills directory). The catalog lists the whole vault; the user may have installed only some of it.
- Load and follow. Open the matched skill's
SKILL.mdin full and do the task by its instructions. Tell the user in one short line which skill you picked, for example: "Routing to lab-report for this." - Stay in the routed skill until the task is done or it clearly hands off to another one.
Catalog
| Skill | Produces | Signals (EN / ID) |
lean-code | Code written or refactored to be concise | code, refactor, clean up / rapikan kode, bikin ringkas |
oss-contributor | A contribution to someone else's repo: screened claim, PR, disclosure | contribute, external PR, good first issue / kontribusi, klaim issue, PR ke repo orang |
small-briefs | A big build split into small verified briefs for a coding agent | break this down, briefs / pecah tugas, delegasikan, brief untuk opencode |
cloudflare-worker | Cloudflare Workers + D1 apps and fixes | cloudflare, wrangler, D1, worker / deploy worker, migrasi D1 |
laravel-patterns | Laravel architecture patterns, adapted from ECC | laravel, eloquent, artisan / pola laravel, bikin fitur laravel |
laravel-security | Laravel security checklist and hardening, adapted from ECC | laravel security, sanctum, csrf / keamanan laravel, audit keamanan |
react-patterns | React 18/19 patterns and hooks discipline, adapted from ECC | react, hooks, useEffect / komponen react, state react |
nextjs-turbopack | Next.js 16+ and Turbopack guidance, adapted from ECC | next.js, turbopack, proxy.ts / next dev lambat |
ui-craft | UI and interface design work | design, UI, layout, landing page / desain tampilan, bikin UI |
title-card | Title cards and thumbnails as PNG images | thumbnail, title card, cover image / thumbnail, cover video |
lab-report | A practicum report in the owner's house format | lab report, practicum / laporan praktikum, hasil pengamatan |
interactive-figure | A clickable HTML figure for a study concept | interactive diagram, simulation / figur interaktif, diagram bisa diklik, simulasi konsep |
anatomy | Crafted isometric SVG figures of a concept as a physical object, adapted from wheresryan22/anatomy | isometric figure, svg illustration / figur isometrik, gambar penjelasan |
cisco-ios-patterns | Cisco IOS review patterns and change windows, adapted from ECC | cisco, ios, access-list / konfigurasi cisco, wildcard mask |
net-lab | Networking lab configs and validation, module-faithful | VLAN, routing, Packet Tracer, subnet / jarkom, konfigurasi switch, praktikum jaringan |
study-notes | Study notes and flashcards from slides or PDFs | summarize, flashcards, notes / rangkum materi, catatan belajar, flashcard |
html-video | A rendered MP4 video from a text brief | video, MP4, shorts, reels, explainer / buatkan video, video penjelasan |
manim-explainer | Math and science animations in Manim | manim, math animation / animasi matematika, animasi rumus |
vps-deploy | An app deployed to a VPS: systemd, Tailscale-only, preview | deploy, VPS, server, systemd / deploy ke VPS, online-kan, pasang di server |
repo-audit | A security audit of the user's own public repos | audit my repos, leaked secrets / audit repo, cek kebocoran, secret bocor |
homelab-vlan-segmentation | Home network VLAN segmentation, adapted from ECC | home vlan, iot isolation / vlan rumah, pisahkan iot, guest wifi |
caption-craft | Social media captions and carousel text, ID/EN | caption, carousel, post text / caption IG, teks carousel |
proofread-id | Formal Indonesian proofreading | proofread, spelling / cek ejaan, rapikan bahasa, periksa tulisan |
council | A hard decision pressure-tested by five advisor lenses with anonymous cross-review and one synthesized verdict | decide, should I X or Y, which option, pressure-test / pilih yang mana, minta pendapat kedua, uji keputusan, bantu putuskan |
Edge cases
- Two skills fit. Route to the one that owns the FINAL deliverable as
primary; use the other as a supporting reference and say so in one line.
Example: "a VLAN explainer video" routes to
html-video(deliverable: MP4) withnet-labconsulted for technical correctness. "Deploy my Workers app" routes tocloudflare-workerfor the app andvps-deployonly if a server is actually involved. - Interactive figure vs video. If the user wants to click and explore,
it is
interactive-figure. If they want a file that plays, it ishtml-videoormanim-explainer. When genuinely ambiguous, this is the one case worth a single short question. - The right skill is not installed. Do not invent it and do not fake its workflow. Name the skill, point to its path in the skill-vault repo, and either use the closest installed skill or do the task unaided, saying which you are doing.
- Nothing matches. Say plainly that the vault has no skill for this yet. Do the task normally if you can. If the request smells repeatable, close by suggesting it as a new vault skill: a name (English, cool, simple), its shelf, and one line on what it would do. The vault grows exactly this way.
- The user names a skill directly. Skip routing and follow it.
What not to do
- Do not route based on one keyword while ignoring the deliverable.
- Do not load two full skills "just in case"; route, then chain only on a real hand-off.
- Do not mention this router's mechanics at length. One routing line to the user is enough; then get to work.
Maintaining this file
When a skill is added to or removed from the vault, add or remove its row in the catalog above in the same change. A router pointing at skills that do not exist is worse than no router.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

