verify-numbers
Skill0 starsChanged 3 months agoApache-2.0View on GitHub
Verify counts, deltas, estimates, remembered values, and time-window metrics before quoting them. Use when a number will anchor a recommendation, comparison, status report, or protocol artifact and its scope or method must be auditable.
In this repository5 other files it gives its agents.
- dispatch-briefSkill
- memory-lintSkill
- proof-before-doneSkill
- render-checkSkill
- usage-costSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before calculating, decide which label applies:
- Distinctive: line 21
Do not relabel an estimate as measured after rounding it or presenting it in a table.
- Distinctive: line 35
If those choices are unresolved, the count is not ready to quote.
- Distinctive: line 44
When counting line-shaped records, require a full-line match.
- Distinctive: line 71
Put the headline number first, then keep its basis beside it:
- Distinctive: line 92
Do not round measured counts, endpoints, or identifiers.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify Numbers
A number that affects a decision needs evidence proportionate to the claim. Do not let a plausible value, a remembered identifier, or a search result acquire the authority of a measurement merely because it is numeric.
Classify the claim
Before calculating, decide which label applies:
- Measured: observed from named inputs with an executed method.
- Calculated: derived from measured inputs with the arithmetic shown.
- Rough estimate: based on stated assumptions rather than complete inputs.
- Recalled: remembered or copied from prior context; re-verify before use.
Do not relabel an estimate as measured after rounding it or presenting it in a table.
Define the quantity
State the unit and scope before running a counter:
- What entity is counted: matching lines, regex matches, files, records, requests, bytes, or another unit?
- Which inputs are included and excluded?
- Which revision or snapshot is being measured?
- For a time series, what are the start and end instants, timezone, bucket semantics, and known coverage gaps?
If those choices are unresolved, the count is not ready to quote.
Measure and verify
- Execute the measurement against the named inputs. Preserve the command or calculation and the raw endpoints needed to reproduce it.
- For a regex count, choose the intended unit explicitly.
grep -candrg -ccount matching lines, not individual matches. Do not substitute one for the other silently. When counting line-shaped records, require a full-line match. From this skill directory, run:
python scripts/anchored_count.py \ --pattern '## Verified' \ path/to/file.mdThe helper applies the regex to each complete line and prints every matched path and line number. Use
--format jsonwhen another tool will consume the result.- Inspect the matched evidence. If the result is surprising or materially affects a decision, spot-check the source and use a second method with the same unit and scope.
- Measure both endpoints of a delta independently with the same method. Report
after - before; never infer an endpoint from the edit or carry it from memory. - Re-run recalled values and identifiers before putting them in a command, protocol message, or final report. After context compaction, reload the governing artifact rather than trusting the summary to preserve exact numbers.
Report the evidence
Reproduce the result in the reply. Do not make the reader recover the number from terminal output or open an evidence file just to learn the conclusion. Put the headline number first, then keep its basis beside it:
**Measured:** 12 matching lines.
- **Scope:** `docs/a.md` and `docs/b.md` at revision `<sha>`
- **Method:** `python scripts/anchored_count.py --pattern '...' <inputs>`
- **Evidence:** matched paths and line numbers from the command output
- **Caveat:** the named files were supplied explicitly; completeness was not checked
**Calculated:** 7 after - 5 before = +2, with both endpoints measured above.
**Rough estimate:** about 18 files = 3 directories x roughly 6 files each;
the directories have not been enumerated yet.For an estimate that anchors a decision, include the assumptions and a range or other uncertainty statement when the inputs support one. For a time-window claim, state the window and timezone beside the value and hedge if the data does not cover the full event period.
Do not round measured counts, endpoints, or identifiers. Round only when the result is explicitly approximate, and make the rounding visible. Surface only caveats that apply to the run. Do not call a result high, low, good, or bad unless the user requested that comparison and the benchmark is also defined and verified.
Limits
The helper proves only full-line regex counting over explicitly named UTF-8 files, with an optional leading byte-order mark. It treats LF as the physical line separator and normalizes CRLF; other Unicode separators remain content. It does not decide whether the files are the complete population, whether a record spans multiple lines, whether duplicated records should be deduplicated, or whether the resulting number supports the conclusion. Resolve those questions in the claim definition and report them as limitations.
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
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.

