[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A98P3F2631S441GYEP024N":3,"skill-same:01M7A98P3F2631S441GYEP024N":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A98P3F2631S441GYEP024N","false-competence-check",null,"Check finished-looking agent work against the failure modes that look like competence but are not. Use before declaring a fix done, before opening or approving a PR, when a change was fast and confident, when tests are green on the first try, after a rename, sweep, or cleanup, or when reviewing another agent's \"done\" claim. Do not use as a substitute for the task's own acceptance criteria.","SVRN-AGNT\u002FDale-OS","SVRN-AGNT","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F295947566?v=4","01M7A911BWXPQ54YJCK5G6B9EP","SVRN AGNT","01M7A911CFN8Q6RP4DE9MAM81M",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Ffalse-competence-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: false-competence-check\ndescription: Check finished-looking agent work against the failure modes that look like competence but are not. Use before declaring a fix done, before opening or approving a PR, when a change was fast and confident, when tests are green on the first try, after a rename, sweep, or cleanup, or when reviewing another agent's \"done\" claim. Do not use as a substitute for the task's own acceptance criteria.\n---\n\n# False Competence Check\n\n## Rule\n\n**The most expensive mistakes look like good work.**\n\nDecisiveness, speed, cleanup, diligence, and confidence each have a counterfeit. The counterfeit passes casual review because it has the shape of the real thing.\n\n## The counterfeits\n\n| Looks like | Actually | Counter-procedure |\n|---|---|---|\n| Decisiveness | Implementing from stale premises | A prior audit is a hypothesis. Re-locate every symbol by content before building on it. |\n| Speed | A shallow search-based fix | A rename searches the entire file, including templates. Claims about large files need uncapped searches and reading every hit. |\n| A quick win | A visual fix that dodges the data | Identify the mechanism (paint order, clipping, scale, data truth) before choosing the fix class. A wrong number is withheld or labelled, never dressed. |\n| Craftsmanship | A broad refactor disguised as cleanup | Scope out adjacent ugliness. Use anchored edits and verify with counts and a parse. A partial sweep is worse than none. |\n| Diligence | Tests that bless the bug | Break the fix and watch the test fail. When a test encodes current behaviour, ask whether that behaviour is the bug. |\n| Generosity | A PR with hidden unrelated diffs | Diff from the merge base. Every hunk traces to scope-in; incidental fixes get their own commit and a line in the report. |\n| Confidence | False verification | Verify in the environment class where the code runs. Compare suite results against a clean tree. Count deliverables explicitly; search your own diff for placeholders. |\n| Completeness | One instance fixed, pattern not hunted | Search every surface that reads the same data or renders the same pattern before declaring done. |\n| Progress | Fixing the wrong link in the chain | Trace the whole pipeline first. When a feature yields nothing, check the wiring before the producer. |\n| Finished | A code fix presented as data repair | Corrected code does not repair rows it already wrote. Data repair is a separate, dry-run-first, owner-gated path. |\n| Defensiveness | Safety relief keyed to a label | Key relief to the degraded condition itself and test the success-with-degraded-inputs path. |\n| Validation | Model-generated values passing value-blind guards | Overwrite system-owned fields at the trusted boundary. Validate claimed values against the canonical source. Print \"unavailable\", never a synthetic zero. |\n| Consistency | Grandfathered violations reused as precedent | Ratchets only go down. New code meets the current standard even inside old files. |\n\n## Workflow\n\n1. Name which counterfeit your current work most resembles.\n2. Run the one additional check that would falsify the resemblance.\n3. Report the check and its result, not the reassurance.\n\n## Falsify it\n\nAsk: \"Which of these does my diff most resemble, and what single check would prove it is not that?\" If you cannot name the check, you have not ruled it out.\n\n## Stop conditions\n\n- The falsifying check requires access or authority the task does not have.\n- The check fails and fixing it would broaden scope beyond the charter.\n\nReport the resemblance and the blocked check rather than claiming done.\n\n## Output\n\nCLOSEST COUNTERFEIT · FALSIFYING CHECK · RESULT · RESIDUAL RISK.\n","# False Competence Check\n\n## Rule\n\n**The most expensive mistakes look like good work.**\n\nDecisiveness, speed, cleanup, diligence, and confidence each have a counterfeit. The counterfeit passes casual review because it has the shape of the real thing.\n\n## The counterfeits\n\n| Looks like | Actually | Counter-procedure |\n|---|---|---|\n| Decisiveness | Implementing from stale premises | A prior audit is a hypothesis. Re-locate every symbol by content before building on it. |\n| Speed | A shallow search-based fix | A rename searches the entire file, including templates. Claims about large files need uncapped searches and reading every hit. |\n| A quick win | A visual fix that dodges the data | Identify the mechanism (paint order, clipping, scale, data truth) before choosing the fix class. A wrong number is withheld or labelled, never dressed. |\n| Craftsmanship | A broad refactor disguised as cleanup | Scope out adjacent ugliness. Use anchored edits and verify with counts and a parse. A partial sweep is worse than none. |\n| Diligence | Tests that bless the bug | Break the fix and watch the test fail. When a test encodes current behaviour, ask whether that behaviour is the bug. |\n| Generosity | A PR with hidden unrelated diffs | Diff from the merge base. Every hunk traces to scope-in; incidental fixes get their own commit and a line in the report. |\n| Confidence | False verification | Verify in the environment class where the code runs. Compare suite results against a clean tree. Count deliverables explicitly; search your own diff for placeholders. |\n| Completeness | One instance fixed, pattern not hunted | Search every surface that reads the same data or renders the same pattern before declaring done. |\n| Progress | Fixing the wrong link in the chain | Trace the whole pipeline first. When a feature yields nothing, check the wiring before the producer. |\n| Finished | A code fix presented as data repair | Corrected code does not repair rows it already wrote. Data repair is a separate, dry-run-first, owner-gated path. |\n| Defensiveness | Safety relief keyed to a label | Key relief to the degraded condition itself and test the success-with-degraded-inputs path. |\n| Validation | Model-generated values passing value-blind guards | Overwrite system-owned fields at the trusted boundary. Validate claimed values against the canonical source. Print \"unavailable\", never a synthetic zero. |\n| Consistency | Grandfathered violations reused as precedent | Ratchets only go down. New code meets the current standard even inside old files. |\n\n## Workflow\n\n1. Name which counterfeit your current work most resembles.\n2. Run the one additional check that would falsify the resemblance.\n3. Report the check and its result, not the reassurance.\n\n## Falsify it\n\nAsk: \"Which of these does my diff most resemble, and what single check would prove it is not that?\" If you cannot name the check, you have not ruled it out.\n\n## Stop conditions\n\n- The falsifying check requires access or authority the task does not have.\n- The check fails and fixing it would broaden scope beyond the charter.\n\nReport the resemblance and the blocked check rather than claiming done.\n\n## Output\n\nCLOSEST COUNTERFEIT · FALSIFYING CHECK · RESULT · RESIDUAL RISK.\n",{"name":5,"description":7},"main","3f34ad663c72d0d757cfcad2d5b970069eb47675","skills\u002Foperator\u002Ffalse-competence-check",0,"https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT","2026-11-14 13:35:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add SVRN-AGNT\u002FDale-OS --skill false-competence-check",{"tool":37,"command":38},"bunx","bunx skills add SVRN-AGNT\u002FDale-OS --skill false-competence-check",{"tool":40,"command":41},"pnpm","pnpm dlx skills add SVRN-AGNT\u002FDale-OS --skill false-competence-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Ffalse-competence-check\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",118,"https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Ffalse-competence-check\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7A9B1KY6ZAHBV35DTMJ9209","verify-before-cite","Live-verify work state before reporting or relying on it, and reconcile every place that state is recorded. Use before a status report, standup, handoff, or \"what's open\" answer; when a tracker, queue, memory note, or prior session says something is pending, merged, shipped, or blocked; after any merge, release, or promotion; or when records in two places disagree. Do not use to judge whether a claim about data or numbers is proven.","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Fverify-before-cite\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7A9AXKQRJJT2VA12SGYT46N","truth-boundary","Enforce provenance and uncertainty boundaries. Use when a system mixes observed, authoritative, user-attested, derived, estimated, inferred, reconstructed, or unknown values; when missing data could become zero; or when downstream output may overstate certainty. Also use when told to fill a missing, failed, or empty value with zero, a default, or a guess so the work can keep going.","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Ftruth-boundary\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7A9AR7WBVE1ZKV9B6HX9R53","systemic-bug-instinct","Use first, before reading, searching or editing code, whenever a defect, wrong value or balance, stale state, edge-case failure, broken workflow, or misleading UI is reported and a fix is requested, even when the request names the one file to patch. Diagnoses the bug as a possibly systemic failure to find the root mechanism, failure class, blast radius across sibling consumers, fix location, and regression guard. Do not use for a one-line typo or syntax fix, for two components that disagree about one concept (use seam-audit), for a dense screen whose value may be a presentation problem (use operator-ui-audit), or for financial records that contradict each other (use accounting-integrity).","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Fsystemic-bug-instinct\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7A9AJ6FC5M0EKDMCY6V654E","swarm","Design and run the smallest effective multi-agent harness for complex work. Use when the user explicitly says SWARM or asks for a swarm, multi-agent workflow, adaptive orchestration, harness design, parallel investigation, independent falsification, architecture reconciliation, broad audit, competing root-cause hypotheses, or high-risk work that benefits from independent reasoning lanes. Do not use for trivial edits or linear tasks one agent can complete cheaply; the best swarm may use zero subagents. SWARM grants orchestration, not broader implementation, merge, deploy, credential, financial, or destructive authority.","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Fswarm\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A9ACCQJ2DXVKN1TD84N6EJ","shipping-lanes","Design, run, or adopt a pipeline in which agent-written changes are reviewed and merged without a person in the routine loop, with review and landing matched to each change's risk. Use when setting up or changing how PRs get reviewed and merged by agents; when every change waits on one person, or none gets reviewed; when a reviewer is only reached if the author asks for it; when docs and permission changes take the same path; or when bringing a new repository onto the shared shipping system. Do not use to decide whether one specific merge is authorised (use merge-authority), to judge a finished-looking result (use false-competence-check), or to prove a single guard is reached (use reachability-proof).","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Fshipping-lanes\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7A9A4S86CA51DRPZ3SS38M7","seam-audit","Audit the boundary where two components represent the same concept, because each side can pass its own tests while the combined system is wrong. Use when a value looks coherent but is wrong, when a projection or compatibility view stands in for a full record, when sync or merge involves deletes, when status codes or result shapes cross a boundary, or when \"unknown\" may become zero, false, or success as it crosses between two components. Do not use for a defect inside one component (use systemic-bug-instinct), for grading one claim's certainty (use truth-boundary), or for a financial repair's preview and commit (use ledger-repair).","https:\u002F\u002Fgithub.com\u002FSVRN-AGNT\u002FDale-OS\u002Fblob\u002Fmain\u002Fskills\u002Foperator\u002Fseam-audit\u002FSKILL.md",[],[]]