[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BTPRHH1T04R1MBDZDRRNF":3,"skill-same:01M71BTPRHH1T04R1MBDZDRRNF":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":73},"01M71BTPRHH1T04R1MBDZDRRNF","organ-discovery-precision-gate",null,"Gates a lane claim against its WorkSubstrate scope and discovery footprint before the energy gate runs, verifying the lane stayed inside its granted authority. Use when a lane produces a claim that needs scope-and-footprint verification, or when invoking discovery-precision-gate to filter claims before energy evaluation.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Forgan-discovery-precision-gate\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"gate","organ discovery precision gate","discovery","how","energy","verification","claims","filter","gates","when","use","authority","true","claim","system","lane","scope","usage","do","harness","2026-11-10 10:12:30",false,"---\nname: organ-discovery-precision-gate\ndescription: \"Gates a lane claim against its WorkSubstrate scope and discovery footprint before the energy gate runs, verifying the lane stayed inside its granted authority. Use when a lane produces a claim that needs scope-and-footprint verification, or when invoking discovery-precision-gate to filter claims before energy evaluation.\"\ntriggers:\n  - \"organ-discovery-precision-gate\"\n  - \"how do I use discovery-precision-gate\"\n  - \"discovery-precision-gate usage\"\n  - \"discovery-precision-gate guide\"\n  - \"Discovery Precision Gate (scope + footprint filter before the energy gate)\"\ngenerated: true\nsource_node: \"discovery-precision-gate\"\nsource_file: \"_SYSTEM\u002FScripts\u002Fdiscovery-precision-gate.mjs\"\nscope: harness\ninvocation: ability\n---\n\n\u003C!-- GENERATED from the canonical graph node \"discovery-precision-gate\" (mechanism.guide) by _SYSTEM\u002FScripts\u002Fyuri-guide-project.mjs.\n     DO NOT hand-edit — edit _SYSTEM\u002Forgan-guides.json, then run: node _SYSTEM\u002FScripts\u002Fyuri-guide-seed.mjs && node _SYSTEM\u002FScripts\u002Fyuri-guide-project.mjs -->\n\n# Organ Guide — Discovery Precision Gate (scope + footprint filter before the energy gate)\n\n**Module:** `_SYSTEM\u002FScripts\u002Fdiscovery-precision-gate.mjs` · **Layer:** Governance & Safety · **Invocation:** both · **CLI:** none (import-only surface)\n\n**Purpose.** Gates a lane claim against its WorkSubstrate scope + discovery footprint BEFORE the energy gate runs. The energy gate scores a transition's quality; this is the upstream filter asking 'did the lane stay inside the authority it was granted, and how precise was its discovery?'. Rides on yuri-id-bridge (isProtectedPath\u002FnormalizePath — the protected veto) and yuri-navigate (impact centrality — the claim's blast radius).\n\n## Exports\n- `discoveryPrecisionGate(claim = {})`\n  - in: a claim { targets, scope (allowed\u002Fdenied), discovery records }\n  - out: { verdict, vetoes, precision, footprint, advisory_only } — a hard protected\u002Fscope veto blocks; precision is reported\n- `async withNavigate(claim, substrate, opts = {})`\n  - in: a claim + substrate + opts\n  - out: the gate verdict enriched with yuri-navigate impact centrality (blast radius of the claim's graph targets)\n\n## Security boundary\nADVISORY pre-filter with a HARD veto: a protected-path or out-of-scope target produces a blocking veto (fail-closed via isProtectedPath, which is traversal-hardened so '..\u002F'-escapes are caught). Precision + impact are advisory_only (reported for the downstream energy\u002Fproof gates + operator). Reads the graph via yuri-navigate; writes nothing. Deterministic (sorted, no RNG\u002Fclock).\n\n## When to use\nBefore accepting a lane's claim\u002Ftransition — to confirm it stayed inside granted authority (scope + protected paths) and to surface how precise\u002Fwide-blast its discovery was, upstream of the energy gate.\n\n## Gotchas\n- The verdict is ADVISORY except the protected\u002Fscope VETO, which is a hard block — do not treat the precision score as a gate by itself.\n- Protected-path detection is realpath\u002Ftraversal-hardened (yuri-id-bridge), not lexical — '..\u002F' escapes are caught.\n- withNavigate is async (graph impact lookup); high impact_centrality means 'surface for review', not automatic block.\n\n## Session Notes\n\n### 2026-06-13\n- session: 40m | peak ctx: 0% | compacts: 0\n- tools: Bash×824, Read×163, Edit×17, StructuredOutput×16, Write×8, TodoWrite×4, ToolSearch×2, ScheduleWakeup×2, Workflow×1, mcp×1, AskUserQuestion×1\n- corrections: none\n- errors: none\n","\u003C!-- GENERATED from the canonical graph node \"discovery-precision-gate\" (mechanism.guide) by _SYSTEM\u002FScripts\u002Fyuri-guide-project.mjs.\n     DO NOT hand-edit — edit _SYSTEM\u002Forgan-guides.json, then run: node _SYSTEM\u002FScripts\u002Fyuri-guide-seed.mjs && node _SYSTEM\u002FScripts\u002Fyuri-guide-project.mjs -->\n\n# Organ Guide — Discovery Precision Gate (scope + footprint filter before the energy gate)\n\n**Module:** `_SYSTEM\u002FScripts\u002Fdiscovery-precision-gate.mjs` · **Layer:** Governance & Safety · **Invocation:** both · **CLI:** none (import-only surface)\n\n**Purpose.** Gates a lane claim against its WorkSubstrate scope + discovery footprint BEFORE the energy gate runs. The energy gate scores a transition's quality; this is the upstream filter asking 'did the lane stay inside the authority it was granted, and how precise was its discovery?'. Rides on yuri-id-bridge (isProtectedPath\u002FnormalizePath — the protected veto) and yuri-navigate (impact centrality — the claim's blast radius).\n\n## Exports\n- `discoveryPrecisionGate(claim = {})`\n  - in: a claim { targets, scope (allowed\u002Fdenied), discovery records }\n  - out: { verdict, vetoes, precision, footprint, advisory_only } — a hard protected\u002Fscope veto blocks; precision is reported\n- `async withNavigate(claim, substrate, opts = {})`\n  - in: a claim + substrate + opts\n  - out: the gate verdict enriched with yuri-navigate impact centrality (blast radius of the claim's graph targets)\n\n## Security boundary\nADVISORY pre-filter with a HARD veto: a protected-path or out-of-scope target produces a blocking veto (fail-closed via isProtectedPath, which is traversal-hardened so '..\u002F'-escapes are caught). Precision + impact are advisory_only (reported for the downstream energy\u002Fproof gates + operator). Reads the graph via yuri-navigate; writes nothing. Deterministic (sorted, no RNG\u002Fclock).\n\n## When to use\nBefore accepting a lane's claim\u002Ftransition — to confirm it stayed inside granted authority (scope + protected paths) and to surface how precise\u002Fwide-blast its discovery was, upstream of the energy gate.\n\n## Gotchas\n- The verdict is ADVISORY except the protected\u002Fscope VETO, which is a hard block — do not treat the precision score as a gate by itself.\n- Protected-path detection is realpath\u002Ftraversal-hardened (yuri-id-bridge), not lexical — '..\u002F' escapes are caught.\n- withNavigate is async (graph impact lookup); high impact_centrality means 'surface for review', not automatic block.\n\n## Session Notes\n\n### 2026-06-13\n- session: 40m | peak ctx: 0% | compacts: 0\n- tools: Bash×824, Read×163, Edit×17, StructuredOutput×16, Write×8, TodoWrite×4, ToolSearch×2, ScheduleWakeup×2, Workflow×1, mcp×1, AskUserQuestion×1\n- corrections: none\n- errors: none\n",{"name":5,"scope":38,"triggers":44,"generated":49,"invocation":50,"description":7,"source_file":51,"source_node":52},[5,45,46,47,48],"how do I use discovery-precision-gate","discovery-precision-gate usage","discovery-precision-gate guide","Discovery Precision Gate (scope + footprint filter before the energy gate)",true,"ability","_SYSTEM\u002FScripts\u002Fdiscovery-precision-gate.mjs","discovery-precision-gate","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Forgan-discovery-precision-gate",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-11 16:42:59",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":49},[63,66,69],{"tool":64,"command":65},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill organ-discovery-precision-gate",{"tool":67,"command":68},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill organ-discovery-precision-gate",{"tool":70,"command":71},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill organ-discovery-precision-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Forgan-discovery-precision-gate\u002FSKILL.md",[],[75,93,117,147,176,195],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":39},"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.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[82,83,84,38,22,85,86,31,87,29,88,28,89,90,91,92],"zoom out","zoom","with","section","re","understand","perspective","you","code","it","context",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":39},"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",[],[100,101,38,102,103,104,105,106,107,108,109,29,110,28,111,112,113,114,115,116],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":39},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[129,130,131,132,133,134,135,136,137,28,138,139,140,141,142,143,144,104,145,146],"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":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":161,"publishedAt":39},"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",[153,156],{"categoryNo":154,"categoryName":155,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[162,90,163,129,38,164,165,166,104,167,168,169,170,171,172,173,174,175,29,28],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"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",[],[183,184,185,186,187,188,189,190,191,28,192,111,193,194],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":213,"publishedAt":39},"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",[201,204,207,210],{"categoryNo":202,"categoryName":203,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":205,"categoryName":206,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":208,"categoryName":209,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":211,"categoryName":212,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000036","内容创作者",[214,215,216,28,111,217,38,218,105,29,219],"writing","writing skills","new","work","editing","Existing"]