agentsclimarketplace

Verify

Skill jschilli/argot/skills/verify

Produce empirical evidence that a claim holds — run tests, reproduce failures, probe blast radius, dogfood the artifact. Use when the user asks to verify, test, prove, reproduce, or confirm something works, and before any completion claim. Execute permission.From its SKILL.md

Install
npx -y skills add jschilli/argot --skill verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, as published. Nobody here has run it

verify — argot verb 5/7

Signature: Change or claim → Verdict (.argot/verdict-*.md + .json, schema: artifacts/verdict.schema.json): verified | refuted | inconclusive + attached evidence.

Envelope: execute (tests, runs, probes). Not a write verb — fixes discovered here go back through build.

Procedure

  1. State the claim precisely. "It works" is not a claim; "endpoint X returns 401 for scrubbed tokens" is.
  2. Choose probes that could fail: the falsifying test for the claimed mechanism, not a confirmation ritual. Prefer end-to-end evidence; name what's missing if blocked.
  3. Run them fresh. Recalled or assumed results don't count (fresh: true per probe).
  4. Probe the blast radius: what beyond the diff could this affect; probe the load-bearing ones; list the rest as unprobed.
  5. Emit the Verdict — including inconclusive when that's the truth. An honest inconclusive beats a confident wrong.

Contract

  • verify is self-evidence (the builder may verify its own work); it never substitutes for review (independent judgment). Ship-gates want both.
  • --loop until-<condition> is legal (e.g. until-green) — the stop condition must be falsifiable.
  • If verification reveals the plan or design is wrong, set back_pressure — dissent is a first-class output.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.