review-skill
Skill97 starsChanged 33 days agoApache-2.0View on GitHub
Inspect, safely test, and assess one Runx skill package for capability, trust, and operator readiness. Use when deciding whether to adopt, improve, reject, install, or publish a skill; its evidence-only assess runner is available when native test evidence already exists.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- rafapeixer/db-skillstheir own version, first seen Nov 8, 2026
- mongodb/docstheir own version, first seen Nov 2, 2026
- rafapeixer/java-skillstheir own version, first seen Oct 20, 2026
- nakane1chome/claude-skillstheir own version, first seen Oct 15, 2026
- mongodb/agent-skillstheir own version, first seen Oct 13, 2026
- mongodb/laravel-mongodbtheir own version, first seen Oct 13, 2026
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- mongodb/laravel-mongodb★ 7.1ksame name
- mongodb/docs★ 779same name
- harlan-zw/skilld★ 327same name
- skilld-dev/skilld★ 324same name
- mongodb/agent-skills★ 190same name
- aviz85/claude-skills-library★ 49same name
- mixpanel/ai-plugins★ 18same name
- geemus/hax-yax★ 4same name
- XAzer-R/azer-feilian-director★ 4same name
- alehlopeh/claude-skills★ 2same name
10 more not listed
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.
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- runxSkill
- adopt-skillSkill
- agencySkill
- answer-from-docsSkill
- attention-reviewSkill
- audit-receiptSkill
- brand-voiceSkill
- business-opsSkill
- chargeSkill
- chief-of-staffSkill
- cold-outreachSkill
- content-pipelineSkill
- contract-drafterSkill
- conversation-replySkill
- conversation-reviewSkill
- crm-cleanupSkill
- cve-auditSkill
- data-storeSkill
- data-subject-requestSkill
- deep-researchSkill
- diagnose-skill-runSkill
- dispute-respondSkill
- ecosystem-briefSkill
- extractSkill
- ghostwriteSkill
- github-pr-commentSkill
- github-pr-reviewSkill
- github-syncSkill
- google-analyticsSkill
- google-calendarSkill
- google-search-consoleSkill
- governed-outboundSkill
- helpdeskSkill
- incident-commanderSkill
- issue-intakeSkill
- issue-to-prSkill
- issue-triageSkill
- knowledge-routerSkill
- lead-enrichmentSkill
- lead-qualifySkill
- least-privilegeSkill
- ledgerSkill
- list-hygiene-judgeSkill
- marketplace-invokeSkill
- meeting-followupSkill
- mock-chargeSkill
- mock-paySkill
- mock-refundSkill
- moltbookSkill
- n8n-handoffSkill
- nitrosendSkill
- nws-weather-forecastSkill
- open-meteo-weather-forecastSkill
- operator-inboxSkill
- ops-deskSkill
- organic-growthSkill
- policy-authorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run the native harness only when catalog execution is read or plan.
- Distinctive: line 29
Check the happy path, refusal or stop path, authority boundary, artifact or effect, provenance, and recovery posture appropriate to the …
- Distinctive: line 40
Do not recommend provider readiness without provider readback.
- Distinctive: line 41
Do not recommend publication from private previews, placeholder hosts, dead links, or unrelated parent domains.
- Distinctive: line 71
Check the happy path, stop or refusal path, authority, artifact or effect, provenance, and recovery posture appropriate to the capability.
“Common” is measured: kept by at least 6 in 10 of the 16 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.
Files
Review Skill
Evaluate one skill from bounded evidence. The default runner passes a local
package to native runx.skill.validate, which parses and inspects the exact
package, runs read-only or planning harnesses with isolated receipts and no
operator credentials, and forwards that evidence to the focused assessment
runner. Execute-capable targets are inspected but never run automatically.
This skill does not mutate the package, publish a report, install a package, or
manufacture missing evidence. Use assess directly when a caller already has a
bounded evidence pack.
Procedure
- Resolve a workspace- or owning-skill-relative package path and capture its native capability and readiness envelope. Registry or marketplace material must first be installed or supplied as a bounded evidence pack; this skill does not fetch it implicitly.
- Run the native harness only when catalog execution is
readorplan. - Compare the documented capability with the inspected runner and catalog metadata in the evidence pack.
- Separate native harness results, provider readback, supplied assertions, and unverified claims.
- Check the happy path, refusal or stop path, authority boundary, artifact or effect, provenance, and recovery posture appropriate to the skill type.
- Return
needs_more_evidencewhen the evidence cannot support a trust decision. Never upgrade a parse result or prose claim into execution proof. - Recommend
adopt,adopt_with_caveats,improve, orreject, naming the evidence and blocking gaps behind the decision.
Stop conditions
- Refuse evidence containing secrets, raw credentials, private customer data, private inbox content, or provider dumps.
- Do not recommend provider readiness without provider readback.
- Do not recommend publication from private previews, placeholder hosts, dead links, or unrelated parent domains.
- Return
needs_more_evidencewhen no native inspection, harness, receipt, or equivalent bounded source evidence is supplied. - Reject capabilities that cannot be bounded, audited, or assigned a truthful terminal state.
Output
capability_profile: bounded capability, execution shape, and claimed effect.trust_assessment: evidence tier, caveats, and unsupported claims.test_matrix: passed, failed, skipped, and still-required checks.recommendation_report: decision, rationale, blockers, and next action.
Inputs
skill_ref(required): local package path for the default runner; any stable reference may label an evidence-onlyassessrun.evidence_pack(optional for the default runner, required forassess): inspection, harness, receipts, docs, or source evidence. References are preferable to copied private bodies.objective(optional): decision the evaluation should support.test_constraints(optional): time, environment, or safety limits.
Agent task contracts
review-skill-assess
Assess only the supplied evidence for one skill. Separate declared capability, native inspection, harness evidence, provider readback, supplied assertions, and unverified claims. Check the happy path, stop or refusal path, authority, artifact or effect, provenance, and recovery posture appropriate to the capability. Return needs_more_evidence when the packet cannot support a decision. Never infer provider readiness from a parse result, local supplied answer, or prose claim. Recommend adopt, adopt_with_caveats, improve, or reject with concrete blockers.
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
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.

