[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG7SM245TKS7XVGDTTCRB8":3,"skill-same:01M6MG7SM245TKS7XVGDTTCRB8":61},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6MG7SM245TKS7XVGDTTCRB8","audit",null,"Audit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs PASS\u002FWARN\u002FFAIL per dimension. Validates spec coverage.","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\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Faudit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"review","spec","security","code quality","code","parallel","quality","coverage","tests","semantic","mode","phase","outputs","2026-11-10 10:12:30",false,"---\nname: audit\ndescription: \"Audit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs PASS\u002FWARN\u002FFAIL per dimension. Validates spec coverage.\"\n---\n\n# Audit — Verify Everything\n\n**CRITICAL**: Run `HARNESS_DIR=$(epic path)` first. NEVER use `.harness\u002F` in the project directory.\n\n## Execution Modes\n\nThis skill has 3 internal modes that run in parallel:\n\n1. **audit:code** — Code quality, logic, style, test coverage, spec coverage\n2. **audit:security** — OWASP Top 10 + performance (N+1, leaks)\n3. **audit:test** — Full test suite, AC verification, coverage delta\n\n### `--strict` Mode (Trust Boundary Isolation)\n\nWhen invoked with `--strict` (or when `.harness\u002Fengagement.md` has `mode: strict`), the audit enforces independence between verification agents to prevent reward hacking:\n\n- **Artifact-only delivery**: Each mode receives only the code diff and spec — no builder context, no session history, no prior agent conclusions.\n- **Cross-check independence**: `audit:code` and `audit:security` run without visibility into each other's findings. Results are combined only during synthesis (Step 4).\n- **Blind scoring**: No mode can see another mode's verdict until synthesis. This prevents anchoring bias where a clean code review inflates the security score.\n- **No self-review**: If the same agent built the code (via `\u002Fgo`), a different agent instance must run audit. The builder's session ID is checked and excluded.\n\nUse `--strict` for security-sensitive projects, compliance requirements, or when the build phase had ambiguous outcomes.\n\n---\n\n## Process\n\n### Step 0: Prerequisites\n\nConfirm go has run:\n```bash\ngit symbolic-ref --short HEAD  # must NOT be main\u002Fmaster\n```\n\nLoad the spec to know what was supposed to be built:\n```bash\nls -t $HARNESS_DIR\u002Fspecs\u002FSPEC-*.md | head -1\n```\nRead the Requirements and Acceptance Criteria sections.\n\n### Step 1: Gather Scope\n\n```bash\ngit diff --stat $(git merge-base HEAD main)\ngit diff --name-only $(git merge-base HEAD main)\ngit diff --numstat $(git merge-base HEAD main)\n```\n\n**Over-edit signal.** From `--numstat`, flag any file whose added+removed lines exceed 100 while the spec has 2 or fewer Requirements, or any file the spec never mentions. Flagged files get the Diff minimality check in audit:code. Typical cause: a formatter the project never adopted rewrote the whole file (quote style, line wrapping, import splitting).\n\n### Step 2: Scope Detection\n\n| Pattern | Scope | Extra checks |\n|---------|-------|-------------|\n| `*.api.*`, `*route*`, `*controller*`, `*handler*` | API | + Contract testing, request validation |\n| `*.tsx`, `*.jsx`, `*.vue`, `*.svelte`, `*.css` | Frontend | + Accessibility, semantic HTML |\n| `*.sql`, `*migration*`, `*schema*` | Database | + Migration safety, rollback plan |\n| `*.rs`, `Cargo.toml`, `*.go`, `go.mod` | Backend | + Build verification, type safety |\n| `*.test.*`, `*.spec.*`, `__tests__\u002F` | Tests | + Coverage delta, flaky test detection |\n| `Dockerfile*`, `*.yml`, `*.yaml`, `Makefile` | Infra | + Config validation, secret detection |\n| `*.md`, `*.txt` | Docs | + Link checking, freshness |\n\n### Step 3: Run Checks in Parallel\n\nLaunch all 3 modes with `run_in_background: true`.\n\n**`--strict` isolation protocol**: When strict mode is active, each mode agent must be launched with:\n- Only the diff output from Step 1 as input (no session context)\n- No access to other modes' intermediate or final results\n- A fresh context window containing only: spec, diff, and the mode-specific checklist\n\nThis ensures each mode forms independent conclusions. Results are combined only in Step 4 synthesis.\n\n---\n\n## Mode: audit:code (Review)\n\n### Constraints\n- Be specific — cite file and line number for every finding\n- Suggest fixes, don't just flag problems — every finding needs a one-line fix hint\n\n### Review Dimensions\n\n1. **Correctness**: Does the code do what it claims? Edge cases handled?\n2. **Logic**: Race conditions, off-by-one, null pointer risks?\n3. **Style**: Consistent with project conventions? Readable?\n4. **Tests**: Changes covered by tests? Tests meaningful?\n5. **Naming**: Do names clearly convey intent?\n6. **Spec coverage**: Each Requirement addressed in the diff?\n7. **Diff minimality**: Every hunk traces to a Requirement. Hunks that only reformat, re-wrap, re-quote, or reorder untouched code are WARN; list them and revert before ship.\n\n### Output Format\n\n```\n## Code Review: \u003Cfile or area>\n- [BLOCKER] \u003Cdescription> (line X)\n- [WARN] \u003Cdescription> (line Y)\n- [NIT] \u003Cdescription> (line Z)\n\n## Summary\n- Blockers: N\n- Warnings: N\n- Verdict: APPROVE \u002F REQUEST_CHANGES\n```\n\n---\n\n## Mode: audit:security (Security)\n\n### Constraints\n- False positives are better than false negatives for security\n- Always check `.env` files are in `.gitignore`\n\n### Security Checklist (OWASP Top 10)\n\n1. Injection (SQL, XSS, command)\n2. Broken authentication\n3. Sensitive data exposure\n4. Access control failures\n5. Security misconfiguration\n\n### Performance Checklist\n\n1. N+1 queries\n2. Unbounded data loading\n3. Missing indexes\n4. Memory leaks (event listeners, growing caches)\n5. Blocking main thread\n\n### Output Format\n\n```\n## Security Audit\n- [CRITICAL] SQL injection risk in \u003Cfile>:\u003Cline>\n- [HIGH] Hardcoded secret in \u003Cfile>:\u003Cline>\n- [MEDIUM] Missing rate limit on \u003Cendpoint>\n\n## Performance Audit\n- [HIGH] N+1 query in \u003Cfile>:\u003Cline>\n- [MEDIUM] Unbounded array growth in \u003Cfile>:\u003Cline>\n\n## Summary\n- Security: PASS \u002F FAIL (N critical, N high)\n- Performance: PASS \u002F WARN (N issues)\n```\n\n---\n\n## Mode: audit:test (Test Runner)\n\n1. Run the full test suite\n2. Verify each Acceptance Criterion is demonstrably met\n3. Report coverage delta\n4. Flag any flaky tests\n\n---\n\n### Step 3.5: Semantic Deduplication\n\nAfter all 3 modes complete, merge their findings and deduplicate:\n\n**Collection**: Gather all findings from code, security, and test modes into a single pool.\n\n**Root-Cause Grouping**: For each finding, identify the root cause. Findings sharing the same root cause (same file, same function, same underlying pattern) form a group.\n\n**Classification** (per group):\n\n| Classification | Meaning | Action |\n|---------------|---------|--------|\n| `NEW` | First finding for this root cause | Include in report |\n| `DUP_BETTER` | Duplicate with better evidence or higher severity | Replace original with this |\n| `DUP_SKIP` | Duplicate with weaker or equal evidence | Drop; reference the `NEW` finding |\n\n**Severity Reassessment**: The surviving finding in each group takes the highest severity across all modes. For example, if code review says `[WARN]` but security says `[CRITICAL]` for the same root cause, the deduped finding is `[CRITICAL]`.\n\n**Output**: Only deduplicated findings proceed to Step 4 synthesis. The report should note: \"N findings deduplicated from M total (K groups collapsed).\"\n\n---\n\n### Step 4: Synthesize\n\nCombine deduplicated findings into a single report:\n\n```\n## Audit Report\n- Spec: SPEC-{timestamp} ({goal_slug})\n- Branch: {current branch}\n\n### Change Scope\n- Scopes detected: [API, Frontend, Backend, Database, Infra, Docs, Tests]\n- Scope-specific checks: [list what ran]\n\n### Code Quality: [PASS\u002FWARN\u002FFAIL]\n### Security: [PASS\u002FWARN\u002FFAIL]\n### Performance: [PASS\u002FWARN\u002FFAIL]\n### Tests: [X\u002FY passing, Z% coverage]\n\n### Deduplication\n- Total findings: M\n- Deduplicated: N (K groups collapsed)\n\n### Spec Coverage\n- R1: ✅\u002F❌ addressed in diff\n- R2: ✅\u002F❌ addressed in diff\n- AC1: ✅\u002F❌ verified by test\n- AC2: ✅\u002F❌ verified by test\n\n### Action Items\n1. [blocker or warning]\n```\n\n### Step 5: Act\n\n- **All PASS + all AC verified**: **\"Audit passed. Run `\u002Fship` to create a PR.\"**\n- **WARN**: Show warnings, ask if user wants to fix before shipping\n- **FAIL or AC missing**: List each blocker with a one-line fix hint. **\"Fix with `\u002Fgo`, then re-run `\u002Faudit`.\"**\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"It's a small change, skip security\" | Small changes introduce big vulnerabilities | Always run the security checklist |\n| \"Tests are passing, that's enough\" | Tests don't catch security or performance issues | Run all 3 modes |\n| \"I'll fix the warnings later\" | Later never comes | Fix blockers now, warnings before merge |\n| \"Dedup is overkill for small audits\" | Small audits can still have cross-mode overlap | Always dedup — the cost is trivial |\n| \"Strict mode is overkill\" | Without isolation, the builder can influence reviewers via shared context | Use `--strict` for security-sensitive or compliance-driven projects |\n| \"The agents are independent enough\" | Shared context creates anchoring bias — a clean code review inflates security scores | Strict mode ensures blind scoring until synthesis |\n\n## Evidence Required\n\n- [ ] All 3 modes (code, security, test) completed\n- [ ] Each Requirement has a coverage verdict\n- [ ] Each AC has a test\u002Fverification verdict\n- [ ] No BLOCKER items remain on PASS\n- [ ] Deduplication applied: total vs. deduplicated count reported\n\n## Red Flags\n\n- Skipping security review for \"small changes\"\n- Approving code with failing tests\n- Ignoring performance warnings in hot paths\n- Marking audit PASS when any AC is unverified\n- Reporting raw findings without deduplication\n","# Audit — Verify Everything\n\n**CRITICAL**: Run `HARNESS_DIR=$(epic path)` first. NEVER use `.harness\u002F` in the project directory.\n\n## Execution Modes\n\nThis skill has 3 internal modes that run in parallel:\n\n1. **audit:code** — Code quality, logic, style, test coverage, spec coverage\n2. **audit:security** — OWASP Top 10 + performance (N+1, leaks)\n3. **audit:test** — Full test suite, AC verification, coverage delta\n\n### `--strict` Mode (Trust Boundary Isolation)\n\nWhen invoked with `--strict` (or when `.harness\u002Fengagement.md` has `mode: strict`), the audit enforces independence between verification agents to prevent reward hacking:\n\n- **Artifact-only delivery**: Each mode receives only the code diff and spec — no builder context, no session history, no prior agent conclusions.\n- **Cross-check independence**: `audit:code` and `audit:security` run without visibility into each other's findings. Results are combined only during synthesis (Step 4).\n- **Blind scoring**: No mode can see another mode's verdict until synthesis. This prevents anchoring bias where a clean code review inflates the security score.\n- **No self-review**: If the same agent built the code (via `\u002Fgo`), a different agent instance must run audit. The builder's session ID is checked and excluded.\n\nUse `--strict` for security-sensitive projects, compliance requirements, or when the build phase had ambiguous outcomes.\n\n---\n\n## Process\n\n### Step 0: Prerequisites\n\nConfirm go has run:\n```bash\ngit symbolic-ref --short HEAD  # must NOT be main\u002Fmaster\n```\n\nLoad the spec to know what was supposed to be built:\n```bash\nls -t $HARNESS_DIR\u002Fspecs\u002FSPEC-*.md | head -1\n```\nRead the Requirements and Acceptance Criteria sections.\n\n### Step 1: Gather Scope\n\n```bash\ngit diff --stat $(git merge-base HEAD main)\ngit diff --name-only $(git merge-base HEAD main)\ngit diff --numstat $(git merge-base HEAD main)\n```\n\n**Over-edit signal.** From `--numstat`, flag any file whose added+removed lines exceed 100 while the spec has 2 or fewer Requirements, or any file the spec never mentions. Flagged files get the Diff minimality check in audit:code. Typical cause: a formatter the project never adopted rewrote the whole file (quote style, line wrapping, import splitting).\n\n### Step 2: Scope Detection\n\n| Pattern | Scope | Extra checks |\n|---------|-------|-------------|\n| `*.api.*`, `*route*`, `*controller*`, `*handler*` | API | + Contract testing, request validation |\n| `*.tsx`, `*.jsx`, `*.vue`, `*.svelte`, `*.css` | Frontend | + Accessibility, semantic HTML |\n| `*.sql`, `*migration*`, `*schema*` | Database | + Migration safety, rollback plan |\n| `*.rs`, `Cargo.toml`, `*.go`, `go.mod` | Backend | + Build verification, type safety |\n| `*.test.*`, `*.spec.*`, `__tests__\u002F` | Tests | + Coverage delta, flaky test detection |\n| `Dockerfile*`, `*.yml`, `*.yaml`, `Makefile` | Infra | + Config validation, secret detection |\n| `*.md`, `*.txt` | Docs | + Link checking, freshness |\n\n### Step 3: Run Checks in Parallel\n\nLaunch all 3 modes with `run_in_background: true`.\n\n**`--strict` isolation protocol**: When strict mode is active, each mode agent must be launched with:\n- Only the diff output from Step 1 as input (no session context)\n- No access to other modes' intermediate or final results\n- A fresh context window containing only: spec, diff, and the mode-specific checklist\n\nThis ensures each mode forms independent conclusions. Results are combined only in Step 4 synthesis.\n\n---\n\n## Mode: audit:code (Review)\n\n### Constraints\n- Be specific — cite file and line number for every finding\n- Suggest fixes, don't just flag problems — every finding needs a one-line fix hint\n\n### Review Dimensions\n\n1. **Correctness**: Does the code do what it claims? Edge cases handled?\n2. **Logic**: Race conditions, off-by-one, null pointer risks?\n3. **Style**: Consistent with project conventions? Readable?\n4. **Tests**: Changes covered by tests? Tests meaningful?\n5. **Naming**: Do names clearly convey intent?\n6. **Spec coverage**: Each Requirement addressed in the diff?\n7. **Diff minimality**: Every hunk traces to a Requirement. Hunks that only reformat, re-wrap, re-quote, or reorder untouched code are WARN; list them and revert before ship.\n\n### Output Format\n\n```\n## Code Review: \u003Cfile or area>\n- [BLOCKER] \u003Cdescription> (line X)\n- [WARN] \u003Cdescription> (line Y)\n- [NIT] \u003Cdescription> (line Z)\n\n## Summary\n- Blockers: N\n- Warnings: N\n- Verdict: APPROVE \u002F REQUEST_CHANGES\n```\n\n---\n\n## Mode: audit:security (Security)\n\n### Constraints\n- False positives are better than false negatives for security\n- Always check `.env` files are in `.gitignore`\n\n### Security Checklist (OWASP Top 10)\n\n1. Injection (SQL, XSS, command)\n2. Broken authentication\n3. Sensitive data exposure\n4. Access control failures\n5. Security misconfiguration\n\n### Performance Checklist\n\n1. N+1 queries\n2. Unbounded data loading\n3. Missing indexes\n4. Memory leaks (event listeners, growing caches)\n5. Blocking main thread\n\n### Output Format\n\n```\n## Security Audit\n- [CRITICAL] SQL injection risk in \u003Cfile>:\u003Cline>\n- [HIGH] Hardcoded secret in \u003Cfile>:\u003Cline>\n- [MEDIUM] Missing rate limit on \u003Cendpoint>\n\n## Performance Audit\n- [HIGH] N+1 query in \u003Cfile>:\u003Cline>\n- [MEDIUM] Unbounded array growth in \u003Cfile>:\u003Cline>\n\n## Summary\n- Security: PASS \u002F FAIL (N critical, N high)\n- Performance: PASS \u002F WARN (N issues)\n```\n\n---\n\n## Mode: audit:test (Test Runner)\n\n1. Run the full test suite\n2. Verify each Acceptance Criterion is demonstrably met\n3. Report coverage delta\n4. Flag any flaky tests\n\n---\n\n### Step 3.5: Semantic Deduplication\n\nAfter all 3 modes complete, merge their findings and deduplicate:\n\n**Collection**: Gather all findings from code, security, and test modes into a single pool.\n\n**Root-Cause Grouping**: For each finding, identify the root cause. Findings sharing the same root cause (same file, same function, same underlying pattern) form a group.\n\n**Classification** (per group):\n\n| Classification | Meaning | Action |\n|---------------|---------|--------|\n| `NEW` | First finding for this root cause | Include in report |\n| `DUP_BETTER` | Duplicate with better evidence or higher severity | Replace original with this |\n| `DUP_SKIP` | Duplicate with weaker or equal evidence | Drop; reference the `NEW` finding |\n\n**Severity Reassessment**: The surviving finding in each group takes the highest severity across all modes. For example, if code review says `[WARN]` but security says `[CRITICAL]` for the same root cause, the deduped finding is `[CRITICAL]`.\n\n**Output**: Only deduplicated findings proceed to Step 4 synthesis. The report should note: \"N findings deduplicated from M total (K groups collapsed).\"\n\n---\n\n### Step 4: Synthesize\n\nCombine deduplicated findings into a single report:\n\n```\n## Audit Report\n- Spec: SPEC-{timestamp} ({goal_slug})\n- Branch: {current branch}\n\n### Change Scope\n- Scopes detected: [API, Frontend, Backend, Database, Infra, Docs, Tests]\n- Scope-specific checks: [list what ran]\n\n### Code Quality: [PASS\u002FWARN\u002FFAIL]\n### Security: [PASS\u002FWARN\u002FFAIL]\n### Performance: [PASS\u002FWARN\u002FFAIL]\n### Tests: [X\u002FY passing, Z% coverage]\n\n### Deduplication\n- Total findings: M\n- Deduplicated: N (K groups collapsed)\n\n### Spec Coverage\n- R1: ✅\u002F❌ addressed in diff\n- R2: ✅\u002F❌ addressed in diff\n- AC1: ✅\u002F❌ verified by test\n- AC2: ✅\u002F❌ verified by test\n\n### Action Items\n1. [blocker or warning]\n```\n\n### Step 5: Act\n\n- **All PASS + all AC verified**: **\"Audit passed. Run `\u002Fship` to create a PR.\"**\n- **WARN**: Show warnings, ask if user wants to fix before shipping\n- **FAIL or AC missing**: List each blocker with a one-line fix hint. **\"Fix with `\u002Fgo`, then re-run `\u002Faudit`.\"**\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"It's a small change, skip security\" | Small changes introduce big vulnerabilities | Always run the security checklist |\n| \"Tests are passing, that's enough\" | Tests don't catch security or performance issues | Run all 3 modes |\n| \"I'll fix the warnings later\" | Later never comes | Fix blockers now, warnings before merge |\n| \"Dedup is overkill for small audits\" | Small audits can still have cross-mode overlap | Always dedup — the cost is trivial |\n| \"Strict mode is overkill\" | Without isolation, the builder can influence reviewers via shared context | Use `--strict` for security-sensitive or compliance-driven projects |\n| \"The agents are independent enough\" | Shared context creates anchoring bias — a clean code review inflates security scores | Strict mode ensures blind scoring until synthesis |\n\n## Evidence Required\n\n- [ ] All 3 modes (code, security, test) completed\n- [ ] Each Requirement has a coverage verdict\n- [ ] Each AC has a test\u002Fverification verdict\n- [ ] No BLOCKER items remain on PASS\n- [ ] Deduplication applied: total vs. deduplicated count reported\n\n## Red Flags\n\n- Skipping security review for \"small changes\"\n- Approving code with failing tests\n- Ignoring performance warnings in hot paths\n- Marking audit PASS when any AC is unverified\n- Reporting raw findings without deduplication\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Faudit",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit",{"tool":53,"command":54},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit",{"tool":56,"command":57},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Faudit\u002FSKILL.md",true,[],[62,72,80,88,96,104],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":71},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":71},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":71},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":71},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":71},"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",[],[]]