[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MM5EMFGZ8W211BHWQVNMEY":3,"skill-same:01M6MM5EMFGZ8W211BHWQVNMEY":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6MM5EMFGZ8W211BHWQVNMEY","principle-attack-the-premise",null,"Use after repeated fixes built on one shared theory of the cause keep failing at the same gate. Stop patching, state that theory in writing, and run a check whose result would change if the theory were wrong.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frequie\u002Fendostack\u002Fskills\u002Fprinciple-attack-the-premise\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"principle attack the premise","gate","failing","result","Wrong","fixes","at","true","keep","shared","writing","stop","use","check","patching","state","run","change","2026-11-10 10:12:30",false,"---\nname: principle-attack-the-premise\ndescription: Use after repeated fixes built on one shared theory of the cause keep failing at the same gate. Stop patching, state that theory in writing, and run a check whose result would change if the theory were wrong.\ndisable-model-invocation: true\n---\n\n# Attack the premise\n\nA second failure at the same check, from fixes built on one assumption, makes that assumption the suspect. Before you try a third variant, write the premise down and run an observation able to refute it.\n\n## When it applies\n\nTwo or more attempts that assumed the same cause have failed one gate (the same test, benchmark, or review criterion), and you are about to try a third variation.\n\nIt does not apply to a single failed fix, or to failures at unrelated gates with unrelated assumptions. The neighbouring principle, [principle-redesign-from-first-principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md), reshapes a design when a requirement changes. This one questions a factual assumption the existing design depends on.\n\n## What to do\n\n1. Write the premise as one sentence, in the reply or the decision log, where the user can read it. Example: \"The auth bypass in the agent's tool router comes from the regex allowlist missing a case.\"\n2. Design a discriminating observation, one whose result differs depending on whether the premise holds. For the example: log the exact tool name string that reached the router on the failing request. If it matches the allowlist exactly, the regex was never the problem.\n3. Look at the shape of the failures as well as their size. Which inputs, runs, or components fail, and does one participant always lose? A test that fails only on the webhook path, never the CLI, says more than a failure count.\n4. Make the check rerunnable as a script or a single command, per [principle-build-the-lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md), so a reviewer can reproduce your evidence.\n5. Act on the outcome. When the observation refutes the premise, look for the cause somewhere else: write down the traits the failing cases share that the premise failed to anticipate, and pursue those. When the observation confirms the premise, go one level deeper using [principle-fix-root-causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md); the previous attempts most likely patched a downstream effect.\n6. If the evidence shows a structural condition, such as one worker always finishing last or one service always reading stale config, remove the condition. Adding a mechanism that repairs the outcome afterward leaves the cause running and adds cost on every execution, which [principle-laziness-protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md) rules out.\n\n## The failure it prevents\n\nContinuing to iterate on a wrong diagnosis because of effort already spent, and stacking compensating patches in a place the evidence has ruled out.\n\n## Done when\n\nThe premise is written down and a discriminating observation has been run before any new fix begins. This is a hard gate.\n\nRelated: [principle-build-the-lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md), [principle-fix-root-causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md), [principle-laziness-protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md), [principle-redesign-from-first-principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md).\n","# Attack the premise\n\nA second failure at the same check, from fixes built on one assumption, makes that assumption the suspect. Before you try a third variant, write the premise down and run an observation able to refute it.\n\n## When it applies\n\nTwo or more attempts that assumed the same cause have failed one gate (the same test, benchmark, or review criterion), and you are about to try a third variation.\n\nIt does not apply to a single failed fix, or to failures at unrelated gates with unrelated assumptions. The neighbouring principle, [principle-redesign-from-first-principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md), reshapes a design when a requirement changes. This one questions a factual assumption the existing design depends on.\n\n## What to do\n\n1. Write the premise as one sentence, in the reply or the decision log, where the user can read it. Example: \"The auth bypass in the agent's tool router comes from the regex allowlist missing a case.\"\n2. Design a discriminating observation, one whose result differs depending on whether the premise holds. For the example: log the exact tool name string that reached the router on the failing request. If it matches the allowlist exactly, the regex was never the problem.\n3. Look at the shape of the failures as well as their size. Which inputs, runs, or components fail, and does one participant always lose? A test that fails only on the webhook path, never the CLI, says more than a failure count.\n4. Make the check rerunnable as a script or a single command, per [principle-build-the-lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md), so a reviewer can reproduce your evidence.\n5. Act on the outcome. When the observation refutes the premise, look for the cause somewhere else: write down the traits the failing cases share that the premise failed to anticipate, and pursue those. When the observation confirms the premise, go one level deeper using [principle-fix-root-causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md); the previous attempts most likely patched a downstream effect.\n6. If the evidence shows a structural condition, such as one worker always finishing last or one service always reading stale config, remove the condition. Adding a mechanism that repairs the outcome afterward leaves the cause running and adds cost on every execution, which [principle-laziness-protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md) rules out.\n\n## The failure it prevents\n\nContinuing to iterate on a wrong diagnosis because of effort already spent, and stacking compensating patches in a place the evidence has ruled out.\n\n## Done when\n\nThe premise is written down and a discriminating observation has been run before any new fix begins. This is a hard gate.\n\nRelated: [principle-build-the-lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md), [principle-fix-root-causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md), [principle-laziness-protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md), [principle-redesign-from-first-principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md).\n",{"name":5,"description":7,"disable-model-invocation":42},true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Frequie\u002Fendostack\u002Fskills\u002Fprinciple-attack-the-premise",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":42},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill principle-attack-the-premise",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill principle-attack-the-premise",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill principle-attack-the-premise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frequie\u002Fendostack\u002Fskills\u002Fprinciple-attack-the-premise\u002FSKILL.md",[],[67,77,85,93,101,109],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":76},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":76},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":76},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":76},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":76},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]