[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKV3QP1MW8CVR72BXF81MT":3,"skill-same:01M6KKV3QP1MW8CVR72BXF81MT":69},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6KKV3QP1MW8CVR72BXF81MT","component-poison",null,"Deliberately introduce a controlled number of specification\u002Fcode misalignments (\"poisons\") into a single Certus component on a throwaway branch, in order to test translation-verification tooling such as `component-check-spec-translation`. Each poison intentionally desynchronizes the component's `spec.md` from its implementation while keeping the code compiling. Use only for red-team \u002F evaluation of the audit skills, never on a branch intended to merge.","AI-native-Systems-Research\u002Fai-native-storage-certus","AI-native-Systems-Research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270755458?v=4","01M6KKQWSJX0D4X33E0KKSR4WM","AI-native Systems Research","01M6KKQWXTKR6MYVQMPKVJ5WD5",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002F.claude\u002Fskills\u002Fcomponent-poison\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"component","component poison","single","test","throwaway","for","number","name","as","translation","specification","only","never","use","check","branch","team","red-team","audit","verification","code","merge","2026-11-10 10:12:30",false,"---\nname: component-poison\ndescription: Deliberately introduce a controlled number of specification\u002Fcode misalignments (\"poisons\") into a single Certus component on a throwaway branch, in order to test translation-verification tooling such as `component-check-spec-translation`. Each poison intentionally desynchronizes the component's `spec.md` from its implementation while keeping the code compiling. Use only for red-team \u002F evaluation of the audit skills, never on a branch intended to merge.\nargument-hint: \"[component-name] [poison-count]\"\n---\n\n# Poison a Component\n\nThe purpose of this skill is to **test the translation-verification mechanisms** (e.g.\n`component-check-spec-translation`) by deliberately introducing known, controlled\nmismatches between a component's specification (`spec.md`) and its code. The audit skill\nshould then be able to detect these seeded mismatches.\n\nThis is a destructive, adversarial skill. It only ever operates on a dedicated\n`poison-\u003Ccomponent-name>` branch that is **not** meant to be merged. Do not run it on\n`unstable`, a feature branch you intend to ship, or any branch with uncommitted work you\ncare about.\n\nThe component name is `$0` and the number of poisons to introduce is `$1`.\n\n## 1. Resolve parameters\n\n1. If `$0` (component name) was not supplied, interactively ask the user which component to\n   poison and stop until provided.\n2. Resolve `$0` to exactly one component directory under `components\u002F` (the lower-case,\n   hyphen-ized form of the name, or the directory whose `define_component!` block declares\n   it). If it does not exist or is ambiguous, return an error and stop.\n3. Discover the component's specs with `rg --files \u003Ccomponent-dir>` and select files whose\n   path ends in `\u002Fspec.md` (support `specs\u002F\u003Cfeature>\u002Fspec.md` and\n   `.specify\u002Fspecs\u002F\u003Cfeature>\u002Fspec.md`, and deeper nesting). If **no** `spec.md` exists,\n   stop and report the searched path — there is nothing to misalign against.\n4. If `$1` (poison-count) was not supplied, interactively ask the user how many poisons to\n   introduce and stop until provided. Require a positive integer; reject `0` or negatives.\n\n## 2. Create and check out the poison branch\n\n1. Confirm the working tree is clean enough to proceed. If there are uncommitted changes\n   that would be swept onto the new branch, warn the user and ask whether to continue.\n2. Record the current branch as the base branch.\n3. Create a **new local branch derived from the current branch**, named\n   `poison-\u003Ccomponent-name>` (using the lower-case, hyphen-ized component name), and check\n   it out — e.g. `git checkout -b poison-eviction-policy-lru`. If a branch with that name\n   already exists, ask the user whether to delete and recreate it, or to append a numeric\n   suffix. Do not push this branch to any remote.\n\n## 3. Introduce `$1` poisons\n\nBuild a short inventory of the component's spec claims (requirements, interfaces,\nparameters, data types, defaults, constants, errors, semantics, exclusions) so each poison\ntargets a *specific, testable* claim. Then apply exactly `$1` distinct changes, each of\nwhich purposely mis-aligns `spec.md` and the code. Spread the poisons across different\nclaims and, where possible, across different poison categories below so the test exercises\nseveral detection paths.\n\nEach poison must fall into one of these categories (mix them; do not use the same category\nfor every poison):\n\n- **Remove functionality** — delete a function, branch, validation, or behavior that the\n  spec requires (spec still promises it; code no longer does it → *Missing*).\n- **Add unspecified functionality** — introduce behavior the spec never mentions: an unused\n  helper, a hidden \"backdoor\" code path, or writing state to a file\u002Fenv that the spec does\n  not describe (→ *Extra behavior*).\n- **Change syntax \u002F parameters** — alter a function signature, argument order, argument\n  count, or name away from what the spec documents (→ *Contradiction*).\n- **Change a data type** — change a field\u002Freturn\u002Fparameter type to one that mismatches the\n  type explicitly specified (e.g. `u32` where the spec says `u64`, `Option\u003CT>` vs `T`).\n- **Change semantics** — keep the signature but change what the function *does*: invert a\n  condition, change a default value, change rounding\u002Funits, weaken an error into a silent\n  success, or change ordering guarantees.\n- **Over-specify the spec** — add a new requirement, acceptance scenario, default, or\n  use-case to `spec.md` that the code does **not** implement (poisons the spec side rather\n  than the code side).\n\nGuidance for each poison:\n\n- Make it a *semantic* mismatch, not a cosmetic one. Renaming a private local or reflowing\n  comments will not exercise the audit. Target something the spec states as an observable\n  contract.\n- Keep each poison small and self-contained, and note the exact `path:line` on both the\n  spec side and the code side.\n- Prefer targeting distinct requirement IDs \u002F interfaces so the poisons are independently\n  detectable.\n\n## 4. Keep the code compiling\n\n**The code must still compile after all poison changes.** After applying the poisons,\nbuild the component and fix any compilation errors introduced by the poisons *without\nundoing the intended misalignment*:\n\n```bash\ncargo build -p \u003Ccrate-name>\n```\n\nIf a component is SPDK-gated and cannot be built in this environment, build with its\ndefault configuration and clearly note in the report that a full `--workspace` build was\nnot verified. If a poison cannot be made to compile without also removing the misalignment,\nback it out and choose a different poison so the final count of applied poisons still\nequals `$1` (or, if impossible, stop and report how many were successfully applied).\n\nDo **not** run formatters or linters that would \"helpfully\" reconcile the mismatch, and do\nnot run `component-sync-specs` or any spec-sync skill — that would defeat the purpose.\n\n## 5. Summarize the poisons\n\nWrite a `POISON.md` file in the component directory summarizing every applied change in a\ntable, so the poisons can later be compared against whatever the verification skill detects\n(the ground-truth key). Use this shape:\n\n```markdown\n# Poison Report\n\nComponent: \u003Ccomponent-dir>\nBase branch: \u003Cbase branch>\nPoison branch: poison-\u003Ccomponent-name>\nPoisons requested: \u003C$1>   Poisons applied: \u003CN>\nBuild verified: \u003Ccargo build -p \u003Ccrate> result \u002F caveat>\n\n> Generated by the `component-poison` skill to test translation-verification tooling.\n> This branch is intentionally broken and must not be merged.\n\n| # | Category | Side poisoned | Spec claim (path:line) | Code location (path:line) | What was changed | Expected audit result |\n|---|---|---|---|---|---|---|\n| 1 | Change data type | code | specs\u002F001-...\u002Fspec.md:88 | src\u002Flib.rs:142 | Return type `u64` → `u32` | Contradiction (High) |\n| 2 | Over-specify spec | spec | specs\u002F001-...\u002Fspec.md:120 (added) | (none) | Added FR for retry backoff not implemented | Missing (Medium) |\n```\n\nMap the \"Expected audit result\" column to the classifications the audit skill uses\n(*Aligned \u002F Partial \u002F Contradiction \u002F Missing \u002F Extra behavior \u002F Unverifiable*) so the\npoison report doubles as an answer key.\n\n## 6. Report\n\nPrint a concise summary to the user: the poison branch name, the base branch, how many\npoisons were applied (vs requested), whether the build passed, and the path to `POISON.md`.\nRemind the user this branch is intentionally broken, must not be merged, and that they can\nnow run `component-check-spec-translation` against the component to see how many poisons it\ncatches. Do not commit or push unless the user explicitly asks.\n","# Poison a Component\n\nThe purpose of this skill is to **test the translation-verification mechanisms** (e.g.\n`component-check-spec-translation`) by deliberately introducing known, controlled\nmismatches between a component's specification (`spec.md`) and its code. The audit skill\nshould then be able to detect these seeded mismatches.\n\nThis is a destructive, adversarial skill. It only ever operates on a dedicated\n`poison-\u003Ccomponent-name>` branch that is **not** meant to be merged. Do not run it on\n`unstable`, a feature branch you intend to ship, or any branch with uncommitted work you\ncare about.\n\nThe component name is `$0` and the number of poisons to introduce is `$1`.\n\n## 1. Resolve parameters\n\n1. If `$0` (component name) was not supplied, interactively ask the user which component to\n   poison and stop until provided.\n2. Resolve `$0` to exactly one component directory under `components\u002F` (the lower-case,\n   hyphen-ized form of the name, or the directory whose `define_component!` block declares\n   it). If it does not exist or is ambiguous, return an error and stop.\n3. Discover the component's specs with `rg --files \u003Ccomponent-dir>` and select files whose\n   path ends in `\u002Fspec.md` (support `specs\u002F\u003Cfeature>\u002Fspec.md` and\n   `.specify\u002Fspecs\u002F\u003Cfeature>\u002Fspec.md`, and deeper nesting). If **no** `spec.md` exists,\n   stop and report the searched path — there is nothing to misalign against.\n4. If `$1` (poison-count) was not supplied, interactively ask the user how many poisons to\n   introduce and stop until provided. Require a positive integer; reject `0` or negatives.\n\n## 2. Create and check out the poison branch\n\n1. Confirm the working tree is clean enough to proceed. If there are uncommitted changes\n   that would be swept onto the new branch, warn the user and ask whether to continue.\n2. Record the current branch as the base branch.\n3. Create a **new local branch derived from the current branch**, named\n   `poison-\u003Ccomponent-name>` (using the lower-case, hyphen-ized component name), and check\n   it out — e.g. `git checkout -b poison-eviction-policy-lru`. If a branch with that name\n   already exists, ask the user whether to delete and recreate it, or to append a numeric\n   suffix. Do not push this branch to any remote.\n\n## 3. Introduce `$1` poisons\n\nBuild a short inventory of the component's spec claims (requirements, interfaces,\nparameters, data types, defaults, constants, errors, semantics, exclusions) so each poison\ntargets a *specific, testable* claim. Then apply exactly `$1` distinct changes, each of\nwhich purposely mis-aligns `spec.md` and the code. Spread the poisons across different\nclaims and, where possible, across different poison categories below so the test exercises\nseveral detection paths.\n\nEach poison must fall into one of these categories (mix them; do not use the same category\nfor every poison):\n\n- **Remove functionality** — delete a function, branch, validation, or behavior that the\n  spec requires (spec still promises it; code no longer does it → *Missing*).\n- **Add unspecified functionality** — introduce behavior the spec never mentions: an unused\n  helper, a hidden \"backdoor\" code path, or writing state to a file\u002Fenv that the spec does\n  not describe (→ *Extra behavior*).\n- **Change syntax \u002F parameters** — alter a function signature, argument order, argument\n  count, or name away from what the spec documents (→ *Contradiction*).\n- **Change a data type** — change a field\u002Freturn\u002Fparameter type to one that mismatches the\n  type explicitly specified (e.g. `u32` where the spec says `u64`, `Option\u003CT>` vs `T`).\n- **Change semantics** — keep the signature but change what the function *does*: invert a\n  condition, change a default value, change rounding\u002Funits, weaken an error into a silent\n  success, or change ordering guarantees.\n- **Over-specify the spec** — add a new requirement, acceptance scenario, default, or\n  use-case to `spec.md` that the code does **not** implement (poisons the spec side rather\n  than the code side).\n\nGuidance for each poison:\n\n- Make it a *semantic* mismatch, not a cosmetic one. Renaming a private local or reflowing\n  comments will not exercise the audit. Target something the spec states as an observable\n  contract.\n- Keep each poison small and self-contained, and note the exact `path:line` on both the\n  spec side and the code side.\n- Prefer targeting distinct requirement IDs \u002F interfaces so the poisons are independently\n  detectable.\n\n## 4. Keep the code compiling\n\n**The code must still compile after all poison changes.** After applying the poisons,\nbuild the component and fix any compilation errors introduced by the poisons *without\nundoing the intended misalignment*:\n\n```bash\ncargo build -p \u003Ccrate-name>\n```\n\nIf a component is SPDK-gated and cannot be built in this environment, build with its\ndefault configuration and clearly note in the report that a full `--workspace` build was\nnot verified. If a poison cannot be made to compile without also removing the misalignment,\nback it out and choose a different poison so the final count of applied poisons still\nequals `$1` (or, if impossible, stop and report how many were successfully applied).\n\nDo **not** run formatters or linters that would \"helpfully\" reconcile the mismatch, and do\nnot run `component-sync-specs` or any spec-sync skill — that would defeat the purpose.\n\n## 5. Summarize the poisons\n\nWrite a `POISON.md` file in the component directory summarizing every applied change in a\ntable, so the poisons can later be compared against whatever the verification skill detects\n(the ground-truth key). Use this shape:\n\n```markdown\n# Poison Report\n\nComponent: \u003Ccomponent-dir>\nBase branch: \u003Cbase branch>\nPoison branch: poison-\u003Ccomponent-name>\nPoisons requested: \u003C$1>   Poisons applied: \u003CN>\nBuild verified: \u003Ccargo build -p \u003Ccrate> result \u002F caveat>\n\n> Generated by the `component-poison` skill to test translation-verification tooling.\n> This branch is intentionally broken and must not be merged.\n\n| # | Category | Side poisoned | Spec claim (path:line) | Code location (path:line) | What was changed | Expected audit result |\n|---|---|---|---|---|---|---|\n| 1 | Change data type | code | specs\u002F001-...\u002Fspec.md:88 | src\u002Flib.rs:142 | Return type `u64` → `u32` | Contradiction (High) |\n| 2 | Over-specify spec | spec | specs\u002F001-...\u002Fspec.md:120 (added) | (none) | Added FR for retry backoff not implemented | Missing (Medium) |\n```\n\nMap the \"Expected audit result\" column to the classifications the audit skill uses\n(*Aligned \u002F Partial \u002F Contradiction \u002F Missing \u002F Extra behavior \u002F Unverifiable*) so the\npoison report doubles as an answer key.\n\n## 6. Report\n\nPrint a concise summary to the user: the poison branch name, the base branch, how many\npoisons were applied (vs requested), whether the build passed, and the path to `POISON.md`.\nRemind the user this branch is intentionally broken, must not be merged, and that they can\nnow run `component-check-spec-translation` against the component to see how many poisons it\ncatches. Do not commit or push unless the user explicitly asks.\n",{"name":5,"description":7,"argument-hint":46},"[component-name] [poison-count]","unstable","dc564aa356769b7754391c9fa4fdaa0f179f476c",".claude\u002Fskills\u002Fcomponent-poison",4,"https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research","https:\u002F\u002Fai-native-systems-research.github.io\u002Fai-native-systems-research\u002F","2026-11-12 06:08:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-poison",{"tool":61,"command":62},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-poison",{"tool":64,"command":65},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-poison","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002F.claude\u002Fskills\u002Fcomponent-poison\u002FSKILL.md",true,[],[70,87,100,111,127,138],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":41},"01M6KP29TWSNGADF3AJ47BR7TY","tools-spin-sync","Synchronize Spin\u002FPromela models with current source code and re-verify","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[77,78,79,39,80,81,82,26,83,84,85,86],"tools spin sync","Tools","sync","verify","model","models","with","re","source","source code",{"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":41},"01M6KP277TDY3ZAJEBP5P6MDT8","tools-spin-model","Create a new Spin\u002FPromela formal verification model for a system property","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-model\u002FSKILL.md",[],[94,81,78,95,96,25,24,97,98,99,38],"tools spin model","system","formal verification","prove","new","create",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":41},"01M6KP250W406CEDSF02BRXT9D","tools-creusot-install","Install the Creusot Rust verification tool","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-install\u002FSKILL.md",[],[107,108,78,109,38,110],"tools creusot install","install","rust","tool",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":41},"01M6KP22H28FQ1X0V7VJHEFWXD","tools-creusot-init","Prepare an existing Cargo project to use Creusot formal verification","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-init\u002FSKILL.md",[],[118,78,119,120,121,122,123,38,32,96,124,125,126],"tools creusot init","init","project","directory","components","prepare","cargo","manager","Existing",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":41},"01M6KP1V506J9YM8DKKVDG1NRE","tools-creusot-coq-install","Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-coq-install\u002FSKILL.md",[],[134,135,108,78,24,126,27,136,38,137],"tools creusot coq install","Coq","installation","add",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":41},"01M6KP1PQJF3H765TYZAZ7P3EF","tools-creusot-annotate-interfaces","Formally verify a component's properties with Creusot and annotate its interface definitions","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-annotate-interfaces\u002FSKILL.md",[],[78,145,146,83,26,147,80,19,148],"tools creusot annotate interfaces","annotate","properties","interface"]