← ClaudeAtlas

using-agtmlslisted

Meta-router for the AgtMLS skill catalog. Read first when unsure which AgtMLS skill applies, when several look relevant, when asking 'is there a skill for porting or noyalib work', or when onboarding to how the hub's skills and shared references fit together.
sebastienrousseau/agtmls · ★ 1 · AI & Automation · score 80
Install: claude install-skill sebastienrousseau/agtmls
# Using AgtMLS — the meta-router AgtMLS is a hub of agent skills. This page is the discovery flowchart: it helps you pick the right skill (or decide none applies) before loading one. ## Pick a skill 1. **Porting / translating / rewriting code between languages?** → load **`cross-language-port`** (Rust, Python, Go, C++, Swift, TS, JS, Ruby, Bash). It preserves behaviour and *proves* equivalence. Micro-snippets (a few lines): do inline, don't load it. In-language migrations (Py2→3, ES5→ESNext, C++17→23) and behaviour-changing redesigns: not this skill. 2. **Doing ordinary engineering work — building, fixing, or finishing?** → load the discipline skill for the phase you are in. These apply in any repo, any language, and are always installed: | Phase | Skill | Load when | | --- | --- | --- | | Specify | **`brainstorming`** | The ask is vague and needs pinning down before anything is planned | | Decompose | **`writing-plans`** | Work spans several files or sessions and needs steps with done-conditions | | Build | **`test-driven-development`** | Adding or changing behaviour — red test first | | Diagnose | **`systematic-debugging`** | Something is broken and the cause is unknown | | Finish | **`verification-before-completion`** | About to claim done, fixed, or working | | Restructure | **`refactoring-safely`** | Changing shape without changing behaviour | | Firefight | **`incident-response`** | Something is broken in production ri