[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G0K83J9JSQFJ2RWXF9NFM":3,"skill-same:01M73G0K83J9JSQFJ2RWXF9NFM":129},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M73G0K83J9JSQFJ2RWXF9NFM","rust-reviewer",null,"Review Rust ownership, lifetimes, unsafe boundaries, concurrency, error handling, Cargo dependencies, and tests.","domehahn\u002Fskcr","domehahn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41511445?v=4","01M735R3R9KEBEJ6D5YYAE9A61","Dominik Hahn","01M735R3SCNX1SGB3T840Z1H3H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"rust-reviewer\"\ndescription: \"Review Rust ownership, lifetimes, unsafe boundaries, concurrency, error handling, Cargo dependencies, and tests.\"\nversion: \"1.0.0\"\nsince: \"2026-09-09\"\nlast_modified: \"2026-09-09\"\nauthors:\n  - \"platform-engineering\"\nstability: \"stable\"\nmin_platform_version:\n  codex: \"unknown\"\n  amazon-q: \"unknown\"\n  antigravity: \"unknown\"\n  auggie: \"unknown\"\n  bob: \"unknown\"\n  claude-code: \"unknown\"\n  cline: \"unknown\"\n  codebuddy: \"unknown\"\n  continue: \"unknown\"\n  costrict: \"unknown\"\n  crush: \"unknown\"\n  github-copilot: \"unknown\"\n  gitlab-duo: \"unknown\"\n  factory: \"unknown\"\n  forgecode: \"unknown\"\n  opencode: \"unknown\"\n  openhands: \"unknown\"\n  cursor: \"unknown\"\n  roo-code: \"unknown\"\n  kiro: \"unknown\"\n  junie: \"unknown\"\n  gemini-cli: \"unknown\"\n  iflow: \"unknown\"\n  kilocode: \"unknown\"\n  kimi: \"unknown\"\n  lingma: \"unknown\"\n  pi: \"unknown\"\n  qoder: \"unknown\"\n  qwen: \"unknown\"\n  windsurf: \"unknown\"\n  ollama: \"unknown\"\ndeprecated_since:\nreplaces:\nsupersedes: []\nchangelog:\n  - version: \"1.0.0\"\n    date: \"2026-09-09\"\n    change: \"Initial generated production-ready SDLC \u002F DevSecOps skill\"\n---\n# Rust Reviewer\n\n## Purpose\n\nReview Rust ownership, lifetimes, unsafe boundaries, concurrency, error handling, Cargo dependencies, and tests.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- Source code, configuration, dependencies, tests, deployment artifacts, or runtime behavior in Rust engineering change.\n- A design, migration, upgrade, security, reliability, or performance decision requires technology-specific review.\n\n## Operating model\n\n1. Inspect the repository version, dependency lockfiles, build configuration, runtime target, and deployment environment before applying version-sensitive guidance.\n2. Use current official documentation for the pinned version and distinguish verified behavior from assumptions.\n3. Review correctness first, then security, reliability, maintainability, testability, performance, and operational impact.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- ownership and borrowing, lifetimes, unsafe code, Send and Sync, Result handling, Cargo\n- dependency and supply-chain boundaries\n- configuration, secrets, identity, networking, data, observability, deployment, upgrade, and rollback behavior\n\n## Skill-Specific Checklist\n\n- [ ] Identify concrete versions, supported runtimes, dependency managers, build tools, and deployment targets.\n- [ ] Check idiomatic API use, lifecycle boundaries, error handling, concurrency or asynchronous behavior, resource cleanup, and data consistency.\n- [ ] Check input validation, authorization, secret handling, dependency provenance, insecure defaults, and sensitive logging.\n- [ ] Check unit, integration, failure-path, upgrade, rollback, and operational test evidence.\n- [ ] Check observability, capacity, performance, compatibility, deprecations, and migration impact.\n- [ ] Trace Rust engineering inputs, outputs, identities, trust boundaries, external dependencies, and persistent state.\n- [ ] Check Rust engineering defaults, configuration precedence, environment separation, and drift from reviewed source.\n- [ ] Check Rust engineering least privilege, credential rotation, audit events, policy enforcement, and break-glass behavior.\n- [ ] Check Rust engineering resource ownership, cleanup, quotas, rate limits, timeouts, retries, and backpressure.\n- [ ] Check Rust engineering release notes, supported upgrade paths, schema or API compatibility, and rollback constraints.\n\n## Decision Rules\n\n- Do not recommend an API, option, or migration from memory when behavior is version-sensitive; verify it against official documentation for the detected version.\n- Do not run deployments, applies, destroys, migrations, or production mutations without explicit authorization for the exact target.\n- Treat unsupported versions, ambiguous state changes, missing rollback, broad credentials, and untested destructive transitions as release blockers by impact.\n- If Rust engineering identity, version, edition, or deployment model cannot be established, report the uncertainty before recommending a change.\n- If a Rust engineering change can affect availability, security boundaries, persistent data, or external consumers, require staged validation and explicit rollback criteria.\n\n## Finding Categories\n\n- Correctness or lifecycle defect.\n- Security, identity, secret, dependency, or isolation weakness.\n- Reliability, data integrity, upgrade, rollback, or operational gap.\n- Testing, observability, maintainability, compatibility, or performance gap.\n- Rust engineering documentation, ownership, maintenance, licensing, provenance, or evidence gap.\n\n## Severity Guidance\n\n- Critical: enables remote compromise, unrestricted privilege, secret disclosure, destructive production change, or material data loss.\n- High: causes exploitable authorization or isolation failure, sustained outage, corrupt state, or unsafe upgrade and rollback behavior.\n- Medium: creates a bounded correctness, reliability, compatibility, test, observability, or performance risk.\n- Low: improves clarity, idiomatic usage, maintainability, or evidence without changing material behavior.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- List detected versions and evidence sources.\n- Return prioritized findings with affected files or resources, impact, evidence, and concrete remediation.\n- Include validation commands, migration and rollback notes, and unresolved version-sensitive assumptions.\n- Include a Rust engineering architecture and dependency summary with trust boundaries and persistent state.\n- Include Rust engineering validation commands or tests that are safe for the stated environment.\n\n## Acceptance Criteria\n\n- Guidance matches the detected technology version and official documentation.\n- Material correctness, security, reliability, test, upgrade, and rollback risks have evidence-backed disposition.\n- No production mutation or destructive action is performed without exact-scope approval.\n- Rust engineering identity, version, configuration, dependencies, and deployment assumptions are explicit.\n- Rust engineering failure, upgrade, rollback, observability, and recovery paths have proportionate evidence.\n\n## Anti-Patterns\n\n- Giving generic advice without inspecting versions or artifacts.\n- Inventing configuration keys, APIs, defaults, test results, or compatibility claims.\n- Treating a successful build as proof of security, runtime correctness, upgrade safety, or operability.\n- Assuming Landscape inclusion or popularity proves that Rust engineering is secure, supported, compatible, or suitable.\n- Using an unpinned latest version of Rust engineering as the basis for migration or production guidance.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n","# Rust Reviewer\n\n## Purpose\n\nReview Rust ownership, lifetimes, unsafe boundaries, concurrency, error handling, Cargo dependencies, and tests.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- Source code, configuration, dependencies, tests, deployment artifacts, or runtime behavior in Rust engineering change.\n- A design, migration, upgrade, security, reliability, or performance decision requires technology-specific review.\n\n## Operating model\n\n1. Inspect the repository version, dependency lockfiles, build configuration, runtime target, and deployment environment before applying version-sensitive guidance.\n2. Use current official documentation for the pinned version and distinguish verified behavior from assumptions.\n3. Review correctness first, then security, reliability, maintainability, testability, performance, and operational impact.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- ownership and borrowing, lifetimes, unsafe code, Send and Sync, Result handling, Cargo\n- dependency and supply-chain boundaries\n- configuration, secrets, identity, networking, data, observability, deployment, upgrade, and rollback behavior\n\n## Skill-Specific Checklist\n\n- [ ] Identify concrete versions, supported runtimes, dependency managers, build tools, and deployment targets.\n- [ ] Check idiomatic API use, lifecycle boundaries, error handling, concurrency or asynchronous behavior, resource cleanup, and data consistency.\n- [ ] Check input validation, authorization, secret handling, dependency provenance, insecure defaults, and sensitive logging.\n- [ ] Check unit, integration, failure-path, upgrade, rollback, and operational test evidence.\n- [ ] Check observability, capacity, performance, compatibility, deprecations, and migration impact.\n- [ ] Trace Rust engineering inputs, outputs, identities, trust boundaries, external dependencies, and persistent state.\n- [ ] Check Rust engineering defaults, configuration precedence, environment separation, and drift from reviewed source.\n- [ ] Check Rust engineering least privilege, credential rotation, audit events, policy enforcement, and break-glass behavior.\n- [ ] Check Rust engineering resource ownership, cleanup, quotas, rate limits, timeouts, retries, and backpressure.\n- [ ] Check Rust engineering release notes, supported upgrade paths, schema or API compatibility, and rollback constraints.\n\n## Decision Rules\n\n- Do not recommend an API, option, or migration from memory when behavior is version-sensitive; verify it against official documentation for the detected version.\n- Do not run deployments, applies, destroys, migrations, or production mutations without explicit authorization for the exact target.\n- Treat unsupported versions, ambiguous state changes, missing rollback, broad credentials, and untested destructive transitions as release blockers by impact.\n- If Rust engineering identity, version, edition, or deployment model cannot be established, report the uncertainty before recommending a change.\n- If a Rust engineering change can affect availability, security boundaries, persistent data, or external consumers, require staged validation and explicit rollback criteria.\n\n## Finding Categories\n\n- Correctness or lifecycle defect.\n- Security, identity, secret, dependency, or isolation weakness.\n- Reliability, data integrity, upgrade, rollback, or operational gap.\n- Testing, observability, maintainability, compatibility, or performance gap.\n- Rust engineering documentation, ownership, maintenance, licensing, provenance, or evidence gap.\n\n## Severity Guidance\n\n- Critical: enables remote compromise, unrestricted privilege, secret disclosure, destructive production change, or material data loss.\n- High: causes exploitable authorization or isolation failure, sustained outage, corrupt state, or unsafe upgrade and rollback behavior.\n- Medium: creates a bounded correctness, reliability, compatibility, test, observability, or performance risk.\n- Low: improves clarity, idiomatic usage, maintainability, or evidence without changing material behavior.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- List detected versions and evidence sources.\n- Return prioritized findings with affected files or resources, impact, evidence, and concrete remediation.\n- Include validation commands, migration and rollback notes, and unresolved version-sensitive assumptions.\n- Include a Rust engineering architecture and dependency summary with trust boundaries and persistent state.\n- Include Rust engineering validation commands or tests that are safe for the stated environment.\n\n## Acceptance Criteria\n\n- Guidance matches the detected technology version and official documentation.\n- Material correctness, security, reliability, test, upgrade, and rollback risks have evidence-backed disposition.\n- No production mutation or destructive action is performed without exact-scope approval.\n- Rust engineering identity, version, configuration, dependencies, and deployment assumptions are explicit.\n- Rust engineering failure, upgrade, rollback, observability, and recovery paths have proportionate evidence.\n\n## Anti-Patterns\n\n- Giving generic advice without inspecting versions or artifacts.\n- Inventing configuration keys, APIs, defaults, test results, or compatibility claims.\n- Treating a successful build as proof of security, runtime correctness, upgrade safety, or operability.\n- Assuming Landscape inclusion or popularity proves that Rust engineering is secure, supported, compatible, or suitable.\n- Using an unpinned latest version of Rust engineering as the basis for migration or production guidance.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n",{"name":5,"since":25,"authors":26,"version":28,"replaces":6,"changelog":29,"stability":32,"supersedes":33,"description":7,"last_modified":25,"deprecated_since":6,"min_platform_version":34},"2026-09-09",[27],"platform-engineering","1.0.0",[30],{"date":25,"change":31,"version":28},"Initial generated production-ready SDLC \u002F DevSecOps skill","stable",[],{"pi":35,"bob":35,"kimi":35,"kiro":35,"qwen":35,"cline":35,"codex":35,"crush":35,"iflow":35,"junie":35,"qoder":35,"auggie":35,"cursor":35,"lingma":35,"ollama":35,"factory":35,"amazon-q":35,"continue":35,"costrict":35,"kilocode":35,"opencode":35,"roo-code":35,"windsurf":35,"codebuddy":35,"forgecode":35,"openhands":35,"gemini-cli":35,"gitlab-duo":35,"antigravity":35,"claude-code":35,"github-copilot":35},"unknown","main","850948b1e2e668b3ddfc2ac2959286d4190a8a4a",".agents\u002Fskills\u002Frust-reviewer","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr","https:\u002F\u002Fgithub.com\u002Fdomehahn","Proud to live. Love to code and explore. DevSecOps | Cloud & Cloud Native | Java | Go | Python | IaC | AI ","2026-09-11 04:40:53",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add domehahn\u002Fskcr --skill rust-reviewer",{"tool":49,"command":50},"bunx","bunx skills add domehahn\u002Fskcr --skill rust-reviewer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add domehahn\u002Fskcr --skill rust-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FSKILL.md",true,[57,63,69,73,77,81,85,89,93,97,101,105,109,113,119,123],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002FREADME.md","ASSET","资产文件",134,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fassets\u002FREADME.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assurance.yaml","REFERENCE","参考文档",393,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fassurance.yaml",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"CHANGELOG.md",133,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FCHANGELOG.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"contract.yaml",3776,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fcontract.yaml",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"dependencies.yaml",85,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fdependencies.yaml",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"descriptor.yaml",658,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fdescriptor.yaml",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaseline.yaml",2227,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fevals\u002Fbaseline.yaml",{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002FREADME.md",719,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fevals\u002FREADME.md",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"integrations\u002Fa2a.yaml",279,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fintegrations\u002Fa2a.yaml",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"integrations\u002Fmcp.yaml",32,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fintegrations\u002Fmcp.yaml",{"path":102,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":16},"LICENSE","许可证",214,{"path":106,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":107,"sourceHtmlUrl":108},"README.md",1253,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FREADME.md",{"path":110,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002FREADME.md",167,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Freferences\u002FREADME.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002FREADME.md","SCRIPT","脚本",202,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Fscripts\u002FREADME.md",{"path":120,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":121,"sourceHtmlUrl":122},"tests\u002FREADME.md",166,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002Ftests\u002FREADME.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"VERSION","OTHER","其他",6,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frust-reviewer\u002FVERSION",[130,138,146,154,162,170],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7419KQMCNS14XW21KVG78J3","vulnerability-management-coordinator","Assess CVE triage, prioritization, SLAs, exploitability, asset criticality, exceptions, risk acceptance, and remediation tracking.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fvulnerability-management-coordinator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fvulnerability-management-coordinator\u002FSKILL.md",[],[],{"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":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7419GW8E90CEERTQTZ3MTYR","verification-reviewer","Review diffs, validate acceptance criteria, inspect test results, and find missed requirements.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fverification-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fverification-reviewer\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M7419CTW726KC0YN9F2E739T","universal-skill-creator","Create, adapt, validate, and optimize reusable agent skills across agentic platforms.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Funiversal-skill-creator\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Funiversal-skill-creator\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":20},"01M74199GKQYVD5KER7CZ8F2D6","threat-modeler","Identify assets, trust boundaries, abuse cases, attack paths, threats, and required security controls.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fthreat-modeler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fthreat-modeler\u002FSKILL.md",[],[],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":20},"01M74196JRAY93SRVX6X6CDMDF","test-strategy-engineer","Design and generate unit, integration, regression, security, and end-to-end test strategies.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftest-strategy-engineer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftest-strategy-engineer\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":20},"01M74193K4YBY6JHZSVQ92NS9X","sre-reliability-reviewer","Assess SLOs, SLIs, error budgets, capacity, degradation, timeouts, retries, circuit breakers, load shedding, and operational risks.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsre-reliability-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskcr\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsre-reliability-reviewer\u002FSKILL.md",[],[]]