[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEPC1CAVE2FY7G9HQT5ATP":3,"skill-same:01M6MEPC1CAVE2FY7G9HQT5ATP":142},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":89},"01M6MEPC1CAVE2FY7G9HQT5ATP","doc",null,"Write source-checked docs, READMEs, change descriptions and handoffs. Use when: documenting a change, leaving or resuming a handoff, or drafting a questionnaire for someone else.","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\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"context","drafting","when","source","for","canonical","session-handoff","pragmatic","references","evidence","initialize","directory","write","knowledge","wiki","product","code","create","documentation","change","handoff","2026-11-10 10:12:30",false,"---\nname: doc\ndescription: \"Write source-checked docs, READMEs, change descriptions and handoffs. Use when: documenting a change, leaving or resuming a handoff, or drafting a questionnaire for someone else.\"\npractices:\n- wiki-knowledge-surface\n- code-complete\n- pragmatic-programmer\nhexagonal_role: supporting\nconsumes:\n- repo-context\nproduces:\n- documentation\n- session-handoff\ncontext_rel: []\nskill_api_version: 1\nuser-invocable: true\nmetadata:\n  capabilities: [doc, initialize_missing_docs, write_session_handoff]\n  effects: [write_documentation, write_requested_handoff, create_requested_evidence_directory]\n  canonical_status: canonical\n  disposition: keep_specialist\n  tier: product\n  dependencies: []\noutput_contract: requested documentation or handoff with source references, check results and explicit gaps\n---\n# Doc\n\nWrite or update the documentation the caller needs, grounded in the current\nrepository and its accepted intent. A small explanation needs no interview,\ncoverage ledger or separate report. Select only the mode relevant to the task.\n\n## Modes\n\n| Need | Scope and reference |\n|---|---|\n| Explain an API, command, code-map or architecture | Inspect its consumers, source and tests, and write to the existing document owner. A coverage percentage needs a numerator and denominator from one enumerated, checked entity set ([validation techniques](references\u002Fvalidation-rules.md)). How the code works is [Research](..\u002Fresearch\u002FSKILL.md)'s repository tracing; Doc writes it down when a document is requested. |\n| Create or improve a README | Lead with the user's problem and a working first-use path; preserve useful depth. See [README craft](references\u002Freadme-craft.md). |\n| Check an advertised install, upgrade or first-success path | Follow the selected package and current instructions in an authorized disposable environment. See [developer journey](references\u002Fdeveloper-journey.md). |\n| Audit or scaffold OSS documentation | Compare existing docs with the requested pack. Create missing files; revise existing files only within the authorized request. See [OSS pack](references\u002Foss-pack.md). |\n| Initialize missing entry documents | Create only explicitly requested missing files; report existing paths as skipped. See [setup examples](references\u002Fbootstrap\u002Fexamples.md). |\n| Bring docs current after a change, describe a change for reviewers, or write release notes for a range | Start from the exact diff and its public surface; fix what it proves wrong and ask about judgment calls. See [change-driven docs](references\u002Fchange-driven-docs.md). |\n| Preserve a session for another context, or resume from one | Read [the handoff reference](references\u002Fhandoff.md) before writing or resuming one. A handoff records only facts you observed: anything else is `unknown` or the caller's unverified claim, and a note saying HOLD or paused is not state. |\n| Get facts or decisions only another person holds | Write one [questionnaire](references\u002Fquestionnaire.md) they can answer alone; the caller sends it. |\n\nThese are optional task shapes, not successive phases. Detailed references\nsupply techniques and formats; they do not add interviews, approval checkpoints,\nreports or files beyond the accepted request. Existing authorization to revise\nspecified documents is sufficient.\n\n`\u003Cskill-dir>` is the directory that contains this SKILL.md. Claude Code shows it\nas \"Base directory for this skill\"; Codex lists this skill's SKILL.md path; in\nan AgentOps source checkout it is `skills\u002Fdoc`. Replace `\u003Cskill-dir>` with that\nabsolute path before running a command. The working directory stays the user's\nrepository. If the host did not show where this skill is installed, use the\ndirectory of the SKILL.md you read. If you cannot determine it, do not guess a\npath or run a same-named script from the current repository; say the bundled\nscript is unavailable and compare the repository's documentation files with the\nrequested pack by hand.\n\n## Grounded writing\n\n1. Identify the audience, question and existing document owner. Reuse accepted\n   intent; ask only for missing content that materially changes the document.\n   Name the reader's need: learning from scratch, doing one task, looking up a\n   fact, or understanding why. A reference list does not show how to do the\n   task it exists for. For a reader who learns from it, explain each idea before\n   a section relies on it ([ordering](references\u002Fprose-and-report-workmanship.md#order-ideas-for-a-learner)).\n2. Read the relevant declarations and verify them against code, configuration,\n   command help or executable behavior. Use the caller's domain terminology.\n   Take steps in another vendor's interface (menus, settings, where a value\n   appears) from its current docs or the caller, or mark them unverified; never guess.\n   For a larger surface, retain enough source references to disclose what was\n   inspected and what remains unknown; do not imply whole-repository coverage.\n3. Make the smallest useful edit. Explain non-obvious rules, ordering and tradeoffs\n   when they help the reader; a reference page need not manufacture a lesson.\n   Preserve operator policy and history outside the authorized scope. Edit an\n   existing document in its own shape, from a fresh read if a person may have\n   changed it (their edits win): extend the passage that already says it, under\n   any heading, rather than add a duplicate section, and do not reorder or\n   restyle it into a template unless asked for a rewrite. When rewriting\n   existing prose, keep every fact, number, name, citation and identifier,\n   and keep each claim's certainty: \"may\" does not become \"does\".\n   When condensing (a summary, handoff or release notes), keep every failure,\n   caveat, open question and request, and sound no more finished, positive or\n   certain than the source; say where it is vague or contradicts itself.\n   Leave code blocks, quotes and link targets untouched unless they are the\n   thing to fix.\n4. Check links, cited commits and paths, leftover drafting scaffold, examples\n   and the repository's documentation build or validator ([techniques](references\u002Fvalidation-rules.md)).\n   Remove empty claims and redundant prose; [prose guidance](references\u002Fprose-and-report-workmanship.md)\n   can help when the requested output is substantial.\n   A link handed to a reader (in a document, report, handoff or change\n   description) must open the exact item it names for that reader. Build\n   repository URLs from Git rather than by hand, and point them at a ref that\n   already contains the pushed content: a main-branch link to a file that exists\n   only on a feature branch is dead. Link the item itself (the pull request, the\n   file and line), not its parent page. When no direct link can be verified, say\n   where to find the item instead of giving a guessed link.\n5. Return changed paths and check results, plus unresolved factual gaps. Write a\n   separate report only when the caller requests one or an existing consumer\n   requires it.\n\n## Missing-document setup\n\nCreate only the requested missing documents, such as `PRODUCT.md`, `GOALS.md`\nor `AGENTS.md`; a collision is skipped, not overwritten by setup. Verify the\ncreated paths and report created, skipped and failed writes. Setup does not\ninstall tools, run `ao session bootstrap`, initialize Git or trackers, start a\nruntime, add hooks, or infer a repository workflow. AgentOps verdict storage is\ncreated only on explicit request; see [AgentOps internals](references\u002Fagentops-internal.md).\n\n## Reference menu\n\nLoad these only for the document being written. They supply examples and\ntechniques under the kernel's accepted scope, not additional workflow gates.\n\n- Writing and checks: [prose workmanship](references\u002Fprose-and-report-workmanship.md) (cleanup, learner order, diagrams, one live statement), [validation techniques](references\u002Fvalidation-rules.md).\n- After a change: [change-driven docs](references\u002Fchange-driven-docs.md) for doc drift, reader-need coverage and change descriptions.\n- Explicit context configuration: [context routing](references\u002Fbootstrap\u002Fcontext-routing.md).\n- AgentOps itself (vocabulary, evidence routing, handoff commands): [AgentOps internals](references\u002Fagentops-internal.md).\n","# Doc\n\nWrite or update the documentation the caller needs, grounded in the current\nrepository and its accepted intent. A small explanation needs no interview,\ncoverage ledger or separate report. Select only the mode relevant to the task.\n\n## Modes\n\n| Need | Scope and reference |\n|---|---|\n| Explain an API, command, code-map or architecture | Inspect its consumers, source and tests, and write to the existing document owner. A coverage percentage needs a numerator and denominator from one enumerated, checked entity set ([validation techniques](references\u002Fvalidation-rules.md)). How the code works is [Research](..\u002Fresearch\u002FSKILL.md)'s repository tracing; Doc writes it down when a document is requested. |\n| Create or improve a README | Lead with the user's problem and a working first-use path; preserve useful depth. See [README craft](references\u002Freadme-craft.md). |\n| Check an advertised install, upgrade or first-success path | Follow the selected package and current instructions in an authorized disposable environment. See [developer journey](references\u002Fdeveloper-journey.md). |\n| Audit or scaffold OSS documentation | Compare existing docs with the requested pack. Create missing files; revise existing files only within the authorized request. See [OSS pack](references\u002Foss-pack.md). |\n| Initialize missing entry documents | Create only explicitly requested missing files; report existing paths as skipped. See [setup examples](references\u002Fbootstrap\u002Fexamples.md). |\n| Bring docs current after a change, describe a change for reviewers, or write release notes for a range | Start from the exact diff and its public surface; fix what it proves wrong and ask about judgment calls. See [change-driven docs](references\u002Fchange-driven-docs.md). |\n| Preserve a session for another context, or resume from one | Read [the handoff reference](references\u002Fhandoff.md) before writing or resuming one. A handoff records only facts you observed: anything else is `unknown` or the caller's unverified claim, and a note saying HOLD or paused is not state. |\n| Get facts or decisions only another person holds | Write one [questionnaire](references\u002Fquestionnaire.md) they can answer alone; the caller sends it. |\n\nThese are optional task shapes, not successive phases. Detailed references\nsupply techniques and formats; they do not add interviews, approval checkpoints,\nreports or files beyond the accepted request. Existing authorization to revise\nspecified documents is sufficient.\n\n`\u003Cskill-dir>` is the directory that contains this SKILL.md. Claude Code shows it\nas \"Base directory for this skill\"; Codex lists this skill's SKILL.md path; in\nan AgentOps source checkout it is `skills\u002Fdoc`. Replace `\u003Cskill-dir>` with that\nabsolute path before running a command. The working directory stays the user's\nrepository. If the host did not show where this skill is installed, use the\ndirectory of the SKILL.md you read. If you cannot determine it, do not guess a\npath or run a same-named script from the current repository; say the bundled\nscript is unavailable and compare the repository's documentation files with the\nrequested pack by hand.\n\n## Grounded writing\n\n1. Identify the audience, question and existing document owner. Reuse accepted\n   intent; ask only for missing content that materially changes the document.\n   Name the reader's need: learning from scratch, doing one task, looking up a\n   fact, or understanding why. A reference list does not show how to do the\n   task it exists for. For a reader who learns from it, explain each idea before\n   a section relies on it ([ordering](references\u002Fprose-and-report-workmanship.md#order-ideas-for-a-learner)).\n2. Read the relevant declarations and verify them against code, configuration,\n   command help or executable behavior. Use the caller's domain terminology.\n   Take steps in another vendor's interface (menus, settings, where a value\n   appears) from its current docs or the caller, or mark them unverified; never guess.\n   For a larger surface, retain enough source references to disclose what was\n   inspected and what remains unknown; do not imply whole-repository coverage.\n3. Make the smallest useful edit. Explain non-obvious rules, ordering and tradeoffs\n   when they help the reader; a reference page need not manufacture a lesson.\n   Preserve operator policy and history outside the authorized scope. Edit an\n   existing document in its own shape, from a fresh read if a person may have\n   changed it (their edits win): extend the passage that already says it, under\n   any heading, rather than add a duplicate section, and do not reorder or\n   restyle it into a template unless asked for a rewrite. When rewriting\n   existing prose, keep every fact, number, name, citation and identifier,\n   and keep each claim's certainty: \"may\" does not become \"does\".\n   When condensing (a summary, handoff or release notes), keep every failure,\n   caveat, open question and request, and sound no more finished, positive or\n   certain than the source; say where it is vague or contradicts itself.\n   Leave code blocks, quotes and link targets untouched unless they are the\n   thing to fix.\n4. Check links, cited commits and paths, leftover drafting scaffold, examples\n   and the repository's documentation build or validator ([techniques](references\u002Fvalidation-rules.md)).\n   Remove empty claims and redundant prose; [prose guidance](references\u002Fprose-and-report-workmanship.md)\n   can help when the requested output is substantial.\n   A link handed to a reader (in a document, report, handoff or change\n   description) must open the exact item it names for that reader. Build\n   repository URLs from Git rather than by hand, and point them at a ref that\n   already contains the pushed content: a main-branch link to a file that exists\n   only on a feature branch is dead. Link the item itself (the pull request, the\n   file and line), not its parent page. When no direct link can be verified, say\n   where to find the item instead of giving a guessed link.\n5. Return changed paths and check results, plus unresolved factual gaps. Write a\n   separate report only when the caller requests one or an existing consumer\n   requires it.\n\n## Missing-document setup\n\nCreate only the requested missing documents, such as `PRODUCT.md`, `GOALS.md`\nor `AGENTS.md`; a collision is skipped, not overwritten by setup. Verify the\ncreated paths and report created, skipped and failed writes. Setup does not\ninstall tools, run `ao session bootstrap`, initialize Git or trackers, start a\nruntime, add hooks, or infer a repository workflow. AgentOps verdict storage is\ncreated only on explicit request; see [AgentOps internals](references\u002Fagentops-internal.md).\n\n## Reference menu\n\nLoad these only for the document being written. They supply examples and\ntechniques under the kernel's accepted scope, not additional workflow gates.\n\n- Writing and checks: [prose workmanship](references\u002Fprose-and-report-workmanship.md) (cleanup, learner order, diagrams, one live statement), [validation techniques](references\u002Fvalidation-rules.md).\n- After a change: [change-driven docs](references\u002Fchange-driven-docs.md) for doc drift, reader-need coverage and change descriptions.\n- Explicit context configuration: [context routing](references\u002Fbootstrap\u002Fcontext-routing.md).\n- AgentOps itself (vocabulary, evidence routing, handoff commands): [AgentOps internals](references\u002Fagentops-internal.md).\n",{"name":5,"consumes":45,"metadata":47,"produces":57,"practices":58,"context_rel":62,"description":7,"hexagonal_role":63,"user-invocable":64,"output_contract":65,"skill_api_version":66},[46],"repo-context",{"tier":34,"effects":48,"disposition":52,"capabilities":53,"dependencies":56,"canonical_status":24},[49,50,51],"write_documentation","write_requested_handoff","create_requested_evidence_directory","keep_specialist",[5,54,55],"initialize_missing_docs","write_session_handoff",[],[37,25],[59,60,61],"wiki-knowledge-surface","code-complete","pragmatic-programmer",[],"supporting",true,"requested documentation or handoff with source references, check results and explicit gaps",1,"main","347aedf8480cd92b21f761e97b7343a45898f5fa","plugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc",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":78,"prompt":88,"zipAvailable":64},[79,82,85],{"tool":80,"command":81},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doc",{"tool":83,"command":84},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doc",{"tool":86,"command":87},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill doc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002FSKILL.md",[90,96,100,104,108,112,116,120,124,128,132,136],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fagentops-internal.md","REFERENCE","参考文档",2035,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fagentops-internal.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fbootstrap\u002Fcontext-routing.md",9256,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fbootstrap\u002Fcontext-routing.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fbootstrap\u002Fexamples.md",1255,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fbootstrap\u002Fexamples.md",{"path":105,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fchange-driven-docs.md",6698,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fchange-driven-docs.md",{"path":109,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fdeveloper-journey.md",5152,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fdeveloper-journey.md",{"path":113,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fhandoff.md",4757,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fhandoff.md",{"path":117,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Foss-pack.md",2218,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Foss-pack.md",{"path":121,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fprose-and-report-workmanship.md",3668,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fprose-and-report-workmanship.md",{"path":125,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fquestionnaire.md",1707,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fquestionnaire.md",{"path":129,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Freadme-craft.md",3324,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Freadme-craft.md",{"path":133,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fvalidation-rules.md",7174,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Freferences\u002Fvalidation-rules.md",{"path":137,"resourceType":138,"resourceTypeDesc":139,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Faudit-oss-docs.sh","SCRIPT","脚本",11252,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fdoc\u002Fscripts\u002Faudit-oss-docs.sh",[143,153,161,169,177,185],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":152},"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":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":152},"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":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":152},"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":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":152},"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":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":152},"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":152},"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",[],[]]