agentleFS
Sign inStart free
chanjalmechanjalme/claude-skills/skills/skill-router/SKILL.md

skill-router

Skill0 starsChanged 5 months agoMITView on GitHub

Use at the START of any non-trivial task to pick the right skills from Christian's large installed library before doing the work. Triggers when a task could plausibly match one or more installed skills, when the user says 'which skills', 'use the right skills', 'stack skills', or when starting building/design/research/business/job-hunt work. Routes to 2-4 relevant skills, orders them (process skill first, implementation second), and always ends the stack with an audit/review skill.

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context-engineering, accessibility and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mrgoonieSkill

    context-engineering

    Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

    Also in 3 projects that use this

  • ElasticSkill

    accessibility

    Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.

    Also in 3 projects that use this

  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 4 projects that use this

  • SupabaseSkill

    copywriting

    Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

    Also in 3 projects that use this

  • GoogleSkill

    teach

    Teach the user a new skill or concept, within this workspace.

    Also in 3 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 3 projects that use this

  • +4 more from google

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    State the stack out loud: before starting: "Routing: [process] → [domain] → [audit]." One line.

    line 31
  2. Distinctive:

    Don't list every plausible skill.

    line 39
  3. Distinctive:

    Don't skip the audit skill because the task "looks simple."

    line 40
  4. Distinctive:

    Don't route for trivial conversational replies.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Router

Christian has 300+ skills installed. The failure mode is doing work raw when a skill exists, or picking the wrong one. This skill makes selection deliberate.

When to run

At the start of any task that is not a one-line answer. Run BEFORE exploring or building.

Procedure

  1. Classify the task into one or more buckets:
    • Build / code (web, bot, game, script)
    • Design / brand / visual
    • Business / Luno (planning, marketing, finance, launch)
    • Job hunt (cover letter, LinkedIn, resume)
    • Research / learning / knowledge
    • Writing / content
    • Ops / debugging / review
  2. Pick 2-4 skills max. Order them:
    • Process skill first — it sets HOW: superpowers:brainstorming (anything creative/new), superpowers:systematic-debugging (bugs), superpowers:writing-plans (multi-step), superpowers:test-driven-development (impl).
    • Implementation/domain skill second — frontend-design, logo-creator, telegram-bot-factory, luno-os, deep-research, cover-letter-loop, etc.
    • Audit/review skill LAST, always — claude-design-auditor-skill, code-review, accessibility-audit, avoid-ai-writing, pm-skills:pm-critic, or verification-before-completion. Never end a build without one.
  3. State the stack out loud before starting: "Routing: [process] → [domain] → [audit]." One line. Then execute.

Christian's standing preferences (from memory)

  • Stack 2+ skills at once; always end with an audit/review skill to catch design flaws.
  • For new builds: plan → explore → tests-first → minimum implementation, in that order.
  • Personal skills to prefer when relevant: luno-os, cover-letter-loop, vault-librarian, assumption-check, memory-hygiene, telegram-bot-factory, research-to-vault.

Anti-patterns

  • Don't list every plausible skill. 2-4, ordered, then go.
  • Don't skip the audit skill because the task "looks simple."
  • Don't route for trivial conversational replies.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free