verifying — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited verifying (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Evidence before claims, always.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf you haven't run the verification command in this message, you cannot claim it passes.
BEFORE claiming any status:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifying| Claim | Requires | Not Sufficient |
|---|---|---|
| "Tests pass" | Test command output: 0 failures | Previous run, "should pass" |
| "Linter clean" | Linter output: 0 errors | Partial check |
| "Build succeeds" | Build command: exit 0 | Linter passing |
| "Bug fixed" | Test original symptom: passes | Code changed |
| "Feature complete" | Requirements checklist verified | Tests passing |
If you catch yourself:
STOP. Run the verification command.
| Excuse | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ tests |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial check is enough" | Partial proves nothing |
Tests:
Run test command → See: 34/34 pass → "All tests pass"
NOT: "Should pass now" / "Looks correct"Build:
Run build → See: exit 0 → "Build passes"
NOT: "Linter passed" (linter doesn't check compilation)Bug fix:
Reproduce bug → Apply fix → Test → Bug no longer occurs → "Fixed"
NOT: "Changed the code, should be fixed"Requirements:
Re-read requirements → Check each → Report gaps or completion
NOT: "Tests pass, must be done"# JavaScript/TypeScript
npm test # Run all tests
npm run build # Verify build
npm run lint # Check linting
# Python
pytest # Run all tests
python -m mypy . # Type checking
python -m build # Verify build
# Go
go test ./... # Run all tests
go build ./... # Verify build
# General
echo $? # Check last exit code (0 = success)ALWAYS before:
No shortcuts for verification.
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.