[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BH50THYQKDFY428RP08JZX":3,"skill-same:01M7BH50THYQKDFY428RP08JZX":98},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7BH50THYQKDFY428RP08JZX","rust-craft",null,"Craft production Rust the way the top toolchain teams do. Use when writing, reviewing, or restructuring Rust — workspace layout, Cargo manifests, lints, and profiles; type, trait, and error API design; performance, allocation, and profiling work; async and concurrency; CLI construction; test, snapshot, and benchmark suites; crate selection; release, semver, MSRV, and feature flags.","hadronomy\u002Fskills","hadronomy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17086478?v=4","01M7BH4GMWYV32S7AXN0AYYRZC","Pablo Hernández","01M7BH4GP7A5Z0MQX2JNY7BGJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rust-craft\ndescription: Craft production Rust the way the top toolchain teams do. Use when writing, reviewing, or restructuring Rust — workspace layout, Cargo manifests, lints, and profiles; type, trait, and error API design; performance, allocation, and profiling work; async and concurrency; CLI construction; test, snapshot, and benchmark suites; crate selection; release, semver, MSRV, and feature flags.\n---\n\n# Rust Craft\n\nWrite Rust that is correct before it is fast, measured before it is called fast,\nand shaped so that every call path is obvious to the next reader.\n\nThe rules here are taken from the codebases that set the bar: `oxc`,\n`ruff`\u002F`ty`, `uv`, `mise`, `rust-analyzer`, and the official API guidelines.\nRead [references\u002Fsources.md](references\u002Fsources.md) when you need to check why a\nrule exists.\n\nThis is a routed skill. Always apply the core contract. Read only the reference\nlayers the task needs.\n\n## Core contract\n\n1. **The checkout is the authority.** Before you write a line, read\n   `Cargo.toml`, `rust-toolchain.toml`, `clippy.toml`, `rustfmt.toml`,\n   `AGENTS.md`, and two files next to the one you will change. Repo convention\n   beats every default in this skill.\n2. **Encode constraints in types.** Keep `panic!`, `unreachable!`, `unwrap`,\n   `expect`, and `todo!` out of library and binary code. Use `if let`, let\n   chains, `let ... else`, and newtypes that cannot hold a bad value. Verbose\n   code that removes a panic is the better trade.\n3. **Parse at the edge.** Convert untrusted input into a validated type once, at\n   the boundary. Past that point, only the validated type exists.\n4. **Never silence a lint to make the build pass.** Refactor instead. If a lint\n   must go, write `#[expect(lint, reason = \"...\")]` on the smallest possible\n   scope. Do not use `#[allow]`, a workspace `allow`, or `-A` on the command\n   line.\n5. **Every `unsafe` block carries a `\u002F\u002F SAFETY:` comment** that names the\n   invariant it depends on. Do not reach for `unsafe` to gain speed you have not\n   measured.\n6. **Imports go at the top of the file.** No `use` inside a function body. Use a\n   fully qualified path only for a name you write once.\n7. **Write full names.** `version`, not `ver`. `requires_python`, not `rp`.\n8. **Comments state invariants and reasons.** They never narrate the code and\n   never record what the code used to do.\n9. **Measure before you optimize, and again after.** A speed claim without a\n   benchmark number is not a claim.\n10. **Run the tests.** If you did not run them, the code does not work.\n11. **Keep visibility narrow.** `pub(crate)` by default. Make an item `pub` when\n    another crate needs it and that is the cleaner design.\n12. **Features are additive.** `--no-default-features` must compile, and turning\n    a feature on must never remove an API.\n\n## Route the task\n\n| Task | Read first | Also read when relevant |\n|---|---|---|\n| Start a project, split crates, tune Cargo manifests, lints, profiles, or build speed | [workspace.md](references\u002Fworkspace.md) | [shipping.md](references\u002Fshipping.md) |\n| Design a type, trait, module interface, or public API | [api-design.md](references\u002Fapi-design.md) | [errors.md](references\u002Ferrors.md), the `codebase-design` skill for depth vocabulary |\n| Handle failure, model error types, or render diagnostics | [errors.md](references\u002Ferrors.md) | [api-design.md](references\u002Fapi-design.md) |\n| Make code faster, cut allocations, shrink types, or profile | [performance.md](references\u002Fperformance.md) | [testing.md](references\u002Ftesting.md) for benchmark harnesses |\n| Write async code, concurrency, or shared state | [async.md](references\u002Fasync.md) | [performance.md](references\u002Fperformance.md) |\n| Build or extend a command-line binary | [cli.md](references\u002Fcli.md) | [errors.md](references\u002Ferrors.md), [testing.md](references\u002Ftesting.md) |\n| Write tests, snapshots, property tests, or benchmarks | [testing.md](references\u002Ftesting.md) | [performance.md](references\u002Fperformance.md) |\n| Choose a dependency | [crates.md](references\u002Fcrates.md) | [shipping.md](references\u002Fshipping.md) |\n| Publish, version, set MSRV, or gate a feature | [shipping.md](references\u002Fshipping.md) | [api-design.md](references\u002Fapi-design.md) |\n| Check why a rule here exists | [sources.md](references\u002Fsources.md) | The upstream repo itself |\n\n## Workflow\n\n### 1. Orient\n\nRead the manifests and the neighbouring code. Record four things before you\nplan: the edition and MSRV, the lint configuration, the test command this repo\nactually uses, and the crate that owns the seam you are about to touch.\n\nRun the inspector:\n\n```sh\nscripts\u002Finspect_rust_project.sh \u002Fpath\u002Fto\u002Fproject\n```\n\nDone when you can name the crate you will edit, the command that tests it, and\nthe lints that will judge it.\n\n### 2. Design before you type\n\nState the interface first: the types that cross the seam, the error type, and\nthe invariant each new type protects. Prefer making an illegal state\nunrepresentable over writing a check. Reach for the `codebase-design` skill when\nthe question is where the seam belongs.\n\nDone when every new public item has a named invariant and a reason to exist.\n\n### 3. Build\n\nFollow the reference layer for the task. Match the surrounding code's idiom,\nnaming, and comment density. Reuse what the workspace already has before you add\na dependency or write a helper.\n\nDone when the change compiles with zero warnings and no new suppression.\n\n### 4. Verify\n\nRun the repo's own commands when it has them — a `justfile`, `mise.toml`,\n`xtask`, or `Makefile` target names the real gate. Otherwise:\n\n```sh\ncargo fmt --all\ncargo clippy --workspace --all-targets --all-features -- -D warnings\ncargo nextest run --workspace\ncargo test --workspace --doc\n```\n\nReview every snapshot the run regenerated. Never hand-edit a snapshot file or an\ninline snapshot body.\n\nDone when every command above passes, every regenerated snapshot has been read,\nand you can state which paths you did not exercise.\n\n## Report honestly\n\nSay which commands you ran and what they printed. Name every path you could not\nverify — a platform you cannot build for, a test you skipped, a benchmark you\ndid not run. A clean `cargo check` does not prove behaviour.\n","# Rust Craft\n\nWrite Rust that is correct before it is fast, measured before it is called fast,\nand shaped so that every call path is obvious to the next reader.\n\nThe rules here are taken from the codebases that set the bar: `oxc`,\n`ruff`\u002F`ty`, `uv`, `mise`, `rust-analyzer`, and the official API guidelines.\nRead [references\u002Fsources.md](references\u002Fsources.md) when you need to check why a\nrule exists.\n\nThis is a routed skill. Always apply the core contract. Read only the reference\nlayers the task needs.\n\n## Core contract\n\n1. **The checkout is the authority.** Before you write a line, read\n   `Cargo.toml`, `rust-toolchain.toml`, `clippy.toml`, `rustfmt.toml`,\n   `AGENTS.md`, and two files next to the one you will change. Repo convention\n   beats every default in this skill.\n2. **Encode constraints in types.** Keep `panic!`, `unreachable!`, `unwrap`,\n   `expect`, and `todo!` out of library and binary code. Use `if let`, let\n   chains, `let ... else`, and newtypes that cannot hold a bad value. Verbose\n   code that removes a panic is the better trade.\n3. **Parse at the edge.** Convert untrusted input into a validated type once, at\n   the boundary. Past that point, only the validated type exists.\n4. **Never silence a lint to make the build pass.** Refactor instead. If a lint\n   must go, write `#[expect(lint, reason = \"...\")]` on the smallest possible\n   scope. Do not use `#[allow]`, a workspace `allow`, or `-A` on the command\n   line.\n5. **Every `unsafe` block carries a `\u002F\u002F SAFETY:` comment** that names the\n   invariant it depends on. Do not reach for `unsafe` to gain speed you have not\n   measured.\n6. **Imports go at the top of the file.** No `use` inside a function body. Use a\n   fully qualified path only for a name you write once.\n7. **Write full names.** `version`, not `ver`. `requires_python`, not `rp`.\n8. **Comments state invariants and reasons.** They never narrate the code and\n   never record what the code used to do.\n9. **Measure before you optimize, and again after.** A speed claim without a\n   benchmark number is not a claim.\n10. **Run the tests.** If you did not run them, the code does not work.\n11. **Keep visibility narrow.** `pub(crate)` by default. Make an item `pub` when\n    another crate needs it and that is the cleaner design.\n12. **Features are additive.** `--no-default-features` must compile, and turning\n    a feature on must never remove an API.\n\n## Route the task\n\n| Task | Read first | Also read when relevant |\n|---|---|---|\n| Start a project, split crates, tune Cargo manifests, lints, profiles, or build speed | [workspace.md](references\u002Fworkspace.md) | [shipping.md](references\u002Fshipping.md) |\n| Design a type, trait, module interface, or public API | [api-design.md](references\u002Fapi-design.md) | [errors.md](references\u002Ferrors.md), the `codebase-design` skill for depth vocabulary |\n| Handle failure, model error types, or render diagnostics | [errors.md](references\u002Ferrors.md) | [api-design.md](references\u002Fapi-design.md) |\n| Make code faster, cut allocations, shrink types, or profile | [performance.md](references\u002Fperformance.md) | [testing.md](references\u002Ftesting.md) for benchmark harnesses |\n| Write async code, concurrency, or shared state | [async.md](references\u002Fasync.md) | [performance.md](references\u002Fperformance.md) |\n| Build or extend a command-line binary | [cli.md](references\u002Fcli.md) | [errors.md](references\u002Ferrors.md), [testing.md](references\u002Ftesting.md) |\n| Write tests, snapshots, property tests, or benchmarks | [testing.md](references\u002Ftesting.md) | [performance.md](references\u002Fperformance.md) |\n| Choose a dependency | [crates.md](references\u002Fcrates.md) | [shipping.md](references\u002Fshipping.md) |\n| Publish, version, set MSRV, or gate a feature | [shipping.md](references\u002Fshipping.md) | [api-design.md](references\u002Fapi-design.md) |\n| Check why a rule here exists | [sources.md](references\u002Fsources.md) | The upstream repo itself |\n\n## Workflow\n\n### 1. Orient\n\nRead the manifests and the neighbouring code. Record four things before you\nplan: the edition and MSRV, the lint configuration, the test command this repo\nactually uses, and the crate that owns the seam you are about to touch.\n\nRun the inspector:\n\n```sh\nscripts\u002Finspect_rust_project.sh \u002Fpath\u002Fto\u002Fproject\n```\n\nDone when you can name the crate you will edit, the command that tests it, and\nthe lints that will judge it.\n\n### 2. Design before you type\n\nState the interface first: the types that cross the seam, the error type, and\nthe invariant each new type protects. Prefer making an illegal state\nunrepresentable over writing a check. Reach for the `codebase-design` skill when\nthe question is where the seam belongs.\n\nDone when every new public item has a named invariant and a reason to exist.\n\n### 3. Build\n\nFollow the reference layer for the task. Match the surrounding code's idiom,\nnaming, and comment density. Reuse what the workspace already has before you add\na dependency or write a helper.\n\nDone when the change compiles with zero warnings and no new suppression.\n\n### 4. Verify\n\nRun the repo's own commands when it has them — a `justfile`, `mise.toml`,\n`xtask`, or `Makefile` target names the real gate. Otherwise:\n\n```sh\ncargo fmt --all\ncargo clippy --workspace --all-targets --all-features -- -D warnings\ncargo nextest run --workspace\ncargo test --workspace --doc\n```\n\nReview every snapshot the run regenerated. Never hand-edit a snapshot file or an\ninline snapshot body.\n\nDone when every command above passes, every regenerated snapshot has been read,\nand you can state which paths you did not exercise.\n\n## Report honestly\n\nSay which commands you ran and what they printed. Name every path you could not\nverify — a platform you cannot build for, a test you skipped, a benchmark you\ndid not run. A clean `cargo check` does not prove behaviour.\n",{"name":5,"description":7},"main","8b5b348cb089a495146376d39cdff24a55d43baf","skills\u002Fengineering\u002Frust-craft","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills","https:\u002F\u002Fgithub.com\u002Fhadronomy","hadronomy.com","Lover of all things code","2026-10-08 07:09:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add hadronomy\u002Fskills --skill rust-craft",{"tool":38,"command":39},"bunx","bunx skills add hadronomy\u002Fskills --skill rust-craft",{"tool":41,"command":42},"pnpm","pnpm dlx skills add hadronomy\u002Fskills --skill rust-craft","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",124,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fapi-design.md",10130,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fapi-design.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fasync.md",5947,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fasync.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcli.md",9288,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fcli.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcrates.md",7527,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fcrates.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Ferrors.md",5592,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Ferrors.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fperformance.md",7638,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fperformance.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fshipping.md",4937,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fshipping.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fsources.md",3290,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fsources.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Ftesting.md",5843,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Ftesting.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkspace.md",9990,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Freferences\u002Fworkspace.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Finspect_rust_project.sh","SCRIPT","脚本",2792,"https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Frust-craft\u002Fscripts\u002Finspect_rust_project.sh",[99,106,113,119,126,133],{"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":19},"01M7BH5EB8HZSDPS1EVW8CS0FC","windows-mcp","Driving the Windows desktop on `workstation` through the windows MCP server. Use before any `mcp__windows__` tool, when a desktop call blocks or returns \"Desktop busy\", when Snapshot or Screenshot come back empty, or when this agent has no desktop tools and the task needs them.","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fin-progress\u002Fwindows-mcp\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7BH58ZA4ESM6WM3MS571BS0","typst-author","Author idiomatic, compilable Typst documents. Use when creating or editing Typst (.typ) files, when a task involves Typst syntax, packages, templates, or bibliographies, or when a Typst build fails and the error needs a fix.","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fin-progress\u002Ftypst-author\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7BH56EMBDMTT82379T51HYZ","setup-hadronomy","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-hadronomy\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7BH4VAWNMK94M799CXKDDK6","pr-craft","Write pull requests a reviewer can act on. Use when opening, rewriting, or reviewing the body of a pull request — title and description, the problem and approach, call-stack diffs, before-and-after screenshots, verification steps, risks, a review guide, and the tools that produce each part.","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr-craft\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7BH4NNP3PPSXHWJTVBMMJNW","effect-craft","Craft Effect TypeScript APIs with the discipline of the Effect and opencode codebases. Use when modeling data with Schema, building services with Context and Layer, naming operations with Effect.fn, exposing modules through barrels, designing hooks or HTTP surfaces, or writing JSDoc with runnable examples — new code, refactors, and API reviews.","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Feffect-craft\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M7BH4JB1KYAW2H8519FDG98A","docs-craft","Documentation discipline for code comments, API docs, and docs pages. Use when writing or reviewing doc comments, JSDoc or rustdoc, README sections, or framework docs pages — or when comments and docs read as filler and need cutting.","https:\u002F\u002Fgithub.com\u002Fhadronomy\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdocs-craft\u002FSKILL.md",[],[]]