skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
hachej/boring-stack62 installs

verify-this

Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Use when asked to verify this, prove it works, did this fix it, or show the evidence.

How do I install this agent skill?

npx skills add https://github.com/hachej/boring-stack --skill verify-this
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides a structured workflow for verifying code changes and claims using local tests and metrics. It is a standard developer tool that executes local project commands.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Verify This

Adapted from Cursor's cursor-team-kit/verify-this (MIT, see THIRD_PARTY.md), with this app's surfaces.

Verification is not a recap. It proves or disproves a specific claim with repeatable evidence.

When To Use

  • The person asks "verify this", "prove it works", "did this fix it", or "show me the evidence".
  • A bug fix needs a before/after repro.
  • A page, API, agent-output or performance claim needs measurement.
  • A test passes but the user-visible behaviour still needs confirmation.

Do not use this for vague claims like "the code is cleaner". Ask for a measurable claim first.

Workflow

  1. Restate the claim in falsifiable form: condition, metric, and threshold.
  2. Pick the smallest local surface that can disprove it (below).
  3. Capture a baseline from the old state: the merge base, the parent commit, or the current broken repro (a git worktree of the base gets its own verify instance).
  4. Capture the treatment from the changed state with the same command, data and environment.
  5. Compare raw artifacts: numbers, snapshots, HTTP responses, run rows, eval tables.
  6. Return exactly one verdict: VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

Local surfaces in this app

  • Code behaviour: a focused unit test (node --test test/unit/<file>).
  • The page: the app's journey (npm run build && npm run journey, see boring-app-template), or a browser driver (control-ui) for snapshot, screenshot, network-summary, trace.
  • The API and the wire: verify api <path> before and after.
  • What an agent writes: run the app locally (npm run dev) and drive it, or the evals of hachej/boring-stack for the expert's skill.
  • Performance: verify perf, or timings from the same machine for baseline and treatment.

Verdict Rules

  • VERIFIED: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound.
  • NOT VERIFIED: the behaviour is unchanged, moves the wrong way, or misses the threshold.
  • INCONCLUSIVE: no valid baseline, noisy signal (agent outputs on 3 cases are noisy), failed measurement, or an environment difference invalidates the comparison.

Output

VERIFIED | NOT VERIFIED | INCONCLUSIVE
Claim: <falsifiable claim>

Evidence:
<metric/artifact>: baseline=<...>, treatment=<...>, delta=<...>, threshold=<...>

Reasoning:
<one tight paragraph naming the evidence and any confounds>

Do not soften a negative result. A clear NOT VERIFIED is useful. Never put real user data in an artifact you commit.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/hachej/boring-stack/verify-this">View verify-this on skillZs</a>