[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP8BH6NFST5S92DZF16GMP":3,"skill-same:01M6MP8BH6NFST5S92DZF16GMP":77},{"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":26,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6MP8BH6NFST5S92DZF16GMP","document-review",null,"Optional utility for reviewing existing docs, external specs, hand-authored notes, or non-HOTL documents. HOTL design docs and workflows get structural lint + AI review; other documents get AI-only review with a generic rubric.","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\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fdocument-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"review","document","document review","generic","design","hotl","Existing","for","hand","with","utility","design docs","structural","get","only","rubric","lint","notes","documents","workflows","docs","2026-11-10 10:12:30",false,"---\nname: document-review\ndescription: Optional utility for reviewing existing docs, external specs, hand-authored notes, or non-HOTL documents. HOTL design docs and workflows get structural lint + AI review; other documents get AI-only review with a generic rubric.\n---\n\n# HOTL Document Review\n\n## Overview\n\nOptional utility for ad hoc document review. Use this to review existing docs, external specs, hand-authored plans, or any non-HOTL document. HOTL documents get structural lint (hard gate) followed by AI review. Non-HOTL documents skip lint and go straight to AI review with a generic rubric.\n\n**Note:** This skill is not required in the standard HOTL flow. Writing-plans includes a built-in self-check, and execution preflight runs structural lint automatically. Use this skill when you want to review a document outside of the normal plan-then-execute cycle.\n\n**Announce:** \"Running document review. Classifying input...\"\n\n## Step 0 — Classify the Input\n\nBefore doing anything else, classify the input into one of four categories:\n\n| Category | Detection | Review Path |\n|---|---|---|\n| **HOTL workflow** | Canonical `docs\u002Fplans\u002F*-workflow.md` or legacy `hotl-workflow-*.md` | Phase 1 (HOTL lint, hard gate) → Phase 2 (HOTL AI review) |\n| **HOTL design doc (marked)** | A design-doc-shaped file (canonical `docs\u002Fdesigns\u002F*.md` or legacy `*-design.md` \u002F `*-plan.md`) whose YAML frontmatter declares `design_type:` (one of `feature \\| phase \\| initiative \\| architecture \\| contract \\| reference`) OR `hotl_managed: true` | Phase 1 (HOTL lint) → Phase 2 (HOTL AI review) |\n| **Generic text\u002Fmarkdown** | Any other `.md`, `.txt`, or pasted text — including design-shaped files in `docs\u002Fdesigns\u002F` that lack an HOTL marker | Skip Phase 1 → Phase 2 (generic AI review) |\n| **PDF** | `.pdf` extension | If the current runtime can read\u002Fextract the content, treat as generic text and review. Otherwise, ask the user for a text, markdown, or PDF-text export. |\n| **DOCX \u002F PPTX \u002F binary** | `.docx`, `.pptx`, or other binary formats | **STOP.** Ask the user for a markdown, plain text, or PDF export. Do not attempt conversion. |\n\n**Phase 1.6 opt-in rule:** Path alone does NOT classify a file as HOTL. A design-shaped Markdown file in `docs\u002Fdesigns\u002F` without an HOTL frontmatter marker (`design_type:` or `hotl_managed: true`) is treated as generic markdown — `document-lint.sh` will SKIP it cleanly, and this skill routes it through Phase 2's generic-rubric AI review. To opt a hand-authored design doc into HOTL strict review, add `design_type: \u003Crecognized-value>` or `hotl_managed: true` to its frontmatter.\n\n**Announce the classification:** e.g., \"Classified as HOTL design doc (marked via design_type) — running lint + HOTL review.\" or \"Classified as generic markdown — skipping lint, running generic review.\"\n\n## Phase 1: Structural Lint (HOTL Documents Only)\n\n**Skip this phase entirely for non-HOTL documents.** If the input was classified as generic text\u002Fmarkdown or PDF, go directly to Phase 2 (generic AI review).\n\nFor HOTL documents only, run the deterministic lint script:\n\n```bash\nbash scripts\u002Fdocument-lint.sh \u003Cfile>\n```\n\nResolve `document-lint.sh` in this order:\n\n1. If you are working in the `hotl-plugin` repo itself, use `scripts\u002Fdocument-lint.sh`\n2. Codex native-skills install: `~\u002F.codex\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n3. Codex plugin install: `~\u002F.codex\u002Fplugins\u002Fhotl-source\u002Fscripts\u002Fdocument-lint.sh`\n4. Codex plugin cache fallback: `~\u002F.codex\u002Fplugins\u002Fcache\u002Fcodex-plugins\u002Fhotl\u002F*\u002Fscripts\u002Fdocument-lint.sh`\n5. Cline install fallback: `~\u002F.cline\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n6. Claude Code plugin fallback: `~\u002F.claude\u002Fplugins\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n\nDo not assume `scripts\u002Fdocument-lint.sh` exists in the repo being reviewed. The lint script lives in the HOTL install, not in arbitrary user projects.\n\n#### Resolving `hotl-config.sh`\n\n`hotl-config.sh` (the canonical reader for `.hotl\u002Fconfig.yml`) follows the same six-location resolution order as `document-lint.sh`:\n\n1. If you are working in the `hotl-plugin` repo itself, use `scripts\u002Fhotl-config.sh`\n2. Codex native-skills install: `~\u002F.codex\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n3. Codex plugin install: `~\u002F.codex\u002Fplugins\u002Fhotl-source\u002Fscripts\u002Fhotl-config.sh`\n4. Codex plugin cache fallback: `~\u002F.codex\u002Fplugins\u002Fcache\u002Fcodex-plugins\u002Fhotl\u002F*\u002Fscripts\u002Fhotl-config.sh`\n5. Cline install fallback: `~\u002F.cline\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n6. Claude Code plugin fallback: `~\u002F.claude\u002Fplugins\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n\nDo not assume `scripts\u002Fhotl-config.sh` exists in the repo being reviewed. Callers that do not know their install location should invoke `scripts\u002Fhotl-config-resolve.sh` (a thin command proxy that locates `hotl-config.sh` and forwards argv).\n\n**If lint FAILS:** STOP. Show all errors. The author MUST fix structural issues before AI review runs. Do not proceed.\n\n**If lint PASSES:** Continue to Phase 2 (HOTL AI review).\n\n### What Lint Checks\n\n**Design docs (canonical `docs\u002Fdesigns\u002F*.md`, plus legacy `*-design.md` \u002F `*-plan.md` tactical docs):**\n- Intent Contract with intent, constraints, success_criteria, risk_level\n- Verification Contract with at least one verify step\n- Governance Contract with approval_gates and rollback\n- risk_level is low, medium, or high\n\n**Workflow files (canonical `docs\u002Fplans\u002F*-workflow.md`, plus legacy `hotl-workflow-*.md`):**\n- YAML frontmatter with intent, success_criteria, risk_level\n- Every step has action and loop fields\n- Every looped step (loop: until) has verify and max_iterations\n- Preferred workflow step syntax is `- [ ] **Step N: ...**`, though legacy `### N.` headings may still appear\n- High-risk steps with security keywords have gate: human\n\n## Phase 2: AI-Driven Review (Soft Gate)\n\nRead the full document and evaluate using the rubric that matches the classification:\n\n### For Design Docs\n\n1. **Internal consistency** — Do the three contracts align with each other? Does the verification contract actually test the intent?\n2. **YAGNI** — Is anything speculative, overbuilt, or solving problems that don't exist yet?\n3. **Risk assessment** — Is the risk_level appropriate? Are high-risk areas (auth, encryption, billing) correctly identified?\n4. **Success criteria** — Are they concrete and testable, or vague?\n5. **Scope** — Does this cross too many subsystems? Should it be decomposed?\n\n### For Workflow Files\n\n1. **Step sizing** — Are steps atomic (2-5 minutes each)? Flag steps that are too large or vague.\n2. **Verify coverage** — Do verify commands actually test what the step claims to do?\n3. **Gate placement** — Are human gates placed at the right points? Any risky steps missing gates?\n4. **Loop safety** — Are max_iterations reasonable? Any infinite-loop risks?\n5. **Ordering** — Do steps build on each other logically? Any missing dependencies?\n\n### For Generic Documents\n\n1. **Clarity** — Is the writing clear, specific, and unambiguous?\n2. **Completeness** — Are important details, assumptions, or decisions missing?\n3. **Internal consistency** — Does the document contradict itself anywhere?\n4. **Actionability** — Are decisions, next steps, owners, or open questions clearly stated?\n5. **Risk \u002F Ambiguity** — Are there risky assumptions, vague areas, or likely points of confusion?\n\n## Review Outcomes\n\nAfter completing the review, output exactly one of the following. Use `Lint: PASSED` for HOTL documents or `Lint: SKIPPED (non-HOTL document)` for all other inputs.\n\n### PASS\nAll checks satisfied. Document is ready.\n\n```\nREVIEW: PASS\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: No issues found.\nReady for execution.\n```\n\n### REVISE\nIssues found that should be fixed. List each with a specific suggestion.\n\n```\nREVIEW: REVISE\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: \u003CN> issue(s) found.\n\nIssues:\n1. [ISSUE]: \u003Cdescription>\n   Suggestion: \u003Chow to fix>\n2. [ISSUE]: \u003Cdescription>\n   Suggestion: \u003Chow to fix>\n\nFix these issues and re-run document review.\n```\n\n### HUMAN_OVERRIDE_REQUIRED\nSerious concerns that the AI cannot resolve. Human must decide whether to proceed.\n\n```\nREVIEW: HUMAN_OVERRIDE_REQUIRED\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: Serious concern(s) requiring human judgment.\n\nConcerns:\n1. [CONCERN]: \u003Cdescription>\n   Risk: \u003Cwhat could go wrong>\n2. [CONCERN]: \u003Cdescription>\n   Risk: \u003Cwhat could go wrong>\n\nDo not continue until a human explicitly says to override these concerns.\n```\n\n## Rules\n\n- Always classify the input before choosing a review path.\n- For HOTL documents: never skip lint; never continue to execution when lint fails.\n- For non-HOTL documents: skip lint entirely (no structural validation).\n- For DOCX\u002FPPTX\u002Fbinary: do not attempt conversion; ask for an export.\n- If review outcome is `REVISE`, the author fixes the document first.\n- If review outcome is `HUMAN_OVERRIDE_REQUIRED`, only an explicit human decision allows execution to proceed.\n","# HOTL Document Review\n\n## Overview\n\nOptional utility for ad hoc document review. Use this to review existing docs, external specs, hand-authored plans, or any non-HOTL document. HOTL documents get structural lint (hard gate) followed by AI review. Non-HOTL documents skip lint and go straight to AI review with a generic rubric.\n\n**Note:** This skill is not required in the standard HOTL flow. Writing-plans includes a built-in self-check, and execution preflight runs structural lint automatically. Use this skill when you want to review a document outside of the normal plan-then-execute cycle.\n\n**Announce:** \"Running document review. Classifying input...\"\n\n## Step 0 — Classify the Input\n\nBefore doing anything else, classify the input into one of four categories:\n\n| Category | Detection | Review Path |\n|---|---|---|\n| **HOTL workflow** | Canonical `docs\u002Fplans\u002F*-workflow.md` or legacy `hotl-workflow-*.md` | Phase 1 (HOTL lint, hard gate) → Phase 2 (HOTL AI review) |\n| **HOTL design doc (marked)** | A design-doc-shaped file (canonical `docs\u002Fdesigns\u002F*.md` or legacy `*-design.md` \u002F `*-plan.md`) whose YAML frontmatter declares `design_type:` (one of `feature \\| phase \\| initiative \\| architecture \\| contract \\| reference`) OR `hotl_managed: true` | Phase 1 (HOTL lint) → Phase 2 (HOTL AI review) |\n| **Generic text\u002Fmarkdown** | Any other `.md`, `.txt`, or pasted text — including design-shaped files in `docs\u002Fdesigns\u002F` that lack an HOTL marker | Skip Phase 1 → Phase 2 (generic AI review) |\n| **PDF** | `.pdf` extension | If the current runtime can read\u002Fextract the content, treat as generic text and review. Otherwise, ask the user for a text, markdown, or PDF-text export. |\n| **DOCX \u002F PPTX \u002F binary** | `.docx`, `.pptx`, or other binary formats | **STOP.** Ask the user for a markdown, plain text, or PDF export. Do not attempt conversion. |\n\n**Phase 1.6 opt-in rule:** Path alone does NOT classify a file as HOTL. A design-shaped Markdown file in `docs\u002Fdesigns\u002F` without an HOTL frontmatter marker (`design_type:` or `hotl_managed: true`) is treated as generic markdown — `document-lint.sh` will SKIP it cleanly, and this skill routes it through Phase 2's generic-rubric AI review. To opt a hand-authored design doc into HOTL strict review, add `design_type: \u003Crecognized-value>` or `hotl_managed: true` to its frontmatter.\n\n**Announce the classification:** e.g., \"Classified as HOTL design doc (marked via design_type) — running lint + HOTL review.\" or \"Classified as generic markdown — skipping lint, running generic review.\"\n\n## Phase 1: Structural Lint (HOTL Documents Only)\n\n**Skip this phase entirely for non-HOTL documents.** If the input was classified as generic text\u002Fmarkdown or PDF, go directly to Phase 2 (generic AI review).\n\nFor HOTL documents only, run the deterministic lint script:\n\n```bash\nbash scripts\u002Fdocument-lint.sh \u003Cfile>\n```\n\nResolve `document-lint.sh` in this order:\n\n1. If you are working in the `hotl-plugin` repo itself, use `scripts\u002Fdocument-lint.sh`\n2. Codex native-skills install: `~\u002F.codex\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n3. Codex plugin install: `~\u002F.codex\u002Fplugins\u002Fhotl-source\u002Fscripts\u002Fdocument-lint.sh`\n4. Codex plugin cache fallback: `~\u002F.codex\u002Fplugins\u002Fcache\u002Fcodex-plugins\u002Fhotl\u002F*\u002Fscripts\u002Fdocument-lint.sh`\n5. Cline install fallback: `~\u002F.cline\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n6. Claude Code plugin fallback: `~\u002F.claude\u002Fplugins\u002Fhotl\u002Fscripts\u002Fdocument-lint.sh`\n\nDo not assume `scripts\u002Fdocument-lint.sh` exists in the repo being reviewed. The lint script lives in the HOTL install, not in arbitrary user projects.\n\n#### Resolving `hotl-config.sh`\n\n`hotl-config.sh` (the canonical reader for `.hotl\u002Fconfig.yml`) follows the same six-location resolution order as `document-lint.sh`:\n\n1. If you are working in the `hotl-plugin` repo itself, use `scripts\u002Fhotl-config.sh`\n2. Codex native-skills install: `~\u002F.codex\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n3. Codex plugin install: `~\u002F.codex\u002Fplugins\u002Fhotl-source\u002Fscripts\u002Fhotl-config.sh`\n4. Codex plugin cache fallback: `~\u002F.codex\u002Fplugins\u002Fcache\u002Fcodex-plugins\u002Fhotl\u002F*\u002Fscripts\u002Fhotl-config.sh`\n5. Cline install fallback: `~\u002F.cline\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n6. Claude Code plugin fallback: `~\u002F.claude\u002Fplugins\u002Fhotl\u002Fscripts\u002Fhotl-config.sh`\n\nDo not assume `scripts\u002Fhotl-config.sh` exists in the repo being reviewed. Callers that do not know their install location should invoke `scripts\u002Fhotl-config-resolve.sh` (a thin command proxy that locates `hotl-config.sh` and forwards argv).\n\n**If lint FAILS:** STOP. Show all errors. The author MUST fix structural issues before AI review runs. Do not proceed.\n\n**If lint PASSES:** Continue to Phase 2 (HOTL AI review).\n\n### What Lint Checks\n\n**Design docs (canonical `docs\u002Fdesigns\u002F*.md`, plus legacy `*-design.md` \u002F `*-plan.md` tactical docs):**\n- Intent Contract with intent, constraints, success_criteria, risk_level\n- Verification Contract with at least one verify step\n- Governance Contract with approval_gates and rollback\n- risk_level is low, medium, or high\n\n**Workflow files (canonical `docs\u002Fplans\u002F*-workflow.md`, plus legacy `hotl-workflow-*.md`):**\n- YAML frontmatter with intent, success_criteria, risk_level\n- Every step has action and loop fields\n- Every looped step (loop: until) has verify and max_iterations\n- Preferred workflow step syntax is `- [ ] **Step N: ...**`, though legacy `### N.` headings may still appear\n- High-risk steps with security keywords have gate: human\n\n## Phase 2: AI-Driven Review (Soft Gate)\n\nRead the full document and evaluate using the rubric that matches the classification:\n\n### For Design Docs\n\n1. **Internal consistency** — Do the three contracts align with each other? Does the verification contract actually test the intent?\n2. **YAGNI** — Is anything speculative, overbuilt, or solving problems that don't exist yet?\n3. **Risk assessment** — Is the risk_level appropriate? Are high-risk areas (auth, encryption, billing) correctly identified?\n4. **Success criteria** — Are they concrete and testable, or vague?\n5. **Scope** — Does this cross too many subsystems? Should it be decomposed?\n\n### For Workflow Files\n\n1. **Step sizing** — Are steps atomic (2-5 minutes each)? Flag steps that are too large or vague.\n2. **Verify coverage** — Do verify commands actually test what the step claims to do?\n3. **Gate placement** — Are human gates placed at the right points? Any risky steps missing gates?\n4. **Loop safety** — Are max_iterations reasonable? Any infinite-loop risks?\n5. **Ordering** — Do steps build on each other logically? Any missing dependencies?\n\n### For Generic Documents\n\n1. **Clarity** — Is the writing clear, specific, and unambiguous?\n2. **Completeness** — Are important details, assumptions, or decisions missing?\n3. **Internal consistency** — Does the document contradict itself anywhere?\n4. **Actionability** — Are decisions, next steps, owners, or open questions clearly stated?\n5. **Risk \u002F Ambiguity** — Are there risky assumptions, vague areas, or likely points of confusion?\n\n## Review Outcomes\n\nAfter completing the review, output exactly one of the following. Use `Lint: PASSED` for HOTL documents or `Lint: SKIPPED (non-HOTL document)` for all other inputs.\n\n### PASS\nAll checks satisfied. Document is ready.\n\n```\nREVIEW: PASS\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: No issues found.\nReady for execution.\n```\n\n### REVISE\nIssues found that should be fixed. List each with a specific suggestion.\n\n```\nREVIEW: REVISE\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: \u003CN> issue(s) found.\n\nIssues:\n1. [ISSUE]: \u003Cdescription>\n   Suggestion: \u003Chow to fix>\n2. [ISSUE]: \u003Cdescription>\n   Suggestion: \u003Chow to fix>\n\nFix these issues and re-run document review.\n```\n\n### HUMAN_OVERRIDE_REQUIRED\nSerious concerns that the AI cannot resolve. Human must decide whether to proceed.\n\n```\nREVIEW: HUMAN_OVERRIDE_REQUIRED\nDocument: \u003Cfilename>\nLint: PASSED | SKIPPED (non-HOTL document)\nAI Review: Serious concern(s) requiring human judgment.\n\nConcerns:\n1. [CONCERN]: \u003Cdescription>\n   Risk: \u003Cwhat could go wrong>\n2. [CONCERN]: \u003Cdescription>\n   Risk: \u003Cwhat could go wrong>\n\nDo not continue until a human explicitly says to override these concerns.\n```\n\n## Rules\n\n- Always classify the input before choosing a review path.\n- For HOTL documents: never skip lint; never continue to execution when lint fails.\n- For non-HOTL documents: skip lint entirely (no structural validation).\n- For DOCX\u002FPPTX\u002Fbinary: do not attempt conversion; ask for an export.\n- If review outcome is `REVISE`, the author fixes the document first.\n- If review outcome is `HUMAN_OVERRIDE_REQUIRED`, only an explicit human decision allows execution to proceed.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fdocument-review",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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill document-review",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill document-review",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill document-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fdocument-review\u002FSKILL.md",true,[],[78,88,96,104,112,120],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"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",[],[]]