agentleFS
mikemorgensternmikemorgenstern/model-router/skills/help/SKILL.md

help

Skill0 starsChanged 10 months agoMITView on GitHub

Display all available commands and current configuration. User runs /model-router:help Display a comprehensive help screen showing all commands and current config: Then read ~/.model-router/config.yaml and show current config: If config doesn't exist, prompt to run setup:

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 1

    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:

    If config doesn't exist, prompt to run setup:

    line 91

“Common” is measured: kept by at least 6 in 10 of the 57 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

Model Router Help

Display all available commands and current configuration.

Trigger

User runs /model-router:help

Instructions

Display a comprehensive help screen showing all commands and current config:

Model Router - Intelligent AI Model Routing
============================================

COMMANDS:
  /model-router:setup          First-time setup wizard
  /model-router:help           Show this help (you are here)
  /model-router:status         Show current config and available models
  /model-router:recommend      Get model recommendation for a task
  /model-router:configure      Change any setting
  /model-router:test <model>   Test a model's performance
  /model-router:learn          Analyze usage and suggest improvements
  /model-router:update-models  Pull latest community model recommendations

USAGE EXAMPLES:
  "What model should I use for code review?"
      → Model Router will recommend based on your setup

  "/model-router:recommend reasoning"
      → Get recommendation for reasoning tasks

  "/model-router:test gemini-3-pro"
      → Run test suite on a model, optionally update recommendations

  "Route this to Gemini"
      → I'll use Gemini CLI to handle the task

QUICK REFERENCE - Task Types:
  critical_code   → Production code, security-critical
  code_review     → Code review, refactoring
  reasoning       → Complex reasoning, math, logic
  simple_edits    → Typo fixes, formatting
  bulk_operations → Batch processing, data extraction
  writing         → Documentation, emails
  analysis        → Data analysis, summarization

HOW IT WORKS:
  Model Router is a recommendation system. When you ask for help
  with a task, it suggests the best model based on:

  1. Task type (what you're trying to do)
  2. Your subscriptions (what's available)
  3. Your preferences (quality vs cost)
  4. Model capabilities (benchmarks, strengths)

  You then follow the recommendation by telling Claude to use
  a specific model, or by running the CLI command directly.

CONFIGURATION:
  Config file: ~/.model-router/config.yaml
  Models file: ~/.model-router/models.yaml
  Tracking:    ~/.model-router/tracking.jsonl

DOCUMENTATION:
  Full docs: https://github.com/mikemorgenstern/model-router

Then read ~/.model-router/config.yaml and show current config:

YOUR CURRENT CONFIGURATION:
  Profile: [profile]
  Routing preference: [preference]
  Tracking: [enabled/disabled]

  Subscriptions:
    Claude Pro:    [✓/✗]
    ChatGPT Plus:  [✓/✗]
    Google AI Pro: [✓/✗]

  CLI Tools:
    Codex: [✓ installed / ✗ not found]
    Gemini: [✓ installed / ✗ not found]

  Local Models (Ollama):
    [list models or "Not configured"]

If config doesn't exist, prompt to run setup:

No configuration found. Run /model-router:setup to get started.

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.