verified-tooling
How to build a small read-only analysis tool you can trust and re-run: one tool one question, pure and read-only, UNKNOWN is never zero, tests alongside, a real run recorded in a smoke log, and cross-checked totals
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 12
- Forks
- 2
01 前言 Front Matter
- name
- verified-tooling
- license
- MIT
- metadata
- { "polyrob-when": "Building a small read-only analysis tool to re-run", "polyrob-version": "3", "polyrob-priority": "3", "polyrob-triggers": "{\"tool_ids\":[\"coding\",\"code_execution\"]}" }
- description
- How to build a small read-only analysis tool you can trust and re-run: one tool one question, pure and read-only, UNKNOWN is never zero, tests alongside, a real run recorded in a smoke log, and cross-checked totals
03 SKILL.md 正文
Verified Tooling — small tools you can trust twice
When you need the same analysis more than once — a weekly summary of a log, a metric diff between two exports, a check over a folder of records — build a small tool instead of re-parsing by hand each session. Re-parsing by hand is not cheaper; it is the same work with no record of whether you got it right last time.
The rules are about TRUST, not size.
The verbs
Build the tool with coding_create_file (or filesystem_write_file without
coding), test it with coding_run_tests, and run it with
code_execution_run_code or shell_run where that tool is loaded. Without a way to
run code, say so: a tool you cannot run is not verified.
The rules
-
Pure and read-only. The tool reads a file and writes a report. No network, no writes outside its output file, no side effects. Fetch live data separately with the verbs and pass it in as an input file. A tool that reaches the network cannot be re-run on yesterday's data to check yesterday's answer.
-
UNKNOWN is never zero. If the input does not record a value as a clean number, emit
null/UNKNOWNand EXCLUDE it from sums. A missing reading is not a zero reading; a blank cell is not "none". A total that quietly absorbed an unknown as 0 is wrong in the direction that looks responsible, which is the worst direction. -
One tool, one question.
log_summary(counts per level and per day),metric_diff(added / dropped / changed between two exports),records_check(rows that fail the schema). A tool that answers three questions is three tools you cannot test. -
Tests alongside, covering the parse edge cases. Missing columns, an empty file, a duplicate row, a malformed date, a value in the wrong unit. The edge cases are the whole value: the happy path was never the thing you would have got wrong.
-
Verify with a real run, then record it. Append a dated entry to a
SMOKE.mdnext to the tool: the test count, the exact command, a summary of the output, and an honest note on scope and limits. "It works" with no command and no output is not a verification, and next month you cannot tell whether it ever ran. -
Cross-check overlapping totals. If two tools compute figures that must agree — a per-day total summed against a whole-period total — assert it. Agreement between two independent paths is the strongest correctness evidence available without an oracle.
-
Key rows by a stable identifier (an id, an address, a path), never by a display name: two records share a name more often than you expect.
What this is not
It is not a place to put an action. A tool that sends, spends or changes outside state is not a small read-only tool, and none of the trust above transfers to it. Actions go through their own verbs, with their gates and their caps, every time.
04 同仓库更多 Skills
echo-basics
How to use the echo tool from the echo fixture pack.
x-engagement
Operate X account communication on the API rail (the captured-browser rail only where the owner chose it)—read inboxes, post/reply, send DMs, set up the account, with the real write gates and completion evidence
social-discovery
Discover public X/social accounts and conversations with AnySite first (anysite_describe, then anysite_api), using native X account reads where they are authoritative and preserving write gates
polymarket-trading
GATED: place/cancel Polymarket orders. Owner-only, read-first, >$500 confirmation gate; references crypto-trading-safety
polymarket-portfolio-review
Read the configured Polymarket account's positions and trade history from the public Data API (no address parameter); summarize exposure and P&L
polymarket-market-research
Read Polymarket markets (discover, details, price as implied probability, orderbook, spread, volume) with no wallet