[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AGX302BHT9GSRFKGEDJ6F":3,"skill-same:01M71AGX302BHT9GSRFKGEDJ6F":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":63,"updatedAt":64,"install":65,"resources":77},"01M71AGX302BHT9GSRFKGEDJ6F","cyber-auditing-foundry-smart-contract-security",null,">- Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle\u002Fprice manipulation, and arithmetic bugs BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext private keys,","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-auditing-foundry-smart-contract-security\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"auditing foundry smart contract security","cyber auditing foundry smart contract security","security","contract","smart contract security","foundry","smart contract","encrypted","reentrancy","oracle","aderyn","access","false","cybersecurity","forge","testing","static","project","security audit","chain","2026-11-10 10:12:30",false,"---\nname: cyber-auditing-foundry-smart-contract-security\ndescription: \">- Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle\u002Fprice manipulation, and arithmetic bugs BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext private keys,\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: auditing-foundry-smart-contract-security | description: >- |   Pre-deployment security audit of Solidity smart contracts in a Foundry project. |   Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and |   property-based testing (forge fuzz + invariant tests with handlers) to catch |   reentrancy, access-control, oracle\u002Fprice manipulation, and arithmetic bugs |   BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext |   private keys, encrypted cas\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Auditing Foundry Smart Contract Security\n\n## Overview\n\nDeployed smart contracts are **immutable** and custody **real funds**, so a bug\nshipped to mainnet cannot be patched — it can only be exploited. Most catastrophic\nDeFi losses come from a small set of recurring classes: reentrancy, broken access\ncontrol, oracle\u002Fprice manipulation, and unchecked arithmetic or external calls.\n\nThis skill runs a **defense-in-depth, pre-deployment audit** of a Foundry project,\nlayering four independent techniques that each catch what the others miss:\n\n1. **Static analysis** — `slither` (90+ detectors) and `aderyn` (Cyfrin, Rust) scan\n   the AST\u002FIR in seconds for known anti-patterns.\n2. **Symbolic execution** — `mythril` (optional, slow) explores execution paths and\n   SMT-solves for deep arithmetic\u002Freentrancy bugs.\n3. **Property-based testing** — `forge test` with **fuzzing** (`testFuzz_*`) and\n   **invariant tests** (`invariant_*` + handler contracts with ghost variables)\n   proves protocol-level properties hold across millions of random sequences.\n4. **Manual review + key hygiene** — a structured checklist (see\n   `references\u002Fvulnerability-checklist.md`) and a secrets\u002Fkeystore audit so no\n   private key ever lives in plaintext and deployment goes through an encrypted\n   `cast` keystore (see `references\u002Fsecure-deployment-and-keys.md`).\n\nThe skill is **dev-side and pre-deployment** — it is run by the engineer building\nthe contract, not by a SOC after an incident. Findings gate the deploy: any\nhigh\u002Fcritical static finding, failing test, leaked key, or low coverage = **FAIL**.\n\n## When to Use\n\n- Before deploying any Solidity contract to a testnet or mainnet EVM chain.\n- When writing or reviewing a Foundry project (`foundry.toml`, `src\u002F`, `test\u002F`, `script\u002F`).\n- When a contract handles value: tokens (ERC-20\u002F721\u002F1155), vaults, staking, AMMs, bridges, governance.\n- When adding fuzz or invariant tests, or when coverage of value-moving functions is unknown.\n- When wiring deployment scripts — to verify keys are in an encrypted keystore, not `.env` plaintext.\n- When integrating a price oracle, external call, `delegatecall`, or upgradeable proxy.\n- When triaging a Slither\u002FAderyn report and needing to separate real bugs from false positives.\n\n## Prerequisites\n\n- **Foundry** installed (`forge`, `cast`, `anvil`): `curl -L https:\u002F\u002Ffoundry.paradigm.xyz | bash && foundryup`\n- **Slither** + solc: `pip install slither-analyzer` and `solc-select install \u003Cver> && solc-select use \u003Cver>`\n- **Aderyn** (recommended): `cargo install aderyn` (or `npm i -g @cyfrin\u002Faderyn`)\n- **Mythril** (optional, slow symbolic exec): `pip install mythril`\n- **gitleaks** (key-leak scan): see the companion `implementing-secret-scanning-with-gitleaks` skill\n- A Foundry project that **compiles** (`forge build` succeeds) — analyzers need build artifacts.\n- Solidity ^0.8.x is assumed (built-in overflow checks); pre-0.8 contracts need extra SafeMath review.\n\n> Install the Python tools in a virtualenv (recommended on externally-managed distros). Never run\n> analysis against untrusted contract source on a machine with funded wallets unlocked.\n\n## Steps\n\n### Step 1: Build and sanity-check the project\n\n```bash\nforge build                    # analyzers require fresh artifacts\nforge fmt --check              # style gate (optional)\ncat foundry.toml               # note solc version, optimizer, remappings, evm_version\n```\n\n### Step 2: Static analysis (fast, run every time)\n\n```bash\n# Slither — full project (uses foundry.toml + remappings automatically)\nslither . --json slither-report.json\n\n# Aderyn — Cyfrin Rust analyzer, complementary detectors\naderyn . -o aderyn-report.json\n```\n\nOr run the bundled orchestrator that runs both, deduplicates, and gates the result:\n\n```bash\npython3 scripts\u002Fagent.py --project . --output audit-report.json\n```\n\n### Step 3: Symbolic execution on critical contracts (optional, slow)\n\n```bash\n# Only on the highest-value contract(s) — Mythril is path-explosive\nmyth analyze src\u002FVault.sol --solc-json mythril.config.json --execution-timeout 300 -o json\n# or: python3 scripts\u002Fagent.py --project . --mythril src\u002FVault.sol\n```\n\n### Step 4: Property-based testing — fuzz + invariants\n\n```bash\nforge test -vvv                                  # unit + fuzz tests\nforge coverage --report summary                  # coverage of value-moving code\nforge test --match-test invariant_ -vvv          # invariant suite (handler-based)\n```\n\nEvery value-moving contract should have **invariant tests with a handler** (bounded\ninputs, ghost variables, `targetContract(handler)`) — not just unit tests. See\n`references\u002Fapi-reference.md` for the handler pattern, and write a\n`test_RevertWhen_*` (with `vm.expectRevert`) for each access-control guard.\n\n### Step 5: Manual review against the checklist\n\nWalk `references\u002Fvulnerability-checklist.md` for every contract: reentrancy\n(checks-effects-interactions \u002F `nonReentrant`), access control, oracle manipulation,\n`delegatecall`\u002Fproxy storage layout, unchecked return values, `tx.origin`, weak\nrandomness, DoS, front-running\u002FMEV, and ERC-specific pitfalls (approve race,\nfee-on-transfer, rebasing).\n\n### Step 6: Key hygiene & secure deploy\n\n```bash\ngitleaks detect --no-banner            # no private keys \u002F mnemonics \u002F .env committed\ngit ls-files | grep -E '\\.env$|keystore' && echo \"WARN: secrets tracked by git\"\n\n# Import the deploy key ONCE into an encrypted keystore — never a plaintext PRIVATE_KEY env\ncast wallet import deployer --interactive\n\n# Deploy via the keystore account (testnet first), simulate before --broadcast\nforge script script\u002FDeploy.s.sol --account deployer --rpc-url \u003Ctestnet> --broadcast --verify\n```\n\nSee `references\u002Fsecure-deployment-and-keys.md` for the full hardening rules\n(MetaMask hygiene, hardware wallet for mainnet, RPC trust, post-deploy verification).\n\n### Step 7: Triage and report\n\nCombine Slither + Aderyn + Mythril + test results, deduplicate by (file, line),\ndrop confirmed false positives, rank by exploitability × financial impact, and map\neach to its SWC id. The orchestrator emits `audit-report.json` with a PASS\u002FFAIL gate.\n\n## Expected Output\n\nA JSON audit report listing findings with **SWC identifiers**, severity, tool source,\naffected contract\u002Ffunction\u002Fline, and remediation; plus the test\u002Fcoverage summary and a\nsingle **PASS \u002F FAIL** deploy gate. FAIL on any high\u002Fcritical static finding, failing\ntest, leaked secret, or coverage below the configured threshold on value-moving code.\n","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Auditing Foundry Smart Contract Security\n\n## Overview\n\nDeployed smart contracts are **immutable** and custody **real funds**, so a bug\nshipped to mainnet cannot be patched — it can only be exploited. Most catastrophic\nDeFi losses come from a small set of recurring classes: reentrancy, broken access\ncontrol, oracle\u002Fprice manipulation, and unchecked arithmetic or external calls.\n\nThis skill runs a **defense-in-depth, pre-deployment audit** of a Foundry project,\nlayering four independent techniques that each catch what the others miss:\n\n1. **Static analysis** — `slither` (90+ detectors) and `aderyn` (Cyfrin, Rust) scan\n   the AST\u002FIR in seconds for known anti-patterns.\n2. **Symbolic execution** — `mythril` (optional, slow) explores execution paths and\n   SMT-solves for deep arithmetic\u002Freentrancy bugs.\n3. **Property-based testing** — `forge test` with **fuzzing** (`testFuzz_*`) and\n   **invariant tests** (`invariant_*` + handler contracts with ghost variables)\n   proves protocol-level properties hold across millions of random sequences.\n4. **Manual review + key hygiene** — a structured checklist (see\n   `references\u002Fvulnerability-checklist.md`) and a secrets\u002Fkeystore audit so no\n   private key ever lives in plaintext and deployment goes through an encrypted\n   `cast` keystore (see `references\u002Fsecure-deployment-and-keys.md`).\n\nThe skill is **dev-side and pre-deployment** — it is run by the engineer building\nthe contract, not by a SOC after an incident. Findings gate the deploy: any\nhigh\u002Fcritical static finding, failing test, leaked key, or low coverage = **FAIL**.\n\n## When to Use\n\n- Before deploying any Solidity contract to a testnet or mainnet EVM chain.\n- When writing or reviewing a Foundry project (`foundry.toml`, `src\u002F`, `test\u002F`, `script\u002F`).\n- When a contract handles value: tokens (ERC-20\u002F721\u002F1155), vaults, staking, AMMs, bridges, governance.\n- When adding fuzz or invariant tests, or when coverage of value-moving functions is unknown.\n- When wiring deployment scripts — to verify keys are in an encrypted keystore, not `.env` plaintext.\n- When integrating a price oracle, external call, `delegatecall`, or upgradeable proxy.\n- When triaging a Slither\u002FAderyn report and needing to separate real bugs from false positives.\n\n## Prerequisites\n\n- **Foundry** installed (`forge`, `cast`, `anvil`): `curl -L https:\u002F\u002Ffoundry.paradigm.xyz | bash && foundryup`\n- **Slither** + solc: `pip install slither-analyzer` and `solc-select install \u003Cver> && solc-select use \u003Cver>`\n- **Aderyn** (recommended): `cargo install aderyn` (or `npm i -g @cyfrin\u002Faderyn`)\n- **Mythril** (optional, slow symbolic exec): `pip install mythril`\n- **gitleaks** (key-leak scan): see the companion `implementing-secret-scanning-with-gitleaks` skill\n- A Foundry project that **compiles** (`forge build` succeeds) — analyzers need build artifacts.\n- Solidity ^0.8.x is assumed (built-in overflow checks); pre-0.8 contracts need extra SafeMath review.\n\n> Install the Python tools in a virtualenv (recommended on externally-managed distros). Never run\n> analysis against untrusted contract source on a machine with funded wallets unlocked.\n\n## Steps\n\n### Step 1: Build and sanity-check the project\n\n```bash\nforge build                    # analyzers require fresh artifacts\nforge fmt --check              # style gate (optional)\ncat foundry.toml               # note solc version, optimizer, remappings, evm_version\n```\n\n### Step 2: Static analysis (fast, run every time)\n\n```bash\n# Slither — full project (uses foundry.toml + remappings automatically)\nslither . --json slither-report.json\n\n# Aderyn — Cyfrin Rust analyzer, complementary detectors\naderyn . -o aderyn-report.json\n```\n\nOr run the bundled orchestrator that runs both, deduplicates, and gates the result:\n\n```bash\npython3 scripts\u002Fagent.py --project . --output audit-report.json\n```\n\n### Step 3: Symbolic execution on critical contracts (optional, slow)\n\n```bash\n# Only on the highest-value contract(s) — Mythril is path-explosive\nmyth analyze src\u002FVault.sol --solc-json mythril.config.json --execution-timeout 300 -o json\n# or: python3 scripts\u002Fagent.py --project . --mythril src\u002FVault.sol\n```\n\n### Step 4: Property-based testing — fuzz + invariants\n\n```bash\nforge test -vvv                                  # unit + fuzz tests\nforge coverage --report summary                  # coverage of value-moving code\nforge test --match-test invariant_ -vvv          # invariant suite (handler-based)\n```\n\nEvery value-moving contract should have **invariant tests with a handler** (bounded\ninputs, ghost variables, `targetContract(handler)`) — not just unit tests. See\n`references\u002Fapi-reference.md` for the handler pattern, and write a\n`test_RevertWhen_*` (with `vm.expectRevert`) for each access-control guard.\n\n### Step 5: Manual review against the checklist\n\nWalk `references\u002Fvulnerability-checklist.md` for every contract: reentrancy\n(checks-effects-interactions \u002F `nonReentrant`), access control, oracle manipulation,\n`delegatecall`\u002Fproxy storage layout, unchecked return values, `tx.origin`, weak\nrandomness, DoS, front-running\u002FMEV, and ERC-specific pitfalls (approve race,\nfee-on-transfer, rebasing).\n\n### Step 6: Key hygiene & secure deploy\n\n```bash\ngitleaks detect --no-banner            # no private keys \u002F mnemonics \u002F .env committed\ngit ls-files | grep -E '\\.env$|keystore' && echo \"WARN: secrets tracked by git\"\n\n# Import the deploy key ONCE into an encrypted keystore — never a plaintext PRIVATE_KEY env\ncast wallet import deployer --interactive\n\n# Deploy via the keystore account (testnet first), simulate before --broadcast\nforge script script\u002FDeploy.s.sol --account deployer --rpc-url \u003Ctestnet> --broadcast --verify\n```\n\nSee `references\u002Fsecure-deployment-and-keys.md` for the full hardening rules\n(MetaMask hygiene, hardware wallet for mainnet, RPC trust, post-deploy verification).\n\n### Step 7: Triage and report\n\nCombine Slither + Aderyn + Mythril + test results, deduplicate by (file, line),\ndrop confirmed false positives, rank by exploitability × financial impact, and map\neach to its SWC id. The orchestrator emits `audit-report.json` with a PASS\u002FFAIL gate.\n\n## Expected Output\n\nA JSON audit report listing findings with **SWC identifiers**, severity, tool source,\naffected contract\u002Ffunction\u002Fline, and remediation; plus the test\u002Fcoverage summary and a\nsingle **PASS \u002F FAIL** deploy gate. FAIL on any high\u002Fcritical static finding, failing\ntest, leaked secret, or coverage below the configured threshold on value-moving code.\n",{"hide":54,"name":5,"source":55,"license":15,"description":7,"authorized_lab":50,"origin_frontmatter":56},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: auditing-foundry-smart-contract-security | description: >- |   Pre-deployment security audit of Solidity smart contracts in a Foundry project. |   Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and |   property-based testing (forge fuzz + invariant tests with handlers) to catch |   reentrancy, access-control, oracle\u002Fprice manipulation, and arithmetic bugs |   BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext |   private keys, encrypted cas","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-auditing-foundry-smart-contract-security",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-14 03:05:17",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":54},[67,70,73],{"tool":68,"command":69},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-auditing-foundry-smart-contract-security",{"tool":71,"command":72},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-auditing-foundry-smart-contract-security",{"tool":74,"command":75},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-auditing-foundry-smart-contract-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-auditing-foundry-smart-contract-security\u002FSKILL.md",[],[79,103,127,155,182,201],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":49},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","when","you","code","it","context",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":49},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[110,111,90,112,113,114,115,116,117,118,119,96,120,98,121,122,123,124,125,126],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"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":83,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":49},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[137,138,139,140,141,142,143,144,145,98,146,147,148,149,150,151,152,114,153,154],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":167,"publishedAt":49},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":165,"categoryName":166,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[168,100,169,137,90,170,171,172,114,173,174,175,176,177,178,179,180,181,96,98],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":49},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,197,98,198,121,199,200],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":217,"publishedAt":49},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[207,208,211,214],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":215,"categoryName":216,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[218,219,220,98,121,221,90,222,115,96,223],"writing","writing skills","new","work","editing","Existing"]