[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BV1JDP9CAS1QB4CS7K26A":3,"skill-same:01M71BV1JDP9CAS1QB4CS7K26A":73},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71BV1JDP9CAS1QB4CS7K26A","organ-lane-telemetry-cockpit",null,"Human-readable cockpit that reads originator-telemetry.jsonl, groups by traceId, and prints a compact per-run timeline with elapsed time, heartbeat count, chars streamed, and status. Use when you need to see what a lane is doing without reading raw JSONL, or when invoking lane-telemetry-cockpit to inspect lane run summaries.","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-lane-telemetry-cockpit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"organ lane telemetry cockpit","telemetry","lane","human","summaries","jsonl","with","you","workflow","when","compact","use","true","system","time","inspect","view","usage","do","harness","2026-11-10 10:12:30",false,"---\nname: organ-lane-telemetry-cockpit\ndescription: \"Human-readable cockpit that reads originator-telemetry.jsonl, groups by traceId, and prints a compact per-run timeline with elapsed time, heartbeat count, chars streamed, and status. Use when you need to see what a lane is doing without reading raw JSONL, or when invoking lane-telemetry-cockpit to inspect lane run summaries.\"\ntriggers:\n  - \"organ-lane-telemetry-cockpit\"\n  - \"how do I use lane-telemetry-cockpit\"\n  - \"lane-telemetry-cockpit usage\"\n  - \"lane-telemetry-cockpit guide\"\n  - \"Lane Telemetry Cockpit (human-readable view over YURI_LANE_TELEMETRY)\"\ngenerated: true\nsource_node: \"lane-telemetry-cockpit\"\nsource_file: \"_SYSTEM\u002FScripts\u002Flane-telemetry-cockpit.mjs\"\nscope: harness\ninvocation: workflow\n---\n\n\u003C!-- GENERATED from the canonical graph node \"lane-telemetry-cockpit\" (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 — Lane Telemetry Cockpit (human-readable view over YURI_LANE_TELEMETRY)\n\n**Module:** `_SYSTEM\u002FScripts\u002Flane-telemetry-cockpit.mjs` · **Layer:** Skills & Orchestration · **Invocation:** both · **CLI:** `(path) [--json] [--limit N]`\n\n**Purpose.** Human-readable cockpit over the Originator lane-telemetry stream. JSONL is the audit substrate, not the operator experience: this reads originator-telemetry.jsonl, groups by traceId, COLLAPSES the noisy stream\u002Fstderr\u002Fstdout chunk events into counts, and prints a compact per-run timeline (start → model call → verification → exit) with elapsed, heartbeat count, chars streamed, and status — so the operator sees what a lane is doing without reading raw JSON.\n\n## Exports\n- `readTelemetry(file = TELEMETRY, opts = {})`\n  - in: optional telemetry file path + opts\n  - out: parsed telemetry events (malformed lines tolerated)\n- `summarizeByTrace(events)`\n  - in: telemetry events\n  - out: per-traceId summary collapsing chunk events into counts (elapsed, heartbeats, chars, status)\n- `renderCockpit(traces, opts)`\n  - in: summarized traces + render opts\n  - out: the compact human-readable cockpit string\n\n## Security boundary\nStrictly READ-ONLY — reads the telemetry JSONL and renders it; never mutates telemetry. Input line-count is bounded (limit guard). No protected-path access.\n\n## When to use\nInspecting what a dispatched lane run actually did (timeline, model call, verification, exit) without parsing raw originator-telemetry JSON; triaging a slow\u002Ffailed lane run.\n\n## Gotchas\n- It collapses stream\u002Fstderr\u002Fstdout chunk events into COUNTS — individual chunk payloads are not shown (by design, to stay compact).\n- Grouping is by traceId; a run without a stable traceId will not group cleanly.\n- Read-only over a live-appended file — a snapshot reflects the moment it was read.\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 \"lane-telemetry-cockpit\" (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 — Lane Telemetry Cockpit (human-readable view over YURI_LANE_TELEMETRY)\n\n**Module:** `_SYSTEM\u002FScripts\u002Flane-telemetry-cockpit.mjs` · **Layer:** Skills & Orchestration · **Invocation:** both · **CLI:** `(path) [--json] [--limit N]`\n\n**Purpose.** Human-readable cockpit over the Originator lane-telemetry stream. JSONL is the audit substrate, not the operator experience: this reads originator-telemetry.jsonl, groups by traceId, COLLAPSES the noisy stream\u002Fstderr\u002Fstdout chunk events into counts, and prints a compact per-run timeline (start → model call → verification → exit) with elapsed, heartbeat count, chars streamed, and status — so the operator sees what a lane is doing without reading raw JSON.\n\n## Exports\n- `readTelemetry(file = TELEMETRY, opts = {})`\n  - in: optional telemetry file path + opts\n  - out: parsed telemetry events (malformed lines tolerated)\n- `summarizeByTrace(events)`\n  - in: telemetry events\n  - out: per-traceId summary collapsing chunk events into counts (elapsed, heartbeats, chars, status)\n- `renderCockpit(traces, opts)`\n  - in: summarized traces + render opts\n  - out: the compact human-readable cockpit string\n\n## Security boundary\nStrictly READ-ONLY — reads the telemetry JSONL and renders it; never mutates telemetry. Input line-count is bounded (limit guard). No protected-path access.\n\n## When to use\nInspecting what a dispatched lane run actually did (timeline, model call, verification, exit) without parsing raw originator-telemetry JSON; triaging a slow\u002Ffailed lane run.\n\n## Gotchas\n- It collapses stream\u002Fstderr\u002Fstdout chunk events into COUNTS — individual chunk payloads are not shown (by design, to stay compact).\n- Grouping is by traceId; a run without a stable traceId will not group cleanly.\n- Read-only over a live-appended file — a snapshot reflects the moment it was read.\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":27,"description":7,"source_file":50,"source_node":51},[5,45,46,47,48],"how do I use lane-telemetry-cockpit","lane-telemetry-cockpit usage","lane-telemetry-cockpit guide","Lane Telemetry Cockpit (human-readable view over YURI_LANE_TELEMETRY)",true,"_SYSTEM\u002FScripts\u002Flane-telemetry-cockpit.mjs","lane-telemetry-cockpit","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Forgan-lane-telemetry-cockpit",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-10-27 02:18:29",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill organ-lane-telemetry-cockpit",{"tool":66,"command":67},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill organ-lane-telemetry-cockpit",{"tool":69,"command":70},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill organ-lane-telemetry-cockpit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Forgan-lane-telemetry-cockpit\u002FSKILL.md",[],[74,91,114,144,173,192],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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",[],[81,82,25,38,83,84,85,31,86,30,87,28,26,88,89,90],"zoom out","zoom","how","section","re","understand","perspective","code","it","context",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[98,99,38,100,101,102,103,104,105,106,107,30,108,28,27,109,110,111,112,113],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","decisions","architecture","review","perspectives","adversarial",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"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",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[126,127,128,129,130,131,132,133,134,28,135,136,137,138,139,140,141,102,142,143],"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":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":158,"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",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[159,88,160,126,38,161,162,163,102,164,165,166,167,168,169,170,171,172,30,28],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"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",[],[180,181,182,183,184,185,186,187,188,28,189,27,190,191],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":210,"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",[198,201,204,207],{"categoryNo":199,"categoryName":200,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":202,"categoryName":203,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":205,"categoryName":206,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":208,"categoryName":209,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000036","内容创作者",[211,212,213,28,27,214,38,215,103,30,216],"writing","writing skills","new","work","editing","Existing"]