Evaluate

Tear down a third-party product/tool/library from a single URL and answer two questions: (1) is the product worth adopting as-is — installed into your Claude Code workflow (a CLI, MCP server, skill, or dotfile) or otherwise kept around — and (2) are there features or code worth lifting into your current repo. Most evaluations are hunting for one of those two wins. It resolves the URL to its source (repo, README, launch post — with Reddit and paywalled-fetch fallbacks), characterizes the product from its docs, clones the code locally when it's open source, then fans out read-only subagents — ea

37 stars 7 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill evaluate
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/evaluate ~/.claude/skills/evaluate

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /evaluate — teardown a product from a URL and decide what's worth keeping

Given one URL, produce an evidence-backed verdict plus a report. Subagents crawl the code
in chunks; the calling session keeps only conclusions.

## Two questions, every time

Judge both — don't collapse to "lift code":

1. **ADOPT AS-IS** — is the product itself worth keeping/running, slotted into your Claude
   Code workflow (a CLI on PATH, an MCP server, a `/skill` or hook pattern, a dotfile)?
   Judged from docs + how it runs, not a code port. Note install/runtime cost and whether
   it's handy at the workstation even if Worker-irrelevant.
2. **LIFT** — features/code/patterns worth pulling into **this repo**, or worth keeping as
   a reference snippet. The code-crawl axis.

A product can win on one, both, or neither — the verdict names which.

## Operating principles

- **Subagents protect the main context** — orchestrate and synthesize only; never read the
  clone file-by-file yourself; pull conclusions, not file dumps.
- **Evidence or it didn't happen** — every claimed feature cites `path:line`; no evidence,
  no claim.
- **Portability is the point** — score findings against this repo's runtime, deps, license.
- **Docs-only is valid for closed-source** — skip cloning, deliver a docs-based verdict,
  say so explicitly. Read-only rules: see Guardrails.

## Steps

### 0. Resolve the URL → find the source

Locate the product's docs/README and source repo. Try `WebFetch` first; if blocked
Read the full skill on GitHub

Details

Skill name
evaluate
Path
skills/evaluate/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Evaluate skill do?

Tear down a third-party product/tool/library from a single URL and answer two questions: (1) is the product worth adopting as-is — installed into your Claude Code workflow (a CLI, MCP server, skill, or dotfile) or otherwise kept around — and (2) are there features or code worth lifting into your current repo. Most evaluations are hunting for one of those two wins. It resolves the URL to its source (repo, README, launch post — with Reddit and paywalled-fetch fallbacks), characterizes the product from its docs, clones the code locally when it's open source, then fans out read-only subagents — ea

How do I install the Evaluate skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill evaluate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Evaluate popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Frontier Spend

37

iamneilroberts/claude-skills

Use when planning how to spend scarce or expiring access to a premium frontier-tier model (usage-capped, deprecation cliff, "how should I spend my remaining premium-model budget", 2x burn rate, model leaving the plan) — before starting any premium-model session or writing a spend plan.

AI, LLMs & Agents

Deepagents

32

joneqian/claude-skills-suite

LangChain Deep Agents framework for building autonomous coding agents. Use for agent harness, backends, subagents, human-in-the-loop, long-term memory, middleware, and CLI-based agent development.

AI, LLMs & Agents

Gemini Review

37

iamneilroberts/claude-skills

Get a second-opinion review of the current diff (or a chosen focus — architecture, security, docs, design, performance, tests) from the Gemini CLI, then present its findings alongside your own analysis. Single-reviewer counterpart to /codex-review and /review-panel; needs the `gemini` CLI installed. Triggers on `/gemini-review [focus]`, "gemini review this", "get a gemini second opinion on this diff".

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.