[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP0YZPRVZ0NNNZER512F1J":3,"skill-same:01M6MP0YZPRVZ0NNNZER512F1J":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":63},"01M6MP0YZPRVZ0NNNZER512F1J","refocus",null,"Audits an existing Clean Room run and steers it back to missed gates without expanding declared scope.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Frefocus\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"run","manifest","json","clean","task","back","missed","artifact","gates","scope","it","true","clean room","Existing","2026-11-10 10:12:30",false,"---\nname: refocus\ndescription: Audits an existing Clean Room run and steers it back to missed gates without expanding declared scope.\nargument-hint: [existing task-manifest.json or artifact roots]\ndisable-model-invocation: true\n---\n\n# Clean Room Refocus\n\nRefocus realigns the current run to the declared scope, controller policy, artifact schemas, and clean-room boundary.\n\nRefocus does not optimize, expand, or reinterpret the task. It does not invent new requirements or add behavior beyond `preflight-goal.json`, `task-manifest.json`, `clean-run-context.json`, ledgers, implementation plan\u002Freport, QC, and abstract delta tickets.\n\nUse the canonical `clean-room` skill workflow and references in this plugin. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.\n\n## Audit\n\nCompare current artifacts to the canonical gate checklist:\n\n- Scope gate recorded authorization, roots, boundaries, prohibited actions, evidence handling, selected target profile, Agent 0-4 pipeline, and Agent 1.5 sanitizer role for new runs.\n- Preflight goal exists for new runs, validates against `preflight-goal.schema.json`, and is referenced by `task-manifest.json` with `preflight_goal_ref` and `preflight_goal_sha256`.\n- Task manifest records the required `handoff_sequence` and does not skip Stage 0.\n- Initialization snapshot exists when init preferences were used, and reusable `init-config.json` drift is reported instead of silently applied.\n- `clean-run-context.json` exists before clean roles run and excludes source roots, visual roots, contaminated roots, source index refs, visual index refs, and ledger paths.\n- `clean-run-context.json` records artifact-only coordination: Agent 0 does not directly steer Agent 2, Agent 3, or Agent 4, and clean implementation\u002Fpolish roles report to Agent 0 only at terminal status.\n- When context management is enabled, the next role launch can be driven by a fresh `role-session-brief.json` inside the recorded budgets. `controller-status.json` remains contaminated-side only.\n- Implementation roots are recorded, separated, and not source-derived.\n- Source index or visual-index fallback preflight exists when required and remains contaminated-only.\n- Decomposition produced neutral `task-manifest.json` units.\n- Contaminated analysis wrote draft behavior specs without implementation code.\n- Agent 1.5 sanitization ran before handoff, or older artifacts clearly predate the Agent 1.5 gate and require review before reuse.\n- Handoff package excludes full `task-manifest.json`, `source-index.json`, `visual-index.json`, raw screenshots, source or visual paths, raw diffs, copied comments, copied visible words, private identifiers, exact UI palettes\u002Flayouts\u002Ficonography, source-shaped pseudocode, and contaminated ledgers.\n- Agent 2 produced clean-only `implementation-plan.json` when the run reached that gate.\n- Agent 3 produced `implementation-report.json` when the run reached implementation.\n- Non-terminal Agent 3 implementation reports were not used as Agent 0 feedback or guidance.\n- QC produced `qc-report.json` with schema, leakage, coverage, and abstract delta ticket status when the run reached that gate.\n- Agent 4 produced `polish-report.json` when the run reached final polish review.\n- Contaminated verification returned only abstract delta tickets.\n\nValidate schemas and handoff hashes before trusting the artifacts. Use `source-index.json` or `visual-index.json` only on the contaminated side and only when referenced by the task manifest.\n\n## Findings\n\nEmit missed-gate findings only:\n\n- Missing required artifact.\n- Invalid schema.\n- Failed or missing leakage review.\n- Invalid or stale handoff hash.\n- Boundary violation or unproven root separation.\n- Stale handoff compared with latest QC or ledger state.\n- Stale implementation plan compared with latest clean handoff.\n- Stale implementation report compared with latest implementation plan.\n- Controller policy not preserved.\n- Missing, invalid, or drifted preflight goal.\n- Noncanonical manifests, reports, ledgers, or manual result summaries used as completion evidence. Mark these `not verified` unless `clean-room-skill run --dry-run` (or `npx clean-room-skill@latest run --dry-run` if the binary is not available) succeeds against the canonical `task-manifest.json`.\n- Missing public-surface inventory parity: required public commands, APIs, config keys, protocol entries, or user-visible behaviors listed in approved specs are not mapped through behavior spec tests, implementation-plan `public_contract_refs`, terminal implementation reports, and coverage-ledger `public_surface_coverage`.\n\nDo not suggest speculative improvements. Do not change source scope, target profile, public API, or implementation plan.\nIf the user asks to add scope, stop and route to a new scope gate instead of silently expanding the run.\n\n## Output\n\nReturn a bounded next-action plan containing:\n\n- Current verified gate.\n- Missed gate findings.\n- One to three process corrections, ordered by safety.\n- The single next action the controller should take.\n\nIf root separation, authorization, or clean\u002Fcontaminated boundary cannot be proven, the single next action is to stop and repair that gate.\n","# Clean Room Refocus\n\nRefocus realigns the current run to the declared scope, controller policy, artifact schemas, and clean-room boundary.\n\nRefocus does not optimize, expand, or reinterpret the task. It does not invent new requirements or add behavior beyond `preflight-goal.json`, `task-manifest.json`, `clean-run-context.json`, ledgers, implementation plan\u002Freport, QC, and abstract delta tickets.\n\nUse the canonical `clean-room` skill workflow and references in this plugin. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.\n\n## Audit\n\nCompare current artifacts to the canonical gate checklist:\n\n- Scope gate recorded authorization, roots, boundaries, prohibited actions, evidence handling, selected target profile, Agent 0-4 pipeline, and Agent 1.5 sanitizer role for new runs.\n- Preflight goal exists for new runs, validates against `preflight-goal.schema.json`, and is referenced by `task-manifest.json` with `preflight_goal_ref` and `preflight_goal_sha256`.\n- Task manifest records the required `handoff_sequence` and does not skip Stage 0.\n- Initialization snapshot exists when init preferences were used, and reusable `init-config.json` drift is reported instead of silently applied.\n- `clean-run-context.json` exists before clean roles run and excludes source roots, visual roots, contaminated roots, source index refs, visual index refs, and ledger paths.\n- `clean-run-context.json` records artifact-only coordination: Agent 0 does not directly steer Agent 2, Agent 3, or Agent 4, and clean implementation\u002Fpolish roles report to Agent 0 only at terminal status.\n- When context management is enabled, the next role launch can be driven by a fresh `role-session-brief.json` inside the recorded budgets. `controller-status.json` remains contaminated-side only.\n- Implementation roots are recorded, separated, and not source-derived.\n- Source index or visual-index fallback preflight exists when required and remains contaminated-only.\n- Decomposition produced neutral `task-manifest.json` units.\n- Contaminated analysis wrote draft behavior specs without implementation code.\n- Agent 1.5 sanitization ran before handoff, or older artifacts clearly predate the Agent 1.5 gate and require review before reuse.\n- Handoff package excludes full `task-manifest.json`, `source-index.json`, `visual-index.json`, raw screenshots, source or visual paths, raw diffs, copied comments, copied visible words, private identifiers, exact UI palettes\u002Flayouts\u002Ficonography, source-shaped pseudocode, and contaminated ledgers.\n- Agent 2 produced clean-only `implementation-plan.json` when the run reached that gate.\n- Agent 3 produced `implementation-report.json` when the run reached implementation.\n- Non-terminal Agent 3 implementation reports were not used as Agent 0 feedback or guidance.\n- QC produced `qc-report.json` with schema, leakage, coverage, and abstract delta ticket status when the run reached that gate.\n- Agent 4 produced `polish-report.json` when the run reached final polish review.\n- Contaminated verification returned only abstract delta tickets.\n\nValidate schemas and handoff hashes before trusting the artifacts. Use `source-index.json` or `visual-index.json` only on the contaminated side and only when referenced by the task manifest.\n\n## Findings\n\nEmit missed-gate findings only:\n\n- Missing required artifact.\n- Invalid schema.\n- Failed or missing leakage review.\n- Invalid or stale handoff hash.\n- Boundary violation or unproven root separation.\n- Stale handoff compared with latest QC or ledger state.\n- Stale implementation plan compared with latest clean handoff.\n- Stale implementation report compared with latest implementation plan.\n- Controller policy not preserved.\n- Missing, invalid, or drifted preflight goal.\n- Noncanonical manifests, reports, ledgers, or manual result summaries used as completion evidence. Mark these `not verified` unless `clean-room-skill run --dry-run` (or `npx clean-room-skill@latest run --dry-run` if the binary is not available) succeeds against the canonical `task-manifest.json`.\n- Missing public-surface inventory parity: required public commands, APIs, config keys, protocol entries, or user-visible behaviors listed in approved specs are not mapped through behavior spec tests, implementation-plan `public_contract_refs`, terminal implementation reports, and coverage-ledger `public_surface_coverage`.\n\nDo not suggest speculative improvements. Do not change source scope, target profile, public API, or implementation plan.\nIf the user asks to add scope, stop and route to a new scope gate instead of silently expanding the run.\n\n## Output\n\nReturn a bounded next-action plan containing:\n\n- Current verified gate.\n- Missed gate findings.\n- One to three process corrections, ordered by safety.\n- The single next action the controller should take.\n\nIf root separation, authorization, or clean\u002Fcontaminated boundary cannot be proven, the single next action is to stop and repair that gate.\n",{"name":5,"description":7,"argument-hint":38,"disable-model-invocation":40},[39],"existing task-manifest.json or artifact roots",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Frefocus",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":40},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refocus",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refocus",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill refocus","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Frefocus\u002FSKILL.md",[],[65,75,83,91,99,107],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":69,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":74},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":74},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"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":69,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":74},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":74},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":74},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]