agentleFS
mrloldevmrloldev/artificial-analysis-skill/SKILL.md

artificial-analysis

Skill2 starsChanged 7 months agoMITView on GitHub

Pick the right LLM or media model for a task, backed by live benchmark data from artificialanalysis.ai. Use when the user asks "which model should I use for X", "what's the best/fastest/cheapest model", "compare model A vs B", "model leaderboard", or anything about model intelligence / speed / price / context / coding-or-math ability. Also for text-to-image, image-editing, text-to-speech, text-to-video, and image-to-video rankings. Triggers on "which model", "best model for", "cheapest LLM", "fastest model", "compare models", "model pricing", "artificial analysis", "MMLU score", "model ELO".

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. julweber/ai_agent_skills★ 2same name
    2. Kubementat/ai_agent_skills★ 2same name
    3. bitgineer/artificial-analysis-skill★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT skip step 3. Benchmark numbers change.

    line 31
  2. Very specific:

    When in doubt, use balanced.

    line 46
  3. Very specific:

    If slugs are unfamiliar to the user, offer compare.sh as a follow-up.

    line 126

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

Artificial Analysis: pick the right model

Live benchmark data from https://artificialanalysis.ai — intelligence index (10 evals), coding index, math index, output speed, time-to-first-token, pricing, and context-window, for ~400+ LLMs plus media-model ELO leaderboards.

Your job: when the user needs a model recommendation, run recommend.sh with the right profile — do not guess from memory. Model rankings change weekly; never answer from training data alone.

Prerequisites

  1. AA_API_KEY must be exported. Free key (1,000 req/day) at https://artificialanalysis.ai/documentation. If missing, scripts prompt on TTY or fail with a clear pointer.
  2. curl and jq installed.

Responses cached 24h at ~/.cache/artificial-analysis/ — repeated calls are free of rate-limit cost.

Decision flow — ALWAYS follow this for "which model" questions

1. Classify the user's need → pick ONE profile (see table below).
2. Extract hard constraints: budget, min context, required provider, required quality floor.
3. Run:  recommend.sh <profile> [--budget $/M] [--min-context N] [--min-intel N] [--creator X] --top 5
4. Report the top pick with its trade-offs vs. #2 and #3.
5. If the user names two or more specific models, follow with: compare.sh <slug> <slug> ...

Do NOT skip step 3. Benchmark numbers change; the API is the source of truth.

Profile selection

User says / impliesProfileOptimizes for
"best / smartest / most capable model"smartintelligence_index (tie-break: coding)
no strong steer, general production usebalancedintelligence + price + speed
"fast / low latency / streaming / realtime"fastoutput t/s + low TTFT
"cheap / bulk / high-volume / budget"cheapprice (with a sane quality floor)
"coding / code-gen / codegen agent"codingcoding_index
"math / reasoning-heavy / proofs"mathmath_index
"long docs / 200k+ / large context"long-ctxcontext window, then intelligence
"agent / tool loop / long-running"agenticintelligence + speed + context

When in doubt, use balanced. If the user has two conflicting hints (e.g. "fast and smart"), pick the dominant one and say so.

Hard constraints → flags

  • Budget → --budget 5 means ≤ $5/M tokens blended (3:1 input:output).
  • Min context → --min-context 200000.
  • Quality floor → --min-intel 60 (intelligence_index is ~0–100-ish).
  • Specific vendor → --creator anthropic (matches slug or name, case-insensitive substring).

Core scripts

recommend.sh — the one you'll use most

# Pick the best general model
"${CLAUDE_SKILL_DIR}/scripts/recommend.sh" balanced --top 5

# Cheapest decent model for batch processing
"${CLAUDE_SKILL_DIR}/scripts/recommend.sh" cheap --min-intel 55

# Fast Anthropic model for streaming UI
"${CLAUDE_SKILL_DIR}/scripts/recommend.sh" fast --creator anthropic

# Smart model that fits a 500k-token document
"${CLAUDE_SKILL_DIR}/scripts/recommend.sh" long-ctx --min-context 500000

# Best coding model under $10/M
"${CLAUDE_SKILL_DIR}/scripts/recommend.sh" coding --budget 10

Output: ranked table with score, slug, creator, intel/code/math, t/s, TTFT, $/M, ctx.

models.sh — leaderboard

# Top 10 by raw intelligence
"${CLAUDE_SKILL_DIR}/scripts/models.sh" --top 10 --sort-by evaluations.artificial_analysis_intelligence_index

# Just the slugs (for piping into compare.sh)
"${CLAUDE_SKILL_DIR}/scripts/models.sh" --top 20 --slugs

# Inspect available fields on the first model
"${CLAUDE_SKILL_DIR}/scripts/models.sh" --path

Sort keys containing latency, price, ttft, or time_to_first are treated as lower-is-better automatically.

compare.sh — head-to-head

"${CLAUDE_SKILL_DIR}/scripts/compare.sh" claude-4-5-sonnet gpt-5-xhigh gemini-3-1-pro-preview

Prints rows for creator, intel, coding, math, t/s, TTFT, blended / input / output price, and context window.

media.sh — image / audio / video leaderboards

"${CLAUDE_SKILL_DIR}/scripts/media.sh" image --top 15
"${CLAUDE_SKILL_DIR}/scripts/media.sh" edit  --top 10
"${CLAUDE_SKILL_DIR}/scripts/media.sh" tts   --top 10
"${CLAUDE_SKILL_DIR}/scripts/media.sh" ttv   --categories --top 10
"${CLAUDE_SKILL_DIR}/scripts/media.sh" i2v   --categories --top 10

Ranked by ELO rating.

fetch.sh — raw access (for custom jq)

"${CLAUDE_SKILL_DIR}/scripts/fetch.sh" data/llms/models --raw \
  | jq '[.data[] | select(.context_window >= 1000000)] | length'

Guidance when reporting to the user

  1. Name the top pick by slug, link to its AA page (https://artificialanalysis.ai/models/<slug>).
  2. Justify with the two or three metrics that drove the choice — e.g. "intelligence 72, $3.20/M blended, 190 t/s".
  3. Mention the runner-up in one line with the tradeoff ("If you want lower latency, try X at $/M but intel Y").
  4. Attribute: say "per Artificial Analysis benchmarks" — that's the data source and their ToS expects it.
  5. If slugs are unfamiliar to the user, offer compare.sh as a follow-up.

Failure handling

  • 401 → remind user about AA_API_KEY and link to https://artificialanalysis.ai/documentation.
  • 429 → the script auto-falls-back to stale cache; warn the user it's stale.
  • Empty filter result → loosen a constraint (usually --budget or --min-intel).
  • Unknown slug in compare.sh → it warns on stderr; list candidates with models.sh --slugs | grep -i <partial>.

Notes on authentication

The Artificial Analysis API requires an API key. There is no unauthenticated public endpoint — the website renders data server-side through authenticated calls. A free key (1,000 req/day) is explicitly offered for this use case; the skill caches aggressively to stay under that limit.

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.