跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
AI 与知识库

vet

Decides whether someone else's repo, skill, plugin or MCP server is worth adding to this workspace, and records the verdict in a ledger where the next session finds it. Use when the user drops a link or a list of links and asks if it is useful, worth adding or worth stealing, says "eval this", "vet these", "should I install this", "is this worth it", or points at a note full of tools to triage; also before adopting any external tool found mid-task. Dedupes against past verdicts first. Do NOT use to install anything, or to search for prior art while building (that is /outside).

dtiger1889-ops · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add dtiger1889-ops/claude-harness-toolbox --skill vet

技能说明


name: vet description: >- Decides whether someone else's repo, skill, plugin or MCP server is worth adding to this workspace, and records the verdict in a ledger where the next session finds it. Use when the user drops a link or a list of links and asks if it is useful, worth adding or worth stealing, says "eval this", "vet these", "should I install this", "is this worth it", or points at a note full of tools to triage; also before adopting any external tool found mid-task. Dedupes against past verdicts first. Do NOT use to install anything, or to search for prior art while building (that is /outside).

vet -- is someone else's thing worth putting in this workspace?

/outside asks "has anyone shipped this?" while you are building. vet answers the next question: someone HAS shipped it, here is the link, does it earn a place here. It ends in a ledger entry, not an opinion, so the same repo never gets evaluated twice from scratch.

Default: steal the pattern, don't install the thing. Installing is the exception and has to be argued for. Rejecting is a normal, cheap outcome.

Setup: the ledger is one markdown file you choose (for example notes/tools-evaluated.md). Name it in your workspace CLAUDE.md so every session finds it.

Copy this checklist into your response and check items off as you complete them:

  • 1. Candidates listed -- every shortened link resolved, count stated
  • 2. Dedupe sweep run -- each candidate marked NEW / JUDGED / STALE
  • 3. Cheap gates -- identity, liveness, license, entry cost; kills recorded
  • 4. Survivors researched -- inline if <=3, fanned out if more
  • 5. Fit judged in THIS session (G1-G5) -- one verdict per candidate
  • 6. Ledger updated + follow-ups routed
  • 7. Report written to the cap in step 7

1 -- list the candidates

Never judge a thing by its name. Tool names routinely say nothing about what the tool does. Resolve every wrapped or shortened link first (fetch it; follow a cross-host redirect with a second fetch). State the count. More than 8 candidates makes this a batch run.

2 -- dedupe FIRST, before spending one research token

Search for each candidate's name (and its repo slug) across the ledger, your notes, every project's state files and your installed skills folder (~/.claude/skills/). Use plain grep -rin, because search tools that honor .gitignore silently skip ignored folders. A hit in the skills folder means a local equivalent exists: the question becomes "does the external one do something ours does not?"

Mark each candidate:

  • JUDGED -- a dated verdict exists. One line in the report quoting verdict, date and file. Stop. No further spend.
  • STALE -- judged more than 90 days ago, judged on one dimension only, or the repo has moved or changed shape since. Re-check, and say in the entry what changed.
  • NEW -- no hit. Continue.

3 -- cheap gates before any deep read

Ordered so you never pay for a candidate you are going to discard. A kill here is a result.

  • G0a identity. Skill / plugin / MCP server / CLI / library / awesome-list / blog post? An awesome-list is a source of candidates, not a candidate -- say so.
  • G0b liveness. URL resolves? Last commit? Archived? Moved?
  • G0c license. Non-permissive is a hard stop for anything that would touch public work.
  • G0d entry cost on its face. A runtime you don't run, a third-party marketplace, a hosted paid service, or credentials handed to a stranger's server.

4 -- research the survivors

Three or fewer: inline. Read the README, then the actual SKILL.md / entrypoint -- READMEs oversell; the instruction file is the product.

More than three: fan out to helper agents on a cheaper model, 4-5 candidates per agent (each helper costs a full context to start, so one per link is waste). Helpers SUMMARIZE; they never judge fit and never write to disk. Prompt shape:

For each of these links, read the README and the main instruction file (SKILL.md, plugin manifest, or server entrypoint) and return ONE block per link, nothing else. No recommendations, no judgement about whether it is good.

  • name / url
  • what it actually is and in one sentence what it does
  • mechanism -- always-on hook, slash command, background service, prompt pack, marketplace install
  • install footprint -- steps, runtimes, files it writes, what it adds to every session
  • permissions and reach -- hooks, shell, network egress, credentials, third-party servers
  • license, last commit date, archived y/n
  • evidence of it working -- benchmarks, replications, critiques; if a headline number exists, search for whether anyone reproduced or debunked it
  • closest thing it would compete with in this workspace: <list your state files, skills, hooks, notes system, scheduled tasks>
  • verbatim quote of anything alarming (network calls, telemetry, auto-commits)

If a link 404s, say so and move on.

5 -- judge fit in THIS session

Do not delegate this half. Run the gates in order; failing an early gate skips the rest.

  • G1 -- named pain. Does it solve a problem written down somewhere real (an open thread, a backlog item, a note, a complaint the user actually made)? No named pain means Watching -- write the entry, spend nothing more. Before any "nothing here needs it" verdict, grep -rin the pain's keywords across the state files and notes and quote the hits or "none found", because an unsearched negative is a guess.
  • G2 -- collision. Does it compete with something already running here? Competing with a working system defaults to Stole the idea, never a parallel install.
  • G3 -- blast radius. What does installing grant it: always-on hooks, tokens in every context window, a marketplace dependency, disk writes, auto-commits, network egress? A disposable prompt beats an always-on install at equal val
阅读完整来源 ↗