triage · takagoto — Claude Code skill: task routing and setup
This skill asks what you’re trying to learn, build, debug, or review in RAG, then points you to a fitting command or agent. Use it when the next step isn’t clear.
npx skills add TakaGoto/rag-learning-academy --skill triage -a claude-codeWhat triage does
The skill starts by sorting out your situation: learning RAG, studying a topic, building a system, troubleshooting, or reviewing existing work. It asks a follow-up question and maps the answer to a command. For instance, irrelevant retrieval points to /debug-rag, while slow or costly results point to /benchmark.
Learning routes cover lessons, concept explanations, quizzes, and progress checks. Building routes can lead to guided component work, architecture design, or a comparison of approaches. If the listed options miss the mark, describe the situation in your own words; triage can use its judgment and suggest a specific agent.
Before handing off, it gives a reason for its recommendation and asks whether you want to proceed. You still need to confirm before it tells you to run the suggested command. Triage routes the request; the selected skill handles the actual task.
What it helps with
- choose a command to start learning RAG
- find a route for building a RAG system
- send retrieval or generation issues to the right diagnostic
- decide how to review pipeline quality or performance
Example prompts for the agent
- I’m learning RAG and can’t tell where to begin.
- I’m building a RAG system; help me choose a route for the architecture stage.
- My RAG search returns irrelevant documents. What should I run next?
How to install triage
1Skills CLI (Vercel)
npx skills add TakaGoto/rag-learning-academy --skill triage -a claude-code2Manually: put the files in place
~/.claude/skills/triage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/triage/
1Skills CLI (Vercel)
npx skills add TakaGoto/rag-learning-academy --skill triage -a codex2Manually: put the files in place
.agents/skills/triage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TakaGoto/rag-learning-academy --skill triage -a cursor2Manually: put the files in place
.cursor/skills/triage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TakaGoto/rag-learning-academy triage2Manually: put the files in place
.github/skills/triage/SKILL.md1Skills CLI (Vercel)
npx skills add TakaGoto/rag-learning-academy --skill triage -a gemini-cli2Platform CLI
gemini skills install https://github.com/TakaGoto/rag-learning-academy --path .claude/skills/triageManually: put the files in place
.devin/skills/triage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add TakaGoto/rag-learning-academy --skill triage -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about triage
How do I install triage in Claude Code?
Run npx skills add TakaGoto/rag-learning-academy --skill triage -a claude-code. The skill file is at ~/.claude/skills/triage/SKILL.md.
What does the triage skill do?
It asks about your goal and recommends a relevant command or agent. Before handing off, it explains its choice and checks whether you want to continue.
Which platforms support triage?
The skill supports Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. The install command varies by platform.
Source text
SKILL.md · MIT
---
name: triage
description: "Not sure where to start or what's wrong? Get routed to the right agent or skill."
---
# Triage: Find the Right Help
> **When to use this:** You're stuck, confused, or not sure which `/command` to run next. Triage asks a few quick questions and points you in the right direction.
## Step 1: Understand the Learner's Situation
Ask one question to categorize their need:
**"What best describes where you are right now?"**
1. **"I'm brand new to RAG"** → Suggest `/start` to begin their learning journey
2. **"I'm learning and want to study a topic"** → Go to Step 2 (Learning Path)
3. **"I'm building something and need help"** → Go to Step 3 (Building Path)
4. **"Something is broken / not working well"** → Go to Step 4 (Debugging Path)
5. **"I want to review or improve what I have"** → Go to Step 5 (Review Path)
## Step 2: Learning Path
Ask: **"What would you like to do?"**
| Goal | Recommended |
|------|-------------|
| Learn a concept step by step | `/lesson` |
| Get a quick definition | `/glossary [term]` |
| Understand something deeply | `/explain [concept]` |
| Test what I know | `/quiz [topic]` |
| See my progress | `/roadmap` |
| Read a research paper | `/paper-review` |
| Compare two approaches | `/compare` |
## Step 3: Building Path
Ask: **"What stage are you at?"**
| Stage | Recommended |
|-------|-------------|
| I haven't started building yet | `/build` — guided component construction |
| I need to design my system first | `/architecture` — design your RAG architecture |
| I want a real-world challenge | `/challenge` — open-ended project |
| I need help choosing between approaches | `/compare` — side-by-side comparison |
## Step 4: Debugging Path
Ask: **"What's the symptom?"**
| Symptom | Recommended |
|---------|-------------|
| Retrieved documents aren't relevant | `/debug-rag` → retrieval diagnosis |
| The LLM makes things up / hallucinates | `/debug-rag` → generation diagnosis |
| Results are slow or expensive | `/benchmark` → performance profiling |
| I'm not sure what's wrong, quality just feels off | `/evaluate` → measure with metrics first |
| I'm getting errors in my code | `/code-review` → get expert feedback |
## Step 5: Review Path
Ask: **"What would you like to review?"**
| Goal | Recommended |
|------|-------------|
| Get feedback on my code | `/code-review` |
| Measure my pipeline's quality | `/evaluate` |
| Check performance / speed / cost | `/benchmark` |
| See what to learn next | `/roadmap` |
## Step 6: Route and Hand Off
Once you've identified the right skill:
1. Briefly explain WHY you're suggesting that skill ("Based on what you described, `/debug-rag` is the best fit because it has a structured diagnostic process for retrieval issues.")
2. Ask if they'd like to proceed or if they had something else in mind.
3. If they confirm, tell them to run the suggested `/command`.
If none of the options fit, ask the learner to describe their situation in their own words and use your judgment to route them — you can also suggest they talk directly to a specific agent (e.g., "You might want to ask the chunking-strategist about that").
Suggest 2-3 relevant next steps:
- `/start` — if they haven't begun their learning journey yet
- `/roadmap` — to see their overall progress and recommended path
- The specific skill identified through triage
© TakaGoto · MIT · TakaGoto/rag-learning-academy
Similar skills
All skills for AI and ML →triage by other authors comes first.
