ml

What it does and when to use it

Machine learning and LLM engineering judgment, distilled from a stronger model - invoke when DECIDING whether/how to use ML or an LLM for a task (prompt vs RAG vs fine-tune vs classical); working with training/eval data or labels; building or reviewing evals for models and LLM features; designing RAG, structured output, or agent pipelines; or diagnosing why a model/LLM feature underperforms. Method-selection ladder, data and leakage discipline, eval-as-spec rules, LLM-era craft, and a trap catalog.

How it works

1. Route by moment
2. Scope and neighbors
3. The stance

---
user-invocable: false
name: ml
description: Machine learning and LLM engineering judgment, distilled from a stronger model - invoke when DECIDING whether/how to use ML or an LLM for a task (prompt vs RAG vs fine-tune vs classical); working with training/eval data or labels; building or reviewing evals for models and LLM features; designing RAG, structured output, or agent pipelines; or diagnosing why a model/LLM feature underperforms. Method-selection ladder, data and leakage discipline, eval-as-spec rules, LLM-era craft, and a trap catalog.
---

# ML — approach, data, evals, LLM craft, traps

Rule content lives in the five files below; this SKILL.md only routes
(`doctrine/04-maintenance.md` governs edits to this bundle too).

## Route by moment

| You are about to… | Read (in this folder) |
|---|---|
| Decide whether ML/an LLM is warranted, and which method rung to use | `approach.md` |
| Touch a dataset, labels, or splits; suspect a score is too good | `data.md` |
| Define success, build/judge an eval, or assess someone's metric claim | `evals.md` |
| Build with LLMs: prompts, RAG, structured output, agents, model choice | `llm.md` |
| Diagnose an underperforming model or LLM feature | `data.md` §1 first (read real failures), then `llm.md` §3 if RAG, `traps.md` to name the pattern |
| Review an ML project's health; name why a claim or pipeline smells wrong | `traps.md` |

A new ML feature usually runs `approach.md` (interrogate + pick the rung) →
`evals.md` §1 (eval BEFORE build) → `data.md` → then `llm.md` if the rung is LLM-shaped
→ skim `traps.md` §C before finalizing any launch or monitoring plan.

## Scope and neighbors

Modeling and evaluation judgment. The serving infrastructure around a model is ordinary
backend (`backend` bundle: APIs, queues, operate.md); experiment execution discipline is
`methods` (investigate/verify); whether to delegate → `doctrine`.

## The stance

**The eval is the spec; anything unmeasured is folklore.** Look at the data with your
own eyes (`data.md` §1), climb the method ladder from the cheapest rung (`approach.md`
§3), and treat every surprising score as leakage until disproven (`data.md` §2). The
failure mode of this field is not bad models — it is unearned confidence in numbers.

Versions

Database snapshot: 13.11.2026 · package version 5feeb754ff27 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100ai-playbook
  Production-grade decision framework for building AI features, AI workflows, AI agents, and AI-augmented systems. Use this skill whenever the user is designing, building, debugging, reviewing, or deciding whether to add AI to a system — including any work involving LLM calls,…
• 100sota-llm-engineering
  State-of-the-art LLM application engineering rules for BUILDING and AUDITING LLM-powered features. Claude should use this skill whenever it is building, modifying, or reviewing anything that calls a language model — chat features, RAG pipelines, agents and tool use, structured…
• 100llm-app-engineering
  Build reliable LLM-powered features: prompts, structured output, RAG, tool use, evals, cost and latency, safety. Use when integrating or reviewing LLM, agent or retrieval features in an application.
• 95agentic
  AI/LLM engineering patterns. Triggers when building agents, prompts, MCP servers, evals, or RAG. Model selection, caching, tool design, multi-agent orchestration.
• 100evals
  Build and run evaluations for LLM features, prompts, agents, and RAG pipelines — golden datasets, assertions, LLM-as-judge graders, regression gates in CI, A/B comparison of prompts or models. Use whenever someone changes a prompt, swaps a model, ships an AI feature, asks \"is…
• 100ai-engineer
  AI/LLM Application Engineer (/ai) — builds LLM-powered product features: RAG, agentic workflows, prompt engineering, tool use, structured output, evals, and guardrails. Use when implementing AI features in an app — a chatbot, RAG over docs, an agent, a summarizer, semantic…