agentsclimarketplace

Eng verification

Skill tjboudreaux/cc-plugin-engineering-excellence/skills/eng-verification

Mandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.From its SKILL.md

Install
npx -y skills add tjboudreaux/cc-plugin-engineering-excellence --skill eng-verification

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

One thing to look at

  • 4 stars4 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

2.8 KB, as published. Nobody here has run it

Verification Before Completion

Overview

Claiming success without evidence is dishonesty, not efficiency. Every status report, “done,” or “tests pass” statement requires fresh verification.

Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you didn’t run the verifying command in this message, you cannot claim it passes.

Gate Function

1. IDENTIFY: Which command proves the claim?
2. RUN: Execute the full command now (fresh run).
3. READ: Inspect entire output & exit code.
4. VERIFY: Does output prove the claim?
   - If NO → report actual status with evidence
   - If YES → state claim WITH evidence (command + summary)
5. ONLY THEN: Make the claim

Skipping any step = lying.

Common Claims & Required Evidence

ClaimRequiredNot Enough
“Tests pass”Latest test command output showing 0 failuresPrevious run, “should pass”
“Lint clean”Linter command exit 0 nowPartial subset, inference
“Build works”Build command exit 0Linter pass
“Bug fixed”Reproduction test now passesCode diff only
“Regression test exists”Red→Green verified cycleTest created but never failed
“Agent succeeded”Inspect VCS diff + verify outputsAgent success message

Red Flags – STOP

  • Saying “should/probably/seems”
  • Expressing satisfaction before running verification
  • Planning to commit/push/PR without a fresh run
  • Trusting agent reports without checking
  • Partial verification (“just ran affected tests”)
  • “Just this once” or “I’m tired” rationalizations

Rationalization Rebuttals

ExcuseReality
“Should work now”Run the command
“I’m confident”Confidence ≠ evidence
“Just this once”No exceptions
“Agent said success”Verify independently
“Partial check is fine”Partial proves nothing
“I’m exhausted”Exhaustion isn’t evidence

Patterns

  • Tests: run and show X/Y passing output.
  • Regression tests: demonstrate fail (red), apply fix, pass (green), revert to confirm failure if necessary.
  • Requirements: re-read spec, create checklist, tick items with evidence.
  • Agent work: inspect actual diff, run verification yourself.

When to Apply

Always before:

  • Claiming completion/success
  • Expressing satisfaction (“Great! Done!”)
  • Moving to next task
  • Committing, pushing, or filing PRs
  • Delegating completion to others/agents

Bottom Line

Evidence precedes claims. Run the command, read the output, then speak. Anything else breaks trust.

Keep looking

Skills are one crate of 627,801. 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.