[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KNRE464NHN09N8JPRADGJ4":3,"skill-same:01M6KNRE464NHN09N8JPRADGJ4":54},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6KNRE464NHN09N8JPRADGJ4","component-check-leakage",null,"Checks that any component that is being used by another component is only accessed through the component's interface and does not interact directly with the struct.","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\u002Fcomponents\u002Fremote-lookup-rdma-responder\u002F.claude\u002Fskills\u002Fcomponent-check-leakage\u002FSKILL.md",[],[19,20,21,22,23,24,25],"component","check","component check leakage","only","name","with","interface","2026-11-10 10:12:30",false,"---\nname: component-check-leakage\ndescription: Checks that any component that is being used by another component is only accessed through the component's interface and does not interact directly with the struct.\nargument-hint: \"[component-name, component-name, ...]\"\n---\n\n# Component Leakage Check\n\nThis skill audits the codebase for **abstraction leakage** — cases where a component's concrete struct is used directly by another component instead of being accessed through its interface trait.\n\n## The Rule\n\nEach component in `components\u002F` exposes:\n- A **concrete struct** (e.g., `LoggerComponent`, `HelloWorldComponent`) — the implementation detail.\n- An **interface trait** in `components\u002Finterfaces\u002F` (e.g., `ILogger`, `IGreeter`) — the public contract.\n\nWhen component A consumes component B, it must only interact through B's interface. Direct use of B's struct is leakage.\n\n**Violation (leakage):**\n```rust\nuse logger::LoggerComponent;                          \u002F\u002F importing struct from another component\nlet logger = Arc::new(LoggerComponent::new_default()); \u002F\u002F constructing it\nlet logger: Arc\u003CLoggerComponent> = ...;               \u002F\u002F holding a typed reference to the struct\n```\n\n**Correct (interface only):**\n```rust\nuse interfaces::ILogger;\n\u002F\u002F logger injected via receptacle, typed as Arc\u003Cdyn ILogger + Send + Sync>\n```\n\n## Scope and Exceptions\n\n- **Components under `components\u002F`** are subject to this rule (excluding `interfaces\u002F` and `component-framework\u002F`).\n- **Apps under `apps\u002F`** are wiring points — they legitimately instantiate concrete structs. Flag them only as a note, not a violation.\n- **Unit test files** (`#[cfg(test)]` blocks and files in `tests\u002F`) may use concrete structs for test fixtures. These are warnings, not errors.\n- **A component's own source files** constructing its own struct are fine — a component knows its own type.\n- **Dynamic loading entry points** (`extern \"C\" fn create_component`) constructing and returning the struct as a trait object are fine.\n\n## Detection Strategy\n\nFor each component under investigation (all components if no `$ARGUMENTS`, otherwise only those named):\n\n### Step 1 — Identify the component's concrete struct name\n\nRead the `define_component!` macro invocation in the component's `src\u002Flib.rs`. The struct name is the identifier immediately following `pub` in the macro body (e.g., `pub LoggerComponent { ... }`).\n\n### Step 2 — Find all other components that list it as a Cargo dependency\n\nSearch all `Cargo.toml` files under `components\u002F` and `apps\u002F` for a dependency entry whose crate name matches the component being checked. Use the package name (hyphenated) from the component's `Cargo.toml` `[package]` section.\n\n### Step 3 — Check each dependent crate's source for leakage\n\nFor each crate that lists the target component as a dependency, grep its source files (`src\u002F**\u002F*.rs`) for:\n\n1. **Direct import of the struct:**\n   ```\n   use \u003Ccrate_name>::\u003CStructName>\n   use \u003Ccrate_name>::{..., \u003CStructName>, ...}\n   ```\n2. **Qualified path usage:**\n   ```\n   \u003Ccrate_name>::\u003CStructName>::\n   Arc\u003Cdyn ... | Arc\u003C\u003CStructName>>   (type annotations containing the struct)\n   ```\n3. **Type annotations holding the struct** (not behind `dyn`):\n   ```\n   : Arc\u003C\u003CStructName>>\n   : \u003CStructName>\n   ```\n\nExclude matches in:\n- The component's own `src\u002F` files (self-reference)\n- Lines inside `#[cfg(test)]` modules and `tests\u002F` directories (mark separately as warnings)\n- `apps\u002F` crates (mark separately as notes)\n\n### Step 4 — Identify the correct interface\n\nCross-reference `components\u002Finterfaces\u002Fsrc\u002Flib.rs` to find which interface trait(s) the component provides (look for `use \u003Ccrate>::...; pub use` re-exports or the trait definitions). This helps frame the fix suggestion.\n\n### Step 5 — Report\n\nFor each component checked, output a structured report:\n\n```\n## \u003CComponentName> (crate: \u003Ccrate-name>)\n\n### Violations (must fix)\n- \u003Cfile>:\u003Cline> — \u003Cdependent-crate> uses `\u003CStructName>` directly\n  Fix: replace with `Arc\u003Cdyn \u003CIInterface> + Send + Sync>` via receptacle\n\n### Warnings (test code — consider fixing)\n- \u003Cfile>:\u003Cline> — test uses `\u003CStructName>` directly\n\n### Notes (apps — acceptable but review)\n- \u003Cfile>:\u003Cline> — app wiring uses `\u003CStructName>` to construct and bind\n\n### Clean ✓\nNo leakage found.\n```\n\nIf `$ARGUMENTS` are provided, only check components whose names (case-insensitive, hyphen\u002Funderscore normalised) appear in the argument list. Otherwise check all components.\n\nAt the end, print a summary line: `N violation(s) across M component(s)`.\n\n## Example Run\n\n```\n\u002Fcomponent-check-leakage logger\n```\n\nExpected: finds that `gpu-services` uses `LoggerComponent` directly in `src\u002Flib.rs` (tests) and `src\u002Fbin\u002Fp2p_server.rs` (main code), reports violations and suggests using `ILogger` via a receptacle instead.\n","# Component Leakage Check\n\nThis skill audits the codebase for **abstraction leakage** — cases where a component's concrete struct is used directly by another component instead of being accessed through its interface trait.\n\n## The Rule\n\nEach component in `components\u002F` exposes:\n- A **concrete struct** (e.g., `LoggerComponent`, `HelloWorldComponent`) — the implementation detail.\n- An **interface trait** in `components\u002Finterfaces\u002F` (e.g., `ILogger`, `IGreeter`) — the public contract.\n\nWhen component A consumes component B, it must only interact through B's interface. Direct use of B's struct is leakage.\n\n**Violation (leakage):**\n```rust\nuse logger::LoggerComponent;                          \u002F\u002F importing struct from another component\nlet logger = Arc::new(LoggerComponent::new_default()); \u002F\u002F constructing it\nlet logger: Arc\u003CLoggerComponent> = ...;               \u002F\u002F holding a typed reference to the struct\n```\n\n**Correct (interface only):**\n```rust\nuse interfaces::ILogger;\n\u002F\u002F logger injected via receptacle, typed as Arc\u003Cdyn ILogger + Send + Sync>\n```\n\n## Scope and Exceptions\n\n- **Components under `components\u002F`** are subject to this rule (excluding `interfaces\u002F` and `component-framework\u002F`).\n- **Apps under `apps\u002F`** are wiring points — they legitimately instantiate concrete structs. Flag them only as a note, not a violation.\n- **Unit test files** (`#[cfg(test)]` blocks and files in `tests\u002F`) may use concrete structs for test fixtures. These are warnings, not errors.\n- **A component's own source files** constructing its own struct are fine — a component knows its own type.\n- **Dynamic loading entry points** (`extern \"C\" fn create_component`) constructing and returning the struct as a trait object are fine.\n\n## Detection Strategy\n\nFor each component under investigation (all components if no `$ARGUMENTS`, otherwise only those named):\n\n### Step 1 — Identify the component's concrete struct name\n\nRead the `define_component!` macro invocation in the component's `src\u002Flib.rs`. The struct name is the identifier immediately following `pub` in the macro body (e.g., `pub LoggerComponent { ... }`).\n\n### Step 2 — Find all other components that list it as a Cargo dependency\n\nSearch all `Cargo.toml` files under `components\u002F` and `apps\u002F` for a dependency entry whose crate name matches the component being checked. Use the package name (hyphenated) from the component's `Cargo.toml` `[package]` section.\n\n### Step 3 — Check each dependent crate's source for leakage\n\nFor each crate that lists the target component as a dependency, grep its source files (`src\u002F**\u002F*.rs`) for:\n\n1. **Direct import of the struct:**\n   ```\n   use \u003Ccrate_name>::\u003CStructName>\n   use \u003Ccrate_name>::{..., \u003CStructName>, ...}\n   ```\n2. **Qualified path usage:**\n   ```\n   \u003Ccrate_name>::\u003CStructName>::\n   Arc\u003Cdyn ... | Arc\u003C\u003CStructName>>   (type annotations containing the struct)\n   ```\n3. **Type annotations holding the struct** (not behind `dyn`):\n   ```\n   : Arc\u003C\u003CStructName>>\n   : \u003CStructName>\n   ```\n\nExclude matches in:\n- The component's own `src\u002F` files (self-reference)\n- Lines inside `#[cfg(test)]` modules and `tests\u002F` directories (mark separately as warnings)\n- `apps\u002F` crates (mark separately as notes)\n\n### Step 4 — Identify the correct interface\n\nCross-reference `components\u002Finterfaces\u002Fsrc\u002Flib.rs` to find which interface trait(s) the component provides (look for `use \u003Ccrate>::...; pub use` re-exports or the trait definitions). This helps frame the fix suggestion.\n\n### Step 5 — Report\n\nFor each component checked, output a structured report:\n\n```\n## \u003CComponentName> (crate: \u003Ccrate-name>)\n\n### Violations (must fix)\n- \u003Cfile>:\u003Cline> — \u003Cdependent-crate> uses `\u003CStructName>` directly\n  Fix: replace with `Arc\u003Cdyn \u003CIInterface> + Send + Sync>` via receptacle\n\n### Warnings (test code — consider fixing)\n- \u003Cfile>:\u003Cline> — test uses `\u003CStructName>` directly\n\n### Notes (apps — acceptable but review)\n- \u003Cfile>:\u003Cline> — app wiring uses `\u003CStructName>` to construct and bind\n\n### Clean ✓\nNo leakage found.\n```\n\nIf `$ARGUMENTS` are provided, only check components whose names (case-insensitive, hyphen\u002Funderscore normalised) appear in the argument list. Otherwise check all components.\n\nAt the end, print a summary line: `N violation(s) across M component(s)`.\n\n## Example Run\n\n```\n\u002Fcomponent-check-leakage logger\n```\n\nExpected: finds that `gpu-services` uses `LoggerComponent` directly in `src\u002Flib.rs` (tests) and `src\u002Fbin\u002Fp2p_server.rs` (main code), reports violations and suggests using `ILogger` via a receptacle instead.\n",{"name":5,"description":7,"argument-hint":31},"[component-name, component-name, ...]","unstable","dc564aa356769b7754391c9fa4fdaa0f179f476c","components\u002Fremote-lookup-rdma-responder\u002F.claude\u002Fskills\u002Fcomponent-check-leakage",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-check-leakage",{"tool":46,"command":47},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-check-leakage",{"tool":49,"command":50},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill component-check-leakage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fremote-lookup-rdma-responder\u002F.claude\u002Fskills\u002Fcomponent-check-leakage\u002FSKILL.md",true,[],[55,72,88,99,116,128],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":26},"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",[],[62,63,64,65,66,67,68,23,24,69,70,71],"tools spin sync","Tools","sync","code","verify","model","models","re","source","source code",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":26},"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",[],[79,67,63,80,81,82,83,84,85,86,87],"tools spin model","system","formal verification","number","for","prove","new","create","verification",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":26},"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",[],[95,96,63,97,87,98],"tools creusot install","install","rust","tool",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":26},"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",[],[106,63,107,108,109,110,111,87,112,81,113,114,115],"tools creusot init","init","project","directory","components","prepare","use","cargo","manager","Existing",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":26},"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",[],[123,124,96,63,83,115,125,126,87,127],"tools creusot coq install","Coq","as","installation","add",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":26},"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",[],[63,135,136,24,23,137,66,19,25],"tools creusot annotate interfaces","annotate","properties"]