[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMDP1DHSNFRFJ40R0RJZG0":3,"skill-same:01M7AMDP1DHSNFRFJ40R0RJZG0":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AMDP1DHSNFRFJ40R0RJZG0","bmad-review",null,"Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says \"review this\", \"critical review\", \"editorial review\", \"hunt edge cases\", \"review the structure\", or \"review the prose\".","zaurakworks\u002Fagent-system","zaurakworks","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F317111357?v=4","01M7AM97CDHZBZWB7HQWS5KXTG","01M7AM97D2BT6WP9MT76TV8WGG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bmad-review\ndescription: 'Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says \"review this\", \"critical review\", \"editorial review\", \"hunt edge cases\", \"review the structure\", or \"review the prose\".'\n---\n\n# BMad Review\n\nReview content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.\n\nThe lens set is whatever `{workflow.lenses}` resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.\n\n## Inputs\n\n- **content** — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args: `[path]`.\n- **lenses** (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form `skill:bmad-review lenses=\u003Ccode>[,\u003Ccode>...]` (the form bmm's `doc_standards` uses). Default: every applicable lens (a full review).\n- **also_consider** (optional) — areas to keep in mind alongside each lens's normal analysis.\n- **pre-resolved customization** (optional) — `[workflow]` field values supplied by a forwarding caller. See Execution step 1.\n\n## Conventions\n\n- Bare paths (e.g. `references\u002Flens-edge-case-hunter.md`) resolve from `{skill-root}` — this skill's installed directory, where `customize.toml` lives. `{project-root}` resolves to the project working directory.\n- `{workflow.\u003Cname>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).\n- In `style_guide`, `review_guidance`, and `persistent_facts`, a value prefixed `file:` is a path or glob — load that file's contents. If a `file:` value cannot be read, name the failed file in the output header and continue: the shipped baseline for `style_guide`, the remaining entries otherwise.\n\n## Execution\n\n1. **Resolve customization:** `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults. **Forwarded activation:** if a caller invoked you with pre-resolved customization fields (e.g. the `bmad-editorial-review` shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own `customize.toml`. Then execute each `{workflow.activation_steps_prepend}` entry in order, hold `{workflow.persistent_facts}` as standing context for the session, and treat `{workflow.review_guidance}` entries as standing review directives for every lens.\n2. **Load the content.** If it is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` (no `lens` field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is **code** or **docs**; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) is `docs` that a behavioral lens may still apply to; judge by `when`.\n3. **Select lenses** from `{workflow.lenses}`. A lens with an empty `instruction` is disabled. If the user or caller named lenses, run exactly those only — `applies_to` and `when` do not filter an explicit request. Otherwise run every enabled lens whose `applies_to` covers the content class (`any` always covers) and whose `when` applies.\n4. **Announce the plan** in one line before running anything: the content class, the lenses about to run, and — when any lens has `after` set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each `{workflow.activation_steps_append}` entry in order.\n5. **Run the independent lenses** — every selected lens without `after`. Each sees the content and `also_consider`, never another lens's findings. Follow each lens's `instruction`; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, spawn one per lens in parallel: give it the lens `instruction` with `{skill-root}` and paths resolved absolute, the content or where to read it, any `also_consider` areas, the standing review directives, and the constraint \"Return ONLY your findings — no other output.\" Otherwise run the lenses sequentially yourself, completing one before starting the next.\n6. **Run the dependent lenses** — every selected lens with `after`, once the lens it names has completed, passing that lens's findings in. A lens whose `after` target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other and may run in parallel.\n7. **Assemble and present** per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute `{workflow.on_complete}` if set.\n\n## Output\n\nOne JSON array holding every finding from every lens. Each finding carries:\n\n- `lens` — the code of the lens that produced it\n- `location` — where in the content (file:line-range for code, section for documents)\n- `trigger_condition` — the problem, or the condition that exposes it, in one line\n- `guard_snippet` — the concrete fix, guard, or missing check\n- `potential_consequence` — what goes wrong if it ships as-is\n\nEach lens file refines these semantics for its findings and may add lens-specific fields (e.g. `kind`\u002F`confidence` on deletion findings, `gap_shape`\u002F`consumer`\u002F`evidence` on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. `[]` is valid when nothing is found. No severity, priority, or ranking anywhere.\n\nPresent per `{workflow.output_format}` — `\"json\"` (the raw array in a fenced json block), `\"markdown\"`, or `\"both\"` — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per `{workflow.output_preferences}`.\n\nWhen `{workflow.report_path}` is set, write the report there; otherwise present it in chat.\n","# BMad Review\n\nReview content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.\n\nThe lens set is whatever `{workflow.lenses}` resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.\n\n## Inputs\n\n- **content** — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args: `[path]`.\n- **lenses** (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form `skill:bmad-review lenses=\u003Ccode>[,\u003Ccode>...]` (the form bmm's `doc_standards` uses). Default: every applicable lens (a full review).\n- **also_consider** (optional) — areas to keep in mind alongside each lens's normal analysis.\n- **pre-resolved customization** (optional) — `[workflow]` field values supplied by a forwarding caller. See Execution step 1.\n\n## Conventions\n\n- Bare paths (e.g. `references\u002Flens-edge-case-hunter.md`) resolve from `{skill-root}` — this skill's installed directory, where `customize.toml` lives. `{project-root}` resolves to the project working directory.\n- `{workflow.\u003Cname>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).\n- In `style_guide`, `review_guidance`, and `persistent_facts`, a value prefixed `file:` is a path or glob — load that file's contents. If a `file:` value cannot be read, name the failed file in the output header and continue: the shipped baseline for `style_guide`, the remaining entries otherwise.\n\n## Execution\n\n1. **Resolve customization:** `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults. **Forwarded activation:** if a caller invoked you with pre-resolved customization fields (e.g. the `bmad-editorial-review` shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own `customize.toml`. Then execute each `{workflow.activation_steps_prepend}` entry in order, hold `{workflow.persistent_facts}` as standing context for the session, and treat `{workflow.review_guidance}` entries as standing review directives for every lens.\n2. **Load the content.** If it is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` (no `lens` field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is **code** or **docs**; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) is `docs` that a behavioral lens may still apply to; judge by `when`.\n3. **Select lenses** from `{workflow.lenses}`. A lens with an empty `instruction` is disabled. If the user or caller named lenses, run exactly those only — `applies_to` and `when` do not filter an explicit request. Otherwise run every enabled lens whose `applies_to` covers the content class (`any` always covers) and whose `when` applies.\n4. **Announce the plan** in one line before running anything: the content class, the lenses about to run, and — when any lens has `after` set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each `{workflow.activation_steps_append}` entry in order.\n5. **Run the independent lenses** — every selected lens without `after`. Each sees the content and `also_consider`, never another lens's findings. Follow each lens's `instruction`; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, spawn one per lens in parallel: give it the lens `instruction` with `{skill-root}` and paths resolved absolute, the content or where to read it, any `also_consider` areas, the standing review directives, and the constraint \"Return ONLY your findings — no other output.\" Otherwise run the lenses sequentially yourself, completing one before starting the next.\n6. **Run the dependent lenses** — every selected lens with `after`, once the lens it names has completed, passing that lens's findings in. A lens whose `after` target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other and may run in parallel.\n7. **Assemble and present** per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute `{workflow.on_complete}` if set.\n\n## Output\n\nOne JSON array holding every finding from every lens. Each finding carries:\n\n- `lens` — the code of the lens that produced it\n- `location` — where in the content (file:line-range for code, section for documents)\n- `trigger_condition` — the problem, or the condition that exposes it, in one line\n- `guard_snippet` — the concrete fix, guard, or missing check\n- `potential_consequence` — what goes wrong if it ships as-is\n\nEach lens file refines these semantics for its findings and may add lens-specific fields (e.g. `kind`\u002F`confidence` on deletion findings, `gap_shape`\u002F`consumer`\u002F`evidence` on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. `[]` is valid when nothing is found. No severity, priority, or ranking anywhere.\n\nPresent per `{workflow.output_format}` — `\"json\"` (the raw array in a fenced json block), `\"markdown\"`, or `\"both\"` — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per `{workflow.output_preferences}`.\n\nWhen `{workflow.report_path}` is set, write the report there; otherwise present it in chat.\n",{"name":5,"description":7},"main","8d56565809c4907cf7c91fff18c6dc19fc15676a",".agents\u002Fskills\u002Fbmad-review",2,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system","https:\u002F\u002Fgithub.com\u002Fzaurakworks","2026-08-25 20:02:23",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zaurakworks\u002Fagent-system --skill bmad-review",{"tool":36,"command":37},"bunx","bunx skills add zaurakworks\u002Fagent-system --skill bmad-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zaurakworks\u002Fagent-system --skill bmad-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002FSKILL.md",true,[44,50,56,60,64,68,72,76,80,86],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"customize.toml","OTHER","其他",5903,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Fcustomize.toml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Feditorial-common.md","REFERENCE","参考文档",5811,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Feditorial-common.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Flens-adversarial.md",779,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-adversarial.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Flens-edge-case-hunter.md",3845,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-edge-case-hunter.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Flens-prose.md",1354,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-prose.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Flens-structure.md",1582,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-structure.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Flens-verification-gap.md",9518,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-verification-gap.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstructure-models.md",1972,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Freferences\u002Fstructure-models.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Ftests\u002Ftest_word_metrics.py","SCRIPT","脚本",1556,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Fscripts\u002Ftests\u002Ftest_word_metrics.py",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fword_metrics.py",3441,"https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-review\u002Fscripts\u002Fword_metrics.py",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7AMNEBBK6MPZFW7PAXPB65C","skill-maintenance","创建、审计、修正、拆分、升级、迁移或退役 Skill，或其合同／入口已漂移时，先恢复行为、授权与预算，再同步正文、调用者、版本、生成物和验证。普通业务维护、纯格式修正、承载位置未定的纠正不触发。Use for explicit Skill maintenance, not carrier choice.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-maintenance\u002Fskills\u002Fskill-maintenance\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M7AMN8D2VGEE8AX3T4B6ANWT","skill-appraisal","判定一个 Skill 组该不该进当前装配、归哪些事项、与谁重叠，或对已判定过的组按节拍复核。三种进入：首次判定新候选、补判早已在用但从未判定过的组、按失效条件复核。判定单位是组不是单个 Skill；产出必须留下失效条件与下次最少复核步骤。用于外部来源、他人所写、疑似重复或从未被判定过的组。从零设计新 Skill 用 agent-skill-design；已定下后的改造、迁移、退役用 skill-maintenance；只要外部标准与版本事实用 capability-lifecycle；对象是 knowledge 用 knowledge-maintenance。本 Skill 只产出判定，不安装、不写配置、不改 profile。Appraise a Skill group, or recheck an adopted one. Judgement only, never installs.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-appraisal\u002Fskills\u002Fskill-appraisal\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M7AMN45ZD6C1BN60Q55RG345","self-improvement","当用户指出 Agent 漂移、误解、重复犯错，要求把任务经验固化为系统改进，或讨论只增概念却不减关键未知、形成决定或可检验资产时，只暂停依赖被推翻假设的路径，重锚原问题、持久记录纠正、诊断原因，并在授权内改进入口提示词或 Skill。最小实验不能验收产品交付；普通一次性错误、偏好或任务内修复不触发完整自我优化。Use for reported drift, misunderstanding, repeated mistakes, durable Agent improvement, or abstraction loops without decisions or testable assets. Freeze only affected paths and avoid a full detour for ordinary one-off corrections.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Fself-improvement\u002Fskills\u002Fself-improvement\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7AMMXZ9PNV3H53GFNBF6Y9B","resource-observability","当用户查询 Codex／Claude 账户额度、重置时间、Codex 重置券、单 Session Token，或高成本／多 Agent 工作要决定启动、并行、降级、延后或停止时，按需读取 Orca 账户快照与固定 ccusage 回执，区分状态、来源、可信度和未知值。不要用于低风险任务、轮询、自动调度／消费权益、账单推断或长期保存快照。Use for account capacity, reset times, credits, session tokens, or consequential resource decisions. Skip routine work, polling, scheduling, automatic credit use, billing inference, and durable snapshot storage.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Fresource-observability\u002Fskills\u002Fresource-observability\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M7AMMRGYZ3629M4EJPPBSNKX","orchestrated-collaboration","当用户明确要求多 Agent／多 Session／跨 Provider 协作、任务已授权委派，或活动 Session 发生共享写入碰撞时，建立目标来源、排他所有权、可追踪交付、独立验收与综合；按共享资源和 Issue 子树确定唯一协调者，只冻结重叠或受推翻假设影响的路径。协调者参与高价值多交付件能力的拆分或设计时，由未参与者复核父目标；使用已选后端，选 Orca 时动态读 orchestration 指南。不要因复杂、额度或空闲 Agent 擅自并行，也不把试用变成长期依赖。Use for authorized multi-agent work, cross-session delegation, or shared-write collisions. Establish exclusive ownership, traceable delivery, independent acceptance, and bounded synthesis; add parent-goal review when required and avoid invented coordination or permanent platform commitments.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Forchestrated-collaboration\u002Fskills\u002Forchestrated-collaboration\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M7AMMJXXSA6WFAAJCQE8JY1A","knowledge-maintenance","用于多来源调研、可重复实验、会影响权威／Agent 配置／重要决定的研究，或用户要求复用、复核、更新当前知识时：先找已认可知识和失效条件，只补变化、冲突与缺口，再经价值门和可信门更新。不用于低成本一次性事实、原始材料／研发过程留存、私域结构设计、定时全量重查或旧仓导入。Use before multi-source research, repeatable experiments, consequential authority\u002Fconfiguration decisions, or explicit knowledge reuse. Skip cheap one-off facts, raw retention, private architecture, scheduled full re-research, and bulk legacy imports.","https:\u002F\u002Fgithub.com\u002Fzaurakworks\u002Fagent-system\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge-maintenance\u002Fskills\u002Fknowledge-maintenance\u002FSKILL.md",[],[]]