[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVR1Y94GFRGEMKSD65YX1Y":3,"skill-same:01M6JVR1Y94GFRGEMKSD65YX1Y":80},{"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":28,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6JVR1Y94GFRGEMKSD65YX1Y","requesting-code-review",null,"Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.","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\u002FGanyuanRan\u002FAegis\u002Fskills\u002Frequesting-code-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"code review","review","code","requesting code review","architecture","verification","risk","baseline","work","use","evidence","implementation","compatibility","uncertainty","high","when","2026-11-10 10:12:30",false,"---\nname: requesting-code-review\ndescription: \"Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.\"\n---\n\n# Requesting Code Review\n\nDispatch a reviewer subagent using the canonical `code-reviewer.md` template to\ncatch issues before they cascade. The reviewer gets precisely crafted context\nfor evaluation — never your session's history. This keeps the reviewer focused\non the work product, not your thought process, and preserves your own context\nfor continued work.\n\nThis skill is the canonical review-request workflow for method-pack implementation work. Use it to request review only after you have enough evidence, enough context, and a clear authority boundary for what the reviewer is being asked to assess.\n\n**Core principle:** Review early, review often.\n\n**Findings First:** Reviews lead with concrete findings before summary. Use\nbugs first, risk first, tests first. Strengths and general assessment are still\nuseful, but they must not bury correctness, evidence, architecture, or\nretirement problems.\n\nReview readiness is not merge approval. A review can reduce uncertainty and\nrecommend readiness, but it does not replace `verification-before-completion`\nand does not grant completion authority.\n\n## When to Request Review\n\n**Mandatory:**\n- After each task in subagent-driven development\n- After completing major feature\n- Before merge to main\n\n**Optional but valuable:**\n- When stuck (fresh perspective)\n- Before refactoring (baseline check)\n- After fixing complex bug\n\n## Required Outputs\n\nBefore you leave this workflow, you must be able to state:\n\n1. **What exact scope is being reviewed**\n2. **What plan, requirement, or contract defines success**\n3. **What Product \u002F Requirement Baseline defines accepted behavior and non-goals**\n4. **What Architecture \u002F Runtime Boundary Baseline defines the expected architecture state**\n5. **What fresh evidence already exists**\n6. **What compatibility boundary must still hold**\n7. **What old owner \u002F fallback \u002F patch stays, shrinks, or retires**\n8. **What the reviewer must specifically validate**\n9. **Whether the reviewer is providing advisory review only, or also any higher-level merge recommendation**\n10. **Aegis Visibility**: why findings-first ordering, evidence sufficiency,\n    baseline alignment, compatibility, or retirement risk matters for this\n    review request\n11. **Semantic context scope**: which relevant canonical terms, deprecated\n    aliases, or public naming boundaries the review must preserve\n\nReview in this method pack is advisory and evidence-oriented. It is not authoritative completion by itself.\n\nCompare requirements and result in both directions: omissions or weakening,\nand unsupported additions or strengthening. Preserve relevant relationships,\nbehavior, ownership and qualifiers within the authorized transformation. Pair\nan evidenced defect with a relevant valid case; do not add acceptance criteria,\nreject authorized summaries or corrections, or require exhaustive equivalence.\n\n## How to Request\n\n**1. Gather minimum review inputs:**\n\n- What was implemented\n- What requirement \u002F plan \u002F spec \u002F ADR it should match\n- What baseline \u002F current authority docs the diff must align with, including\n  requirements\u002Fproduct alignment and architecture\u002Fcurrent-authority alignment\n- What evidence already exists (tests, commands, logs, screenshots, diff summary)\n- What compatibility boundary or risk deserves reviewer attention\n- Whether there is any old path, fallback, duplicate owner, or temporary patch that should retire\n- Whether the diff contains durable architecture decisions that need ADR\n  Auto Backfill or baseline sync findings\n- Whether `recording-architecture-decisions` was used, or should be used, when\n  an ADR action or baseline sync closure is in scope\n- Relevant active `CONTEXT.md` language when public\u002Fdomain naming is in scope;\n  passive reading does not load active modeling\n\nIf you cannot answer these, stop and gather them before dispatching review.\n\n**2. Define the Git review scope:**\n```bash\n# Before the coordinator's task commit\nREVIEW_SCOPE=working-tree\nBASE_SHA=$(git rev-parse HEAD)\n\n# Or for already committed work\nREVIEW_SCOPE=committed-range\nBASE_SHA=\u003Cknown-start>\nHEAD_SHA=$(git rev-parse HEAD)\n```\n\nFor working-tree review, identify task-owned untracked paths explicitly. Do not\nstage merely to make them visible to a reviewer.\n\n**3. Dispatch reviewer subagent:**\n\nUse the Task tool with a general-purpose reviewer subagent. Fill the canonical\ntemplate at `requesting-code-review\u002Fcode-reviewer.md`; do not rely on a\nseparate named agent prompt.\n\n**Placeholders:**\n- `{WHAT_WAS_IMPLEMENTED}` - What you just built\n- `{PLAN_OR_REQUIREMENTS}` - What it should do\n- `{EVIDENCE}` - Fresh tests, commands, logs, or verification already available\n- `{COMPATIBILITY_BOUNDARY}` - What existing behavior or interfaces must not break\n- `{RETIREMENT_NOTES}` - Old owner \u002F fallback \u002F patch \u002F duplicate branch and expected disposition\n- `{REVIEW_SCOPE}` - `working-tree` or `committed-range`\n- `{BASE_SHA}` - Starting commit\n- `{HEAD_SHA}` - Ending commit, or `WORKTREE`\n- `{DESCRIPTION}` - Brief summary\n\n**4. Act on feedback:**\n- Fix Critical issues immediately\n- Fix Important issues before proceeding\n- Note Minor issues for later\n- Push back if reviewer is wrong (with reasoning)\n- If feedback reveals evidence gaps, run the missing verification instead of arguing from confidence\n- If feedback reveals Design Defect \u002F Implementation Drift, stale logic, or a\n  legacy alias such as architecture drift, decide explicitly whether to repair\n  now, correct the baseline, or record retirement conditions\n\n## Example\n\n```\n[Just completed Task 2: Add verification function]\n\nYou: Let me request code review before proceeding.\n\nBASE_SHA=$(git log --oneline | grep \"Task 1\" | head -1 | awk '{print $1}')\nHEAD_SHA=$(git rev-parse HEAD)\n\n[Dispatch reviewer subagent using requesting-code-review\u002Fcode-reviewer.md]\n  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index\n  PLAN_OR_REQUIREMENTS: Task 2 from docs\u002Faegis\u002Fplans\u002Fdeployment-plan.md\n  EVIDENCE: pytest tests\u002Findex\u002Ftest_verify.py -v -> 12 passed\n  COMPATIBILITY_BOUNDARY: Existing index format and CLI flags must remain stable\n  RETIREMENT_NOTES: Legacy repair fallback still exists in old helper; remove once new path covers all four issue types\n  BASE_SHA: a7981ec\n  HEAD_SHA: 3df7661\n  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types\n\n[Subagent returns]:\n  Strengths: Clean architecture, real tests\n  Issues:\n    Important: Missing progress indicators\n    Minor: Magic number (100) for reporting interval\n  Assessment: Ready to proceed\n\nYou: [Fix progress indicators]\n[Continue to Task 3]\n```\n\n## Integration with Workflows\n\n**Subagent-Driven Development:**\n- Review after EACH task\n- Catch issues before they compound\n- Fix before moving to next task\n\n**Executing Plans:**\n- Review after each batch (3 tasks)\n- Get feedback, apply, continue\n\n**Ad-Hoc Development:**\n- Review before merge\n- Review when stuck\n\n## What the Reviewer Must Check\n\nThe review request must prompt the reviewer to inspect at least:\n\n- Findings First: bugs first, risk first, tests first\n- evidence sufficiency\n- baseline \u002F current authority alignment\n- requirements\u002Fproduct alignment against accepted problem, success evidence, and\n  non-goals\n- architecture\u002Fcurrent-authority alignment against owner, contract,\n  source-of-truth, compatibility, and retirement boundaries\n- Design Defect \u002F Implementation Drift classification with\n  `scope: requirements | architecture | both`\n- legacy phrase mapping: baseline defect, architecture defect, and architecture\n  drift must map back to Design Defect \u002F Implementation Drift rather than\n  becoming parallel result vocabularies\n- duplicate owner risk\n- compatibility boundary\n- missing ADR Auto Backfill or baseline sync findings for durable architecture\n  decisions\n- missing `recording-architecture-decisions` handoff when ADR action or\n  baseline sync closure is in scope\n- unverified claims or missing proof\n- old logic that should retire, stay temporarily, or converge\n- public-name drift, deprecated-term re-entry, or a semantic change recorded in\n  code\u002Fdocs without composing `establishing-project-context`\n\nIf the review only asks “is this code good?”, it is underspecified.\n\n## Red Flags\n\n**Never:**\n- Skip review because \"it's simple\"\n- Ignore Critical issues\n- Proceed with unfixed Important issues\n- Argue with valid technical feedback\n- Treat reviewer approval as equivalent to authoritative completion\n- Ask for review without sharing what evidence already exists\n- Add new logic without telling the reviewer what happens to the old path\n\n**If reviewer wrong:**\n- Push back with technical reasoning\n- Show code\u002Ftests that prove it works\n- Request clarification\n\n## Review Boundaries\n\n- Review can recommend merge readiness, residual risk, and follow-up work\n- Review cannot grant authoritative completion by itself\n- Review should reduce uncertainty, not hide it\n\nSee template at: requesting-code-review\u002Fcode-reviewer.md\n","# Requesting Code Review\n\nDispatch a reviewer subagent using the canonical `code-reviewer.md` template to\ncatch issues before they cascade. The reviewer gets precisely crafted context\nfor evaluation — never your session's history. This keeps the reviewer focused\non the work product, not your thought process, and preserves your own context\nfor continued work.\n\nThis skill is the canonical review-request workflow for method-pack implementation work. Use it to request review only after you have enough evidence, enough context, and a clear authority boundary for what the reviewer is being asked to assess.\n\n**Core principle:** Review early, review often.\n\n**Findings First:** Reviews lead with concrete findings before summary. Use\nbugs first, risk first, tests first. Strengths and general assessment are still\nuseful, but they must not bury correctness, evidence, architecture, or\nretirement problems.\n\nReview readiness is not merge approval. A review can reduce uncertainty and\nrecommend readiness, but it does not replace `verification-before-completion`\nand does not grant completion authority.\n\n## When to Request Review\n\n**Mandatory:**\n- After each task in subagent-driven development\n- After completing major feature\n- Before merge to main\n\n**Optional but valuable:**\n- When stuck (fresh perspective)\n- Before refactoring (baseline check)\n- After fixing complex bug\n\n## Required Outputs\n\nBefore you leave this workflow, you must be able to state:\n\n1. **What exact scope is being reviewed**\n2. **What plan, requirement, or contract defines success**\n3. **What Product \u002F Requirement Baseline defines accepted behavior and non-goals**\n4. **What Architecture \u002F Runtime Boundary Baseline defines the expected architecture state**\n5. **What fresh evidence already exists**\n6. **What compatibility boundary must still hold**\n7. **What old owner \u002F fallback \u002F patch stays, shrinks, or retires**\n8. **What the reviewer must specifically validate**\n9. **Whether the reviewer is providing advisory review only, or also any higher-level merge recommendation**\n10. **Aegis Visibility**: why findings-first ordering, evidence sufficiency,\n    baseline alignment, compatibility, or retirement risk matters for this\n    review request\n11. **Semantic context scope**: which relevant canonical terms, deprecated\n    aliases, or public naming boundaries the review must preserve\n\nReview in this method pack is advisory and evidence-oriented. It is not authoritative completion by itself.\n\nCompare requirements and result in both directions: omissions or weakening,\nand unsupported additions or strengthening. Preserve relevant relationships,\nbehavior, ownership and qualifiers within the authorized transformation. Pair\nan evidenced defect with a relevant valid case; do not add acceptance criteria,\nreject authorized summaries or corrections, or require exhaustive equivalence.\n\n## How to Request\n\n**1. Gather minimum review inputs:**\n\n- What was implemented\n- What requirement \u002F plan \u002F spec \u002F ADR it should match\n- What baseline \u002F current authority docs the diff must align with, including\n  requirements\u002Fproduct alignment and architecture\u002Fcurrent-authority alignment\n- What evidence already exists (tests, commands, logs, screenshots, diff summary)\n- What compatibility boundary or risk deserves reviewer attention\n- Whether there is any old path, fallback, duplicate owner, or temporary patch that should retire\n- Whether the diff contains durable architecture decisions that need ADR\n  Auto Backfill or baseline sync findings\n- Whether `recording-architecture-decisions` was used, or should be used, when\n  an ADR action or baseline sync closure is in scope\n- Relevant active `CONTEXT.md` language when public\u002Fdomain naming is in scope;\n  passive reading does not load active modeling\n\nIf you cannot answer these, stop and gather them before dispatching review.\n\n**2. Define the Git review scope:**\n```bash\n# Before the coordinator's task commit\nREVIEW_SCOPE=working-tree\nBASE_SHA=$(git rev-parse HEAD)\n\n# Or for already committed work\nREVIEW_SCOPE=committed-range\nBASE_SHA=\u003Cknown-start>\nHEAD_SHA=$(git rev-parse HEAD)\n```\n\nFor working-tree review, identify task-owned untracked paths explicitly. Do not\nstage merely to make them visible to a reviewer.\n\n**3. Dispatch reviewer subagent:**\n\nUse the Task tool with a general-purpose reviewer subagent. Fill the canonical\ntemplate at `requesting-code-review\u002Fcode-reviewer.md`; do not rely on a\nseparate named agent prompt.\n\n**Placeholders:**\n- `{WHAT_WAS_IMPLEMENTED}` - What you just built\n- `{PLAN_OR_REQUIREMENTS}` - What it should do\n- `{EVIDENCE}` - Fresh tests, commands, logs, or verification already available\n- `{COMPATIBILITY_BOUNDARY}` - What existing behavior or interfaces must not break\n- `{RETIREMENT_NOTES}` - Old owner \u002F fallback \u002F patch \u002F duplicate branch and expected disposition\n- `{REVIEW_SCOPE}` - `working-tree` or `committed-range`\n- `{BASE_SHA}` - Starting commit\n- `{HEAD_SHA}` - Ending commit, or `WORKTREE`\n- `{DESCRIPTION}` - Brief summary\n\n**4. Act on feedback:**\n- Fix Critical issues immediately\n- Fix Important issues before proceeding\n- Note Minor issues for later\n- Push back if reviewer is wrong (with reasoning)\n- If feedback reveals evidence gaps, run the missing verification instead of arguing from confidence\n- If feedback reveals Design Defect \u002F Implementation Drift, stale logic, or a\n  legacy alias such as architecture drift, decide explicitly whether to repair\n  now, correct the baseline, or record retirement conditions\n\n## Example\n\n```\n[Just completed Task 2: Add verification function]\n\nYou: Let me request code review before proceeding.\n\nBASE_SHA=$(git log --oneline | grep \"Task 1\" | head -1 | awk '{print $1}')\nHEAD_SHA=$(git rev-parse HEAD)\n\n[Dispatch reviewer subagent using requesting-code-review\u002Fcode-reviewer.md]\n  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index\n  PLAN_OR_REQUIREMENTS: Task 2 from docs\u002Faegis\u002Fplans\u002Fdeployment-plan.md\n  EVIDENCE: pytest tests\u002Findex\u002Ftest_verify.py -v -> 12 passed\n  COMPATIBILITY_BOUNDARY: Existing index format and CLI flags must remain stable\n  RETIREMENT_NOTES: Legacy repair fallback still exists in old helper; remove once new path covers all four issue types\n  BASE_SHA: a7981ec\n  HEAD_SHA: 3df7661\n  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types\n\n[Subagent returns]:\n  Strengths: Clean architecture, real tests\n  Issues:\n    Important: Missing progress indicators\n    Minor: Magic number (100) for reporting interval\n  Assessment: Ready to proceed\n\nYou: [Fix progress indicators]\n[Continue to Task 3]\n```\n\n## Integration with Workflows\n\n**Subagent-Driven Development:**\n- Review after EACH task\n- Catch issues before they compound\n- Fix before moving to next task\n\n**Executing Plans:**\n- Review after each batch (3 tasks)\n- Get feedback, apply, continue\n\n**Ad-Hoc Development:**\n- Review before merge\n- Review when stuck\n\n## What the Reviewer Must Check\n\nThe review request must prompt the reviewer to inspect at least:\n\n- Findings First: bugs first, risk first, tests first\n- evidence sufficiency\n- baseline \u002F current authority alignment\n- requirements\u002Fproduct alignment against accepted problem, success evidence, and\n  non-goals\n- architecture\u002Fcurrent-authority alignment against owner, contract,\n  source-of-truth, compatibility, and retirement boundaries\n- Design Defect \u002F Implementation Drift classification with\n  `scope: requirements | architecture | both`\n- legacy phrase mapping: baseline defect, architecture defect, and architecture\n  drift must map back to Design Defect \u002F Implementation Drift rather than\n  becoming parallel result vocabularies\n- duplicate owner risk\n- compatibility boundary\n- missing ADR Auto Backfill or baseline sync findings for durable architecture\n  decisions\n- missing `recording-architecture-decisions` handoff when ADR action or\n  baseline sync closure is in scope\n- unverified claims or missing proof\n- old logic that should retire, stay temporarily, or converge\n- public-name drift, deprecated-term re-entry, or a semantic change recorded in\n  code\u002Fdocs without composing `establishing-project-context`\n\nIf the review only asks “is this code good?”, it is underspecified.\n\n## Red Flags\n\n**Never:**\n- Skip review because \"it's simple\"\n- Ignore Critical issues\n- Proceed with unfixed Important issues\n- Argue with valid technical feedback\n- Treat reviewer approval as equivalent to authoritative completion\n- Ask for review without sharing what evidence already exists\n- Add new logic without telling the reviewer what happens to the old path\n\n**If reviewer wrong:**\n- Push back with technical reasoning\n- Show code\u002Ftests that prove it works\n- Request clarification\n\n## Review Boundaries\n\n- Review can recommend merge readiness, residual risk, and follow-up work\n- Review cannot grant authoritative completion by itself\n- Review should reduce uncertainty, not hide it\n\nSee template at: requesting-code-review\u002Fcode-reviewer.md\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Frequesting-code-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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill requesting-code-review",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill requesting-code-review",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill requesting-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Frequesting-code-review\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"code-reviewer.md","REFERENCE","参考文档",8518,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Frequesting-code-review\u002Fcode-reviewer.md",[81,91,99,107,115,123],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":90},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":90},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":90},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":90},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":90},"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",[],[]]