agentleFS
runxhqrunxhq/runx/skills/review-skill/SKILL.md

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

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
  1. Very specific:

    Run the native harness only when catalog execution is read or plan.

    line 24
  2. Distinctive:

    Check the happy path, refusal or stop path, authority boundary, artifact or effect, provenance, and recovery posture appropriate to the …

    line 29
  3. Distinctive:

    Do not recommend provider readiness without provider readback.

    line 40
  4. Distinctive:

    Do not recommend publication from private previews, placeholder hosts, dead links, or unrelated parent domains.

    line 41
  5. Distinctive:

    Check the happy path, stop or refusal path, authority, artifact or effect, provenance, and recovery posture appropriate to the capability.

    line 71

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. Run the native harness only when catalog execution is read or plan.
  3. Compare the documented capability with the inspected runner and catalog metadata in the evidence pack.
  4. Separate native harness results, provider readback, supplied assertions, and unverified claims.
  5. Check the happy path, refusal or stop path, authority boundary, artifact or effect, provenance, and recovery posture appropriate to the skill type.
  6. Return needs_more_evidence when the evidence cannot support a trust decision. Never upgrade a parse result or prose claim into execution proof.
  7. Recommend adopt, adopt_with_caveats, improve, or reject, 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_evidence when 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-only assess run.
  • evidence_pack (optional for the default runner, required for assess): 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.

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.