[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MK8TFP9AJ1NWQFSXNK66XE":3,"skill-same:01M6MK8TFP9AJ1NWQFSXNK66XE":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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":66},"01M6MK8TFP9AJ1NWQFSXNK66XE","skill-coverage-audit",null,"Trace codepaths in diffs, map against tests, auto-generate missing coverage — use before shipping PRs","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\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-coverage-audit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"audit","coverage","skill coverage audit","diffs","generate","shipping","trace","use","auto","map","tests","missing","true","prs","2026-11-10 10:12:30",false,"---\nname: skill-coverage-audit\ndescription: \"Trace codepaths in diffs, map against tests, auto-generate missing coverage — use before shipping PRs\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Test Coverage Audit\n\n## Artifact consistency before implementation\n\nWhen invoked at a spec\u002Fplan\u002Ftasks boundary, use the feature boundary adapter rather than this skill's code-test generation mode. It automatically runs bounded deterministic checks for coverage, declared paths, stable IDs, explicit terminology\u002Fenums\u002Fcounts and verified policy references. A single artifact skips analysis; a clean pass costs no seat. Reports are advisory and quote the original sources. Escalation uses at most one independent seat, and unavailable or failed semantic review leaves the deterministic results usable.\n\n## Overview\n\nTrace every codepath in a diff, map each path against existing tests, visualize coverage gaps, and auto-generate tests for uncovered paths.\n\n**Core principle:** Trace codepaths in changed files -> Map against existing tests -> Score coverage quality -> Generate tests for gaps -> Report before\u002Fafter counts.\n\n\n## Caps and Limits\n\nThese hard limits prevent runaway analysis:\n\n- **30 code paths max** per audit. If a diff yields more than 30, prioritize by complexity and risk (error paths, security-sensitive branches, public API surfaces first).\n- **20 tests generated max** per audit. Focus on highest-impact gaps first.\n- **2-minute per-test exploration cap.** If understanding a single test path takes longer than 2 minutes, mark it as \"needs manual review\" and move on.\n\n\n## Phase 1: Codepath Tracing\n\n### Step 1: Identify Changed Files\n\nDetermine the diff scope. Use the most relevant source:\n\n```bash\n# PR diff\ngit diff --name-only main...HEAD\n\n# Staged changes\ngit diff --name-only --cached\n\n# Last commit\ngit diff --name-only HEAD~1..HEAD\n```\n\nFilter to source code files only (exclude configs, docs, generated files).\n\n### Step 2: Trace Data Flow Through Every Branch\n\nFor each changed file, you MUST trace:\n\n1. **Conditionals** -- Every `if\u002Felse`, `switch\u002Fcase`, ternary, and pattern match. Each branch is a separate codepath.\n2. **Error paths** -- Every `catch`, `throw`, error return, validation failure, and early return with error. WHY: Error paths are the most common source of untested bugs.\n3. **Function calls** -- Every function invoked from changed code. Trace one level deep into callees to identify integration boundaries.\n4. **Loop boundaries** -- Empty collection, single item, and multi-item paths through loops.\n5. **Guard clauses** -- Every early return, null check, and permission gate.\n\n### Step 3: Build the Codepath Inventory\n\nProduce a structured inventory:\n\n```markdown\n## Codepath Inventory: [filename]\n\n| # | Path Description | Type | Risk |\n|---|-----------------|------|------|\n| 1 | validateUser() happy path | conditional | low |\n| 2 | validateUser() missing email | error | medium |\n| 3 | validateUser() invalid format | error | medium |\n| 4 | processOrder() empty cart guard | guard | high |\n| 5 | processOrder() payment timeout | error | high |\n| 6 | processOrder() success | conditional | low |\n```\n\n**Type categories:** `conditional`, `error`, `guard`, `loop-boundary`, `integration`, `async`\n\n**Risk assessment:** `high` = user-facing failure or data loss, `medium` = degraded behavior, `low` = cosmetic or logging\n\n\n## Phase 2: Test Mapping and Quality Scoring\n\n### Step 1: Search for Existing Tests\n\nFor each file in the diff, search the test directory for related tests:\n\n```bash\n# Find test files that reference the changed file or its exports\n# Search by filename pattern\nfind tests\u002F -name \"*[changed_file_stem]*\" -type f\n\n# Search by import\u002Frequire of the changed module\ngrep -rl \"import.*from.*[module_name]\" tests\u002F\ngrep -rl \"require.*[module_name]\" tests\u002F\n\n# Search by function name references\ngrep -rl \"[function_name]\" tests\u002F\n```\n\n### Step 2: Score Test Quality\n\nFor each codepath, assess existing test coverage with this rubric:\n\n| Rating | Meaning | Criteria |\n|--------|---------|----------|\n| ★★★ | Behavior + edge cases tested | Tests assert behavior AND cover boundary conditions, error cases, and edge inputs |\n| ★★ | Happy path tested | Tests cover the success path but miss error branches or edge cases |\n| ★ | Smoke test only | Test exists but only checks the function runs without error (no meaningful assertions) |\n| ☆ | No test found | No test references this codepath at all |\n\n### Step 3: Produce Coverage Map\n\nMap each codepath to its test coverage:\n\n```markdown\n## Coverage Map: [filename]\n\n| # | Codepath | Test File | Rating | Notes |\n|---|----------|-----------|--------|-------|\n| 1 | validateUser() happy path | test-user.sh:42 | ★★★ | Asserts valid + invalid inputs |\n| 2 | validateUser() missing email | test-user.sh:58 | ★★ | Tests missing, not malformed |\n| 3 | validateUser() invalid format | -- | ☆ | No test for format validation |\n| 4 | processOrder() empty cart guard | -- | ☆ | Guard clause untested |\n| 5 | processOrder() payment timeout | test-orders.sh:30 | ★ | Checks no crash, no assertions |\n| 6 | processOrder() success | test-orders.sh:15 | ★★★ | Full integration test |\n```\n\n\n## Phase 3: Coverage Diagram\n\nAfter completing the map, produce an ASCII coverage summary. This is the primary output artifact.\n\n```\nCOVERAGE: 5\u002F12 paths tested (42%)\n  Code paths: 3\u002F5 (60%)\n  User flows: 2\u002F7 (29%)\nGAPS: 7 paths need tests\n```\n\nBreak down by category:\n\n```\nBY TYPE:\n  conditional:  3\u002F4 tested (75%)  ████████░░\n  error:        1\u002F5 tested (20%)  ██░░░░░░░░\n  guard:        0\u002F2 tested  (0%)  ░░░░░░░░░░\n  integration:  1\u002F1 tested (100%) ██████████\n\nBY RISK:\n  high:    1\u002F3 tested (33%)  ███░░░░░░░\n  medium:  2\u002F5 tested (40%)  ████░░░░░░\n  low:     2\u002F4 tested (50%)  █████░░░░░\n```\n\nUse full block for covered and light shade for uncovered. 10-character bar. Always show exact fractions and percentages.\n\n\n## Phase 4: Auto-Generate Tests\n\n### Step 1: Detect Project Test Conventions\n\nBefore generating any tests, you MUST detect the project's testing patterns:\n\n```markdown\n**Detected Test Conventions:**\n- Framework: [jest\u002Fvitest\u002Fpytest\u002Fbash\u002Fgo test\u002Fetc.]\n- Location: [tests\u002F | __tests__\u002F | src\u002F**\u002F*.test.* | etc.]\n- Naming: [test-*.sh | *.test.ts | *_test.go | etc.]\n- Style: [BDD describe\u002Fit | xUnit | TAP | custom]\n- Helpers: [test-utils.ts | conftest.py | helpers\u002F | etc.]\n- Assertion library: [built-in | chai | assert | etc.]\n```\n\n### Step 2: Generate Tests for Uncovered Paths\n\nFor each no-test and smoke-only codepath, generate a test that:\n\n1. **Follows project naming conventions** -- same directory structure, same file naming pattern\n2. **Uses existing test helpers** -- import from the same test utilities the project already uses\n3. **Tests behavior, not implementation** -- assert observable outcomes, not internal state\n4. **Covers the specific gap** -- targets the exact branch or error path identified in Phase 1\n5. **Includes edge cases** -- aim for full coverage on each generated test\n\n### Step 3: Present Generated Tests\n\nFor each generated test, show:\n\n```markdown\n### Generated: test for [codepath description]\n**Covers:** Codepath #N from [filename]\n**Raises coverage:** from no-test to full coverage\n\n[test code block]\n```\n\n### Step 4: Report Before\u002FAfter\n\nAfter generating all tests, show the coverage change:\n\n```\nBEFORE: 5\u002F12 paths tested (42%)\nAFTER:  11\u002F12 paths tested (92%)\n  New tests generated: 6\n  Remaining gaps: 1 (manual review needed)\n```\n\n\n## Integration with Other Skills\n\n### With flow-deliver \u002F skill-code-review\n\nCoverage audit runs as a complement to code review. When invoked during deliver phase:\n1. Code review assesses quality and correctness\n2. Coverage audit assesses test completeness\n3. Both feed into the ship\u002Fno-ship decision\n\n### With skill-tdd\n\nIf coverage audit finds gaps in new code, recommend the user adopt TDD for the next iteration. Coverage audit fixes existing gaps; TDD prevents future ones.\n\n### With skill-verification-gate\n\nAfter generating tests, use skill-verification-gate to run the test suite and confirm the new tests pass.\n\n\n## Red Flags -- Do Not Do This\n\n| Action | Why It Is Wrong |\n|--------|-----------------|\n| Count lines instead of paths | Line coverage misses branch coverage entirely |\n| Generate tests without checking conventions | Tests that do not match project style will be rejected |\n| Test implementation details | Brittle tests that break on refactoring |\n| Skip error paths | Error paths are where most bugs live |\n| Exceed the 30-path cap | Analysis becomes unfocused and slow |\n| Generate more than 20 tests | Diminishing returns; focus on highest impact |\n| Spend more than 2 min on one path | Mark as needs-manual-review and move on |\n\n\n## Quick Reference\n\n```\n1. TRACE   -> Identify all codepaths in the diff (max 30)\n2. MAP     -> Find existing tests for each path\n3. SCORE   -> Rate coverage quality (no-test \u002F smoke \u002F happy-path \u002F full)\n4. DIAGRAM -> ASCII coverage visualization\n5. GENERATE -> Auto-create tests for gaps (max 20)\n6. REPORT  -> Before\u002Fafter test counts\n```\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Test Coverage Audit\n\n## Artifact consistency before implementation\n\nWhen invoked at a spec\u002Fplan\u002Ftasks boundary, use the feature boundary adapter rather than this skill's code-test generation mode. It automatically runs bounded deterministic checks for coverage, declared paths, stable IDs, explicit terminology\u002Fenums\u002Fcounts and verified policy references. A single artifact skips analysis; a clean pass costs no seat. Reports are advisory and quote the original sources. Escalation uses at most one independent seat, and unavailable or failed semantic review leaves the deterministic results usable.\n\n## Overview\n\nTrace every codepath in a diff, map each path against existing tests, visualize coverage gaps, and auto-generate tests for uncovered paths.\n\n**Core principle:** Trace codepaths in changed files -> Map against existing tests -> Score coverage quality -> Generate tests for gaps -> Report before\u002Fafter counts.\n\n\n## Caps and Limits\n\nThese hard limits prevent runaway analysis:\n\n- **30 code paths max** per audit. If a diff yields more than 30, prioritize by complexity and risk (error paths, security-sensitive branches, public API surfaces first).\n- **20 tests generated max** per audit. Focus on highest-impact gaps first.\n- **2-minute per-test exploration cap.** If understanding a single test path takes longer than 2 minutes, mark it as \"needs manual review\" and move on.\n\n\n## Phase 1: Codepath Tracing\n\n### Step 1: Identify Changed Files\n\nDetermine the diff scope. Use the most relevant source:\n\n```bash\n# PR diff\ngit diff --name-only main...HEAD\n\n# Staged changes\ngit diff --name-only --cached\n\n# Last commit\ngit diff --name-only HEAD~1..HEAD\n```\n\nFilter to source code files only (exclude configs, docs, generated files).\n\n### Step 2: Trace Data Flow Through Every Branch\n\nFor each changed file, you MUST trace:\n\n1. **Conditionals** -- Every `if\u002Felse`, `switch\u002Fcase`, ternary, and pattern match. Each branch is a separate codepath.\n2. **Error paths** -- Every `catch`, `throw`, error return, validation failure, and early return with error. WHY: Error paths are the most common source of untested bugs.\n3. **Function calls** -- Every function invoked from changed code. Trace one level deep into callees to identify integration boundaries.\n4. **Loop boundaries** -- Empty collection, single item, and multi-item paths through loops.\n5. **Guard clauses** -- Every early return, null check, and permission gate.\n\n### Step 3: Build the Codepath Inventory\n\nProduce a structured inventory:\n\n```markdown\n## Codepath Inventory: [filename]\n\n| # | Path Description | Type | Risk |\n|---|-----------------|------|------|\n| 1 | validateUser() happy path | conditional | low |\n| 2 | validateUser() missing email | error | medium |\n| 3 | validateUser() invalid format | error | medium |\n| 4 | processOrder() empty cart guard | guard | high |\n| 5 | processOrder() payment timeout | error | high |\n| 6 | processOrder() success | conditional | low |\n```\n\n**Type categories:** `conditional`, `error`, `guard`, `loop-boundary`, `integration`, `async`\n\n**Risk assessment:** `high` = user-facing failure or data loss, `medium` = degraded behavior, `low` = cosmetic or logging\n\n\n## Phase 2: Test Mapping and Quality Scoring\n\n### Step 1: Search for Existing Tests\n\nFor each file in the diff, search the test directory for related tests:\n\n```bash\n# Find test files that reference the changed file or its exports\n# Search by filename pattern\nfind tests\u002F -name \"*[changed_file_stem]*\" -type f\n\n# Search by import\u002Frequire of the changed module\ngrep -rl \"import.*from.*[module_name]\" tests\u002F\ngrep -rl \"require.*[module_name]\" tests\u002F\n\n# Search by function name references\ngrep -rl \"[function_name]\" tests\u002F\n```\n\n### Step 2: Score Test Quality\n\nFor each codepath, assess existing test coverage with this rubric:\n\n| Rating | Meaning | Criteria |\n|--------|---------|----------|\n| ★★★ | Behavior + edge cases tested | Tests assert behavior AND cover boundary conditions, error cases, and edge inputs |\n| ★★ | Happy path tested | Tests cover the success path but miss error branches or edge cases |\n| ★ | Smoke test only | Test exists but only checks the function runs without error (no meaningful assertions) |\n| ☆ | No test found | No test references this codepath at all |\n\n### Step 3: Produce Coverage Map\n\nMap each codepath to its test coverage:\n\n```markdown\n## Coverage Map: [filename]\n\n| # | Codepath | Test File | Rating | Notes |\n|---|----------|-----------|--------|-------|\n| 1 | validateUser() happy path | test-user.sh:42 | ★★★ | Asserts valid + invalid inputs |\n| 2 | validateUser() missing email | test-user.sh:58 | ★★ | Tests missing, not malformed |\n| 3 | validateUser() invalid format | -- | ☆ | No test for format validation |\n| 4 | processOrder() empty cart guard | -- | ☆ | Guard clause untested |\n| 5 | processOrder() payment timeout | test-orders.sh:30 | ★ | Checks no crash, no assertions |\n| 6 | processOrder() success | test-orders.sh:15 | ★★★ | Full integration test |\n```\n\n\n## Phase 3: Coverage Diagram\n\nAfter completing the map, produce an ASCII coverage summary. This is the primary output artifact.\n\n```\nCOVERAGE: 5\u002F12 paths tested (42%)\n  Code paths: 3\u002F5 (60%)\n  User flows: 2\u002F7 (29%)\nGAPS: 7 paths need tests\n```\n\nBreak down by category:\n\n```\nBY TYPE:\n  conditional:  3\u002F4 tested (75%)  ████████░░\n  error:        1\u002F5 tested (20%)  ██░░░░░░░░\n  guard:        0\u002F2 tested  (0%)  ░░░░░░░░░░\n  integration:  1\u002F1 tested (100%) ██████████\n\nBY RISK:\n  high:    1\u002F3 tested (33%)  ███░░░░░░░\n  medium:  2\u002F5 tested (40%)  ████░░░░░░\n  low:     2\u002F4 tested (50%)  █████░░░░░\n```\n\nUse full block for covered and light shade for uncovered. 10-character bar. Always show exact fractions and percentages.\n\n\n## Phase 4: Auto-Generate Tests\n\n### Step 1: Detect Project Test Conventions\n\nBefore generating any tests, you MUST detect the project's testing patterns:\n\n```markdown\n**Detected Test Conventions:**\n- Framework: [jest\u002Fvitest\u002Fpytest\u002Fbash\u002Fgo test\u002Fetc.]\n- Location: [tests\u002F | __tests__\u002F | src\u002F**\u002F*.test.* | etc.]\n- Naming: [test-*.sh | *.test.ts | *_test.go | etc.]\n- Style: [BDD describe\u002Fit | xUnit | TAP | custom]\n- Helpers: [test-utils.ts | conftest.py | helpers\u002F | etc.]\n- Assertion library: [built-in | chai | assert | etc.]\n```\n\n### Step 2: Generate Tests for Uncovered Paths\n\nFor each no-test and smoke-only codepath, generate a test that:\n\n1. **Follows project naming conventions** -- same directory structure, same file naming pattern\n2. **Uses existing test helpers** -- import from the same test utilities the project already uses\n3. **Tests behavior, not implementation** -- assert observable outcomes, not internal state\n4. **Covers the specific gap** -- targets the exact branch or error path identified in Phase 1\n5. **Includes edge cases** -- aim for full coverage on each generated test\n\n### Step 3: Present Generated Tests\n\nFor each generated test, show:\n\n```markdown\n### Generated: test for [codepath description]\n**Covers:** Codepath #N from [filename]\n**Raises coverage:** from no-test to full coverage\n\n[test code block]\n```\n\n### Step 4: Report Before\u002FAfter\n\nAfter generating all tests, show the coverage change:\n\n```\nBEFORE: 5\u002F12 paths tested (42%)\nAFTER:  11\u002F12 paths tested (92%)\n  New tests generated: 6\n  Remaining gaps: 1 (manual review needed)\n```\n\n\n## Integration with Other Skills\n\n### With flow-deliver \u002F skill-code-review\n\nCoverage audit runs as a complement to code review. When invoked during deliver phase:\n1. Code review assesses quality and correctness\n2. Coverage audit assesses test completeness\n3. Both feed into the ship\u002Fno-ship decision\n\n### With skill-tdd\n\nIf coverage audit finds gaps in new code, recommend the user adopt TDD for the next iteration. Coverage audit fixes existing gaps; TDD prevents future ones.\n\n### With skill-verification-gate\n\nAfter generating tests, use skill-verification-gate to run the test suite and confirm the new tests pass.\n\n\n## Red Flags -- Do Not Do This\n\n| Action | Why It Is Wrong |\n|--------|-----------------|\n| Count lines instead of paths | Line coverage misses branch coverage entirely |\n| Generate tests without checking conventions | Tests that do not match project style will be rejected |\n| Test implementation details | Brittle tests that break on refactoring |\n| Skip error paths | Error paths are where most bugs live |\n| Exceed the 30-path cap | Analysis becomes unfocused and slow |\n| Generate more than 20 tests | Diminishing returns; focus on highest impact |\n| Spend more than 2 min on one path | Mark as needs-manual-review and move on |\n\n\n## Quick Reference\n\n```\n1. TRACE   -> Identify all codepaths in the diff (max 30)\n2. MAP     -> Find existing tests for each path\n3. SCORE   -> Rate coverage quality (no-test \u002F smoke \u002F happy-path \u002F full)\n4. DIAGRAM -> ASCII coverage visualization\n5. GENERATE -> Auto-create tests for gaps (max 20)\n6. REPORT  -> Before\u002Fafter test counts\n```\n",{"name":5,"description":7,"disable-model-invocation":43},true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-coverage-audit",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":55,"prompt":65,"zipAvailable":43},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-coverage-audit",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-coverage-audit",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-coverage-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-coverage-audit\u002FSKILL.md",[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",172,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-coverage-audit\u002Fagents\u002Fopenai.yaml",[74,84,92,100,108,116],{"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":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":83},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":83},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":83},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":83},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":83},"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",[],[]]