[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783KH6CANK632CVENF41QZ2":3,"skill-same:01M783KH6CANK632CVENF41QZ2":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M783KH6CANK632CVENF41QZ2","verified-tooling",null,"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","theselfruleorg\u002Fpolyrob","theselfruleorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128891129?v=4","01M783D1MFDP1D5ZXSNZMKHARH","01M783D1NEE9ATD39KJYCRR09J",12,"MIT","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fdata\u002Fprompts\u002Fskills\u002Fverified-tooling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: verified-tooling\ndescription: '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'\nlicense: MIT\nmetadata:\n  polyrob-when: 'Building a small read-only analysis tool to re-run'\n  polyrob-priority: '3'\n  polyrob-triggers: '{\"tool_ids\":[\"coding\",\"code_execution\"]}'\n  polyrob-version: '3'\n---\n# Verified Tooling — small tools you can trust twice\n\nWhen you need the same analysis more than once — a weekly summary of a log, a metric\ndiff between two exports, a check over a folder of records — build a small tool\ninstead of re-parsing by hand each session. Re-parsing by hand is not cheaper; it is\nthe same work with no record of whether you got it right last time.\n\nThe rules are about TRUST, not size.\n\n## The verbs\nBuild the tool with `coding_create_file` (or `filesystem_write_file` without\n`coding`), test it with `coding_run_tests`, and run it with\n`code_execution_run_code` or `shell_run` where that tool is loaded. Without a way to\nrun code, say so: a tool you cannot run is not verified.\n\n## The rules\n\n1. **Pure and read-only.** The tool reads a file and writes a report. No network,\n   no writes outside its output file, no side effects. Fetch live data separately\n   with the verbs and pass it in as an input file. A tool that reaches the network\n   cannot be re-run on yesterday's data to check yesterday's answer.\n\n2. **UNKNOWN is never zero.** If the input does not record a value as a clean\n   number, emit `null`\u002F`UNKNOWN` and EXCLUDE it from sums. A missing reading is not\n   a zero reading; a blank cell is not \"none\". A total that quietly absorbed an\n   unknown as 0 is wrong in the direction that looks responsible, which is the\n   worst direction.\n\n3. **One tool, one question.** `log_summary` (counts per level and per day),\n   `metric_diff` (added \u002F dropped \u002F changed between two exports),\n   `records_check` (rows that fail the schema). A tool that answers three questions\n   is three tools you cannot test.\n\n4. **Tests alongside, covering the parse edge cases.** Missing columns, an empty\n   file, a duplicate row, a malformed date, a value in the wrong unit. The edge\n   cases are the whole value: the happy path was never the thing you would have\n   got wrong.\n\n5. **Verify with a real run, then record it.** Append a dated entry to a\n   `SMOKE.md` next to the tool: the test count, the exact command, a summary of\n   the output, and an honest note on scope and limits. \"It works\" with no\n   command and no output is not a verification, and next month you cannot tell\n   whether it ever ran.\n\n6. **Cross-check overlapping totals.** If two tools compute figures that must\n   agree — a per-day total summed against a whole-period total — assert it.\n   Agreement between two independent paths is the strongest correctness evidence\n   available without an oracle.\n\n7. **Key rows by a stable identifier** (an id, an address, a path), never by a\n   display name: two records share a name more often than you expect.\n\n## What this is not\n\nIt is not a place to put an action. A tool that sends, spends or changes outside\nstate is not a small read-only tool, and none of the trust above transfers to it.\nActions go through their own verbs, with their gates and their caps, every time.\n","# Verified Tooling — small tools you can trust twice\n\nWhen you need the same analysis more than once — a weekly summary of a log, a metric\ndiff between two exports, a check over a folder of records — build a small tool\ninstead of re-parsing by hand each session. Re-parsing by hand is not cheaper; it is\nthe same work with no record of whether you got it right last time.\n\nThe rules are about TRUST, not size.\n\n## The verbs\nBuild the tool with `coding_create_file` (or `filesystem_write_file` without\n`coding`), test it with `coding_run_tests`, and run it with\n`code_execution_run_code` or `shell_run` where that tool is loaded. Without a way to\nrun code, say so: a tool you cannot run is not verified.\n\n## The rules\n\n1. **Pure and read-only.** The tool reads a file and writes a report. No network,\n   no writes outside its output file, no side effects. Fetch live data separately\n   with the verbs and pass it in as an input file. A tool that reaches the network\n   cannot be re-run on yesterday's data to check yesterday's answer.\n\n2. **UNKNOWN is never zero.** If the input does not record a value as a clean\n   number, emit `null`\u002F`UNKNOWN` and EXCLUDE it from sums. A missing reading is not\n   a zero reading; a blank cell is not \"none\". A total that quietly absorbed an\n   unknown as 0 is wrong in the direction that looks responsible, which is the\n   worst direction.\n\n3. **One tool, one question.** `log_summary` (counts per level and per day),\n   `metric_diff` (added \u002F dropped \u002F changed between two exports),\n   `records_check` (rows that fail the schema). A tool that answers three questions\n   is three tools you cannot test.\n\n4. **Tests alongside, covering the parse edge cases.** Missing columns, an empty\n   file, a duplicate row, a malformed date, a value in the wrong unit. The edge\n   cases are the whole value: the happy path was never the thing you would have\n   got wrong.\n\n5. **Verify with a real run, then record it.** Append a dated entry to a\n   `SMOKE.md` next to the tool: the test count, the exact command, a summary of\n   the output, and an honest note on scope and limits. \"It works\" with no\n   command and no output is not a verification, and next month you cannot tell\n   whether it ever ran.\n\n6. **Cross-check overlapping totals.** If two tools compute figures that must\n   agree — a per-day total summed against a whole-period total — assert it.\n   Agreement between two independent paths is the strongest correctness evidence\n   available without an oracle.\n\n7. **Key rows by a stable identifier** (an id, an address, a path), never by a\n   display name: two records share a name more often than you expect.\n\n## What this is not\n\nIt is not a place to put an action. A tool that sends, spends or changes outside\nstate is not a small read-only tool, and none of the trust above transfers to it.\nActions go through their own verbs, with their gates and their caps, every time.\n",{"name":5,"license":14,"metadata":23,"description":7},{"polyrob-when":24,"polyrob-version":25,"polyrob-priority":25,"polyrob-triggers":26},"Building a small read-only analysis tool to re-run","3","{\"tool_ids\":[\"coding\",\"code_execution\"]}","main","3a595c0e3db5aa91acc53dd80673c4d80e0721d1","data\u002Fprompts\u002Fskills\u002Fverified-tooling",2,"https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg","https:\u002F\u002Ftheselfrule.org","2026-11-14 16:54:43",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add theselfruleorg\u002Fpolyrob --skill verified-tooling",{"tool":41,"command":42},"bunx","bunx skills add theselfruleorg\u002Fpolyrob --skill verified-tooling",{"tool":44,"command":45},"pnpm","pnpm dlx skills add theselfruleorg\u002Fpolyrob --skill verified-tooling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fdata\u002Fprompts\u002Fskills\u002Fverified-tooling\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M783NSEPG1S13E7W3GEQMG6J","echo-basics","How to use the echo tool from the echo fixture pack.","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fpacks\u002Fecho\u002Fpolyrob_echo\u002Fskills\u002Fecho-basics\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M783NM911CND5PQCYDHA9GGV","x-engagement","Operate X account communication on the API rail (the captured-browser rail only where the owner chose it)—read inboxes, post\u002Freply, send DMs, set up the account, with the real write gates and completion evidence","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fpacks\u002Fx\u002Fpolyrob_x\u002Fskills\u002Fx-engagement\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M783NGQ43PGVT6F9XQR4ZNP2","social-discovery","Discover public X\u002Fsocial accounts and conversations with AnySite first (anysite_describe, then anysite_api), using native X account reads where they are authoritative and preserving write gates","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fpacks\u002Fx\u002Fpolyrob_x\u002Fskills\u002Fsocial-discovery\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M783NDAEPJT10SD3DNR56H96","polymarket-trading","GATED: place\u002Fcancel Polymarket orders. Owner-only, read-first, >$500 confirmation gate; references crypto-trading-safety","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fpacks\u002Fmarkets\u002Fpolyrob_markets\u002Fskills\u002Fpolymarket-trading\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M783N8GADTQMKKBQT4Z3JJ84","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","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fpacks\u002Fmarkets\u002Fpolyrob_markets\u002Fskills\u002Fpolymarket-portfolio-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M783N5KTTTRRRSM7XY8SY4NF","polymarket-market-research","Read Polymarket markets (discover, details, price as implied probability, orderbook, spread, volume) with no wallet","https:\u002F\u002Fgithub.com\u002Ftheselfruleorg\u002Fpolyrob\u002Fblob\u002Fmain\u002Fpacks\u002Fmarkets\u002Fpolyrob_markets\u002Fskills\u002Fpolymarket-market-research\u002FSKILL.md",[],[]]