Agent skill · Design & Presentation

huggingface-best

Use when the user asks about finding the best, top, or recommended model for a task, wants to know what AI model to use, or wants to compare models by benchmark scores. Triggers on: \"best model for X\", \"what model should I use for\", \"top models for [task]\", \"which model runs on my laptop/machine/device\", \"recommend a model for\", \"what LLM should I use for\", \"compare models for\", \"what's state of the art for\", or any question about choosing an AI model for a specific use case. Always use this skill when the user wants model recommendations or comparisons, even if they don't expl

Wayner Barrios443★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add waybarrios/opencode-power-pack --skill huggingface-best --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/huggingface-best/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 443
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# HuggingFace Best Model Finder Finds the best models for a task by querying official HF benchmark leaderboards, enriching results with model size data, filtering for what fits on the user's device, and returning a comparison table with benchmark scores. --- ## Step 1: Parse the request Extract from the user's message: - **Task**: what they want the model to do (coding, math/reasoning, chat, OCR, RAG/retrieval, speech recognition, image classification, multimodal, agents, etc.) - **Device**: hardware constraints (MacBook M-series 8/16/32/64GB unified memory, RTX GPU with VRAM amount, CPU-only, cloud/no constraint, etc.) If device is not mentioned, skip filtering entirely and return the highest-performing models regardless of size. If the task is genuinely ambiguous, ask one clarifying question. ### Device → max parameter budget When a device is specified, extract its available memory (unified RAM for Apple Silicon, VRAM for discrete GPUs) and apply: - **fp16 max params (B)** ≈ memory (GB) ÷ 2 - **Q4 max params (B)** ≈ memory (GB) × 2 Examples: 16GB → 8B fp16 / 32B Q4 — 24GB VRAM → 12B fp16 / 48B Q4 — 8GB → 4B fp16 / 16B Q4 --- ## Step 2: Find relevant benchmark datasets Fetch the f

What's inside
Steps it walks through
  1. Step 1: Parse the request
  2. Device → max parameter budget
  3. Step 2: Find relevant benchmark datasets
  4. Step 3: Fetch top models from leaderboards
  5. Step 4: Enrich with model metadata
  6. Step 5: Filter and rank
  7. Step 6: Output
  8. Comparison table
  9. Follow-up
  10. Error handling
Commands it runs
export HF_AUTH="Bearer $(cat ~/.cache/huggingface/token)"
curl -s -H "Authorization: $HF_AUTH" \
REST API
CLI (hf-cli)
hf models info org/model1 --json | jq '{safetensors, tags, cardData}'
More from opencode-power-pack
All skills →
About this skill
What does the huggingface-best skill do?

Use when the user asks about finding the best, top, or recommended model for a task, wants to know what AI model to use, or wants to compare models by benchmark scores. Triggers on: \"best model for X\", \"what model should I use for\", \"top models for [task]\", \"which model runs on my laptop/machine/device\", \"recommend a model for\", \"what LLM should I use for\", \"compare models for\", \"what's state of the art for\", or any question about choosing an AI model for a specific use case. Always use this skill when the user wants model recommendations or comparisons, even if they don't expl

How do I install it?

Run `npx skills add waybarrios/opencode-power-pack --skill huggingface-best --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going