[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MK9TPBDTA9BM58XJAC2B31":3,"skill-same:01M6MK9TPBDTA9BM58XJAC2B31":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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":73},"01M6MK9TPBDTA9BM58XJAC2B31","skill-doc-sync",null,"Post-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.","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-doc-sync\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,38,39,40,41,42,43,44],"sync","skill doc sync","doc sync","doc","update docs","when","changes","true","post","docs","project","across","document","update","use","notes","sync docs","markdown","ship","release notes","release","2026-11-10 10:12:30",false,"---\nname: skill-doc-sync\ndescription: \"Post-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.\"\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# Post-Ship Documentation Synchronization\n\nAutomated documentation synchronization for the Deliver phase. After code is committed and a PR is created, this skill reads all `.md` files in the project, cross-references the diff, auto-updates factual content, checks cross-doc consistency, and updates the PR body.\n\n\n## Caps\n\n- **Max 30 doc files scanned** — skip files beyond the cap, warn the user\n- **Never clobber CHANGELOG** — append only, never delete existing entries\n- **Ask user before changing narrative\u002Fphilosophy sections** — risky changes require confirmation\n\n\n## Step 1: Discover Docs\n\nFind all `.md` files in the project root (max depth 2), skipping `node_modules\u002F` and `.git\u002F`.\n\n```bash\n# Discover all markdown files (max depth 2, skip noise directories)\nDOC_FILES=$(find . -maxdepth 2 -name '*.md' \\\n  -not -path '.\u002Fnode_modules\u002F*' \\\n  -not -path '.\u002F.git\u002F*' \\\n  -not -path '.\u002Fvendor\u002F*' \\\n  -not -path '.\u002F.claude\u002F*' \\\n  2>\u002Fdev\u002Fnull | head -30)\n\nDOC_COUNT=$(echo \"$DOC_FILES\" | wc -l | tr -d ' ')\necho \"Found $DOC_COUNT doc files to scan (cap: 30)\"\n\nif [[ \"$DOC_COUNT\" -ge 30 ]]; then\n  echo \"WARNING: Doc file cap reached (30). Some files may be skipped.\"\nfi\n```\n\nRead each discovered doc file so you have their current content in context.\n\n\n## Step 2: Cross-Reference Diff\n\nRun `git diff --stat HEAD~1` (or diff against the base branch if on a feature branch) to identify which files changed and what content may now be stale in each doc.\n\n```bash\n# Get the diff stat to identify changed files\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nif [[ \"$BRANCH\" == \"main\" || \"$BRANCH\" == \"master\" ]]; then\n  DIFF_STAT=$(git diff --stat HEAD~1)\n  DIFF_FULL=$(git diff HEAD~1)\nelse\n  BASE_BRANCH=$(git merge-base HEAD main 2>\u002Fdev\u002Fnull || git merge-base HEAD master 2>\u002Fdev\u002Fnull)\n  DIFF_STAT=$(git diff --stat \"$BASE_BRANCH\"..HEAD)\n  DIFF_FULL=$(git diff \"$BASE_BRANCH\"..HEAD)\nfi\n\necho \"$DIFF_STAT\"\n```\n\nFor each doc file, check whether any paths, function names, counts, or version numbers mentioned in the doc were affected by the diff.\n\n\n## Step 3: Auto-Update Factual Corrections\n\nFix paths, counts, table entries, and version numbers automatically. These are mechanical changes that do not alter meaning.\n\n**Auto-update targets:**\n- File paths that were renamed or moved in the diff\n- Numeric counts (e.g., \"42 tests\" when the number changed)\n- Version strings (e.g., `v9.5.0` when `package.json` bumped)\n- Table entries referencing renamed or removed items\n- Import\u002Frequire paths that changed\n\n**WHY:** Stale factual references erode trust in documentation. A user who sees a wrong path or count will doubt everything else in the doc.\n\n\n## Step 4: Risky Change Detection\n\nFlag narrative, philosophy, or security-related doc sections for user confirmation. Do NOT auto-edit these.\n\n**Risky categories (require user approval):**\n- Sections with headings containing: \"Philosophy\", \"Principles\", \"Vision\", \"Mission\", \"Security\", \"Threat Model\", \"Architecture Decision\"\n- Paragraphs that express opinion, strategy, or rationale (not just facts)\n- Content under `## Why` or `## Rationale` headings\n- Any changes to `SECURITY.md` or `CONTRIBUTING.md` beyond version bumps\n\n**WHY:** Narrative and philosophy sections reflect human judgment. Silently rewriting them risks misrepresenting the project's intent.\n\nWhen risky changes are detected, present them to the user:\n```\nThe following doc sections may need updating but contain narrative\u002Fphilosophy content.\nI will NOT auto-edit these. Please review and confirm each change:\n\n1. README.md ## Philosophy — mentions \"single-binary deployment\" but diff adds Docker support\n2. SECURITY.md ## Threat Model — new auth endpoint not documented\n\nApprove changes? (list numbers to approve, or \"skip all\")\n```\n\n\n## Step 5: CHANGELOG Voice Polish\n\nApply the \"sell test\" to every CHANGELOG entry: **\"Would a user reading this bullet think 'oh nice, I want to try that'?\"**\n\n**Rules:**\n- Lead with the user benefit, not the implementation detail\n- Use active voice (\"Add X\" not \"X was added\")\n- Keep bullets under 120 characters\n- Never delete existing CHANGELOG entries (append only)\n- Group by: Added, Changed, Fixed, Removed (Keep a Changelog format)\n\n**Example transformations:**\n```\nBAD:  \"Refactored spawn_agent to use parameter expansion instead of basename\"\nGOOD: \"Speed up agent spawning by eliminating 750 subshell forks (92% reduction)\"\n\nBAD:  \"Added SUPPORTS_MCP_ELICITATION flag\"\nGOOD: \"Support MCP elicitation for richer interactive prompts (CC v2.1.76+)\"\n```\n\n**WHY:** The CHANGELOG is marketing copy for developers. Every bullet should make someone want to upgrade.\n\n\n## Step 6: Cross-Doc Consistency\n\nCheck that key values are aligned across all documentation files.\n\n**Consistency checks:**\n- Version numbers match across `README.md`, `CLAUDE.md`, `package.json`, `CHANGELOG.md`, and any other files referencing the current version\n- Feature lists in README match what is actually implemented (cross-reference with command\u002Fskill directories)\n- Badge URLs and shield.io references are up to date\n- Links between docs are not broken (relative path references)\n- Command counts and skill counts match actual directory listings\n\n```bash\n# Example: check version consistency\nPKG_VERSION=$(grep '\"version\"' package.json | head -1 | sed 's\u002F.*\"version\": *\"\u002F\u002F' | sed 's\u002F\".*\u002F\u002F')\necho \"package.json version: $PKG_VERSION\"\n\n# Check README mentions this version\nif ! grep -q \"$PKG_VERSION\" README.md 2>\u002Fdev\u002Fnull; then\n  echo \"WARNING: README.md does not mention version $PKG_VERSION\"\nfi\n\n# Check CHANGELOG has an entry for this version\nif ! grep -q \"$PKG_VERSION\" CHANGELOG.md 2>\u002Fdev\u002Fnull; then\n  echo \"WARNING: CHANGELOG.md has no entry for version $PKG_VERSION\"\nfi\n```\n\n\n## Step 7: Discoverability Check\n\nEnsure every documentation file is reachable from `README.md` or `CLAUDE.md`. Orphaned docs are invisible docs.\n\n**Check:**\n- Every `.md` file in the project should be linked from either `README.md` or `CLAUDE.md` (directly or transitively through another linked doc)\n- Flag orphaned docs that have no inbound links\n- Suggest where to add links for orphaned docs\n\n**WHY:** Documentation that cannot be found does not exist from the user's perspective. Every doc must be one or two clicks from the entry points.\n\n\n## Step 8: TODOS.md Update\n\nUpdate the project's task tracking based on the diff.\n\n**Actions:**\n- Mark completed items: scan TODO\u002FFIXME\u002FHACK comments that were removed in the diff and mark corresponding items as done\n- Flag new deferred work: scan TODO\u002FFIXME\u002FHACK comments that were added in the diff and create new tracking entries\n- Update completion percentages if the project uses progress tracking\n\n```bash\n# Find new TODOs added in the diff\nNEW_TODOS=$(echo \"$DIFF_FULL\" | grep '^+' | grep -iE 'TODO|FIXME|HACK' | grep -v '^+++' || true)\nif [[ -n \"$NEW_TODOS\" ]]; then\n  echo \"New TODOs found in diff:\"\n  echo \"$NEW_TODOS\"\nfi\n\n# Find TODOs removed in the diff\nREMOVED_TODOS=$(echo \"$DIFF_FULL\" | grep '^-' | grep -iE 'TODO|FIXME|HACK' | grep -v '^---' || true)\nif [[ -n \"$REMOVED_TODOS\" ]]; then\n  echo \"Resolved TODOs (removed in diff):\"\n  echo \"$REMOVED_TODOS\"\nfi\n```\n\n\n## Step 9: Commit Doc Changes\n\nCommit all documentation changes to the current branch and update the PR body with a doc-sync summary.\n\n```bash\n# Stage only .md files that were modified by this skill\ngit add *.md docs\u002F*.md 2>\u002Fdev\u002Fnull || true\n\n# Check if there are staged changes\nif git diff --cached --quiet; then\n  echo \"No documentation changes needed — all docs are up to date.\"\nelse\n  git commit -m \"docs: post-ship documentation sync\n\n  - Auto-updated paths, counts, and version references\n  - CHANGELOG entries polished for user benefit\n  - Cross-doc consistency verified\n  - Discoverability check passed\n  \"\n\n  echo \"Documentation sync committed.\"\nfi\n```\n\nIf a PR exists for the current branch, update its body to include a doc-sync section:\n```bash\n# Update PR body with doc-sync summary (if PR exists)\nPR_NUMBER=$(gh pr view --json number -q '.number' 2>\u002Fdev\u002Fnull || true)\nif [[ -n \"$PR_NUMBER\" ]]; then\n  echo \"Updating PR #$PR_NUMBER with doc-sync summary...\"\nfi\n```\n\n\n## Integration\n\nThis skill is designed to work as a sub-step of `flow-deliver`. After validation and review are complete, invoke doc-sync to ensure documentation stays current with the shipped code.\n\n**Invocation from flow-deliver:**\n```\nAfter PR creation and CI passes:\n1. Run doc-sync to update documentation\n2. Push doc changes to the PR branch\n3. Re-run CI if doc changes affect tests\n```\n\n**Standalone invocation:**\n```\nUser: \"sync docs\"\nUser: \"update documentation after merge\"\nUser: \"document changes from last release\"\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# Post-Ship Documentation Synchronization\n\nAutomated documentation synchronization for the Deliver phase. After code is committed and a PR is created, this skill reads all `.md` files in the project, cross-references the diff, auto-updates factual content, checks cross-doc consistency, and updates the PR body.\n\n\n## Caps\n\n- **Max 30 doc files scanned** — skip files beyond the cap, warn the user\n- **Never clobber CHANGELOG** — append only, never delete existing entries\n- **Ask user before changing narrative\u002Fphilosophy sections** — risky changes require confirmation\n\n\n## Step 1: Discover Docs\n\nFind all `.md` files in the project root (max depth 2), skipping `node_modules\u002F` and `.git\u002F`.\n\n```bash\n# Discover all markdown files (max depth 2, skip noise directories)\nDOC_FILES=$(find . -maxdepth 2 -name '*.md' \\\n  -not -path '.\u002Fnode_modules\u002F*' \\\n  -not -path '.\u002F.git\u002F*' \\\n  -not -path '.\u002Fvendor\u002F*' \\\n  -not -path '.\u002F.claude\u002F*' \\\n  2>\u002Fdev\u002Fnull | head -30)\n\nDOC_COUNT=$(echo \"$DOC_FILES\" | wc -l | tr -d ' ')\necho \"Found $DOC_COUNT doc files to scan (cap: 30)\"\n\nif [[ \"$DOC_COUNT\" -ge 30 ]]; then\n  echo \"WARNING: Doc file cap reached (30). Some files may be skipped.\"\nfi\n```\n\nRead each discovered doc file so you have their current content in context.\n\n\n## Step 2: Cross-Reference Diff\n\nRun `git diff --stat HEAD~1` (or diff against the base branch if on a feature branch) to identify which files changed and what content may now be stale in each doc.\n\n```bash\n# Get the diff stat to identify changed files\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nif [[ \"$BRANCH\" == \"main\" || \"$BRANCH\" == \"master\" ]]; then\n  DIFF_STAT=$(git diff --stat HEAD~1)\n  DIFF_FULL=$(git diff HEAD~1)\nelse\n  BASE_BRANCH=$(git merge-base HEAD main 2>\u002Fdev\u002Fnull || git merge-base HEAD master 2>\u002Fdev\u002Fnull)\n  DIFF_STAT=$(git diff --stat \"$BASE_BRANCH\"..HEAD)\n  DIFF_FULL=$(git diff \"$BASE_BRANCH\"..HEAD)\nfi\n\necho \"$DIFF_STAT\"\n```\n\nFor each doc file, check whether any paths, function names, counts, or version numbers mentioned in the doc were affected by the diff.\n\n\n## Step 3: Auto-Update Factual Corrections\n\nFix paths, counts, table entries, and version numbers automatically. These are mechanical changes that do not alter meaning.\n\n**Auto-update targets:**\n- File paths that were renamed or moved in the diff\n- Numeric counts (e.g., \"42 tests\" when the number changed)\n- Version strings (e.g., `v9.5.0` when `package.json` bumped)\n- Table entries referencing renamed or removed items\n- Import\u002Frequire paths that changed\n\n**WHY:** Stale factual references erode trust in documentation. A user who sees a wrong path or count will doubt everything else in the doc.\n\n\n## Step 4: Risky Change Detection\n\nFlag narrative, philosophy, or security-related doc sections for user confirmation. Do NOT auto-edit these.\n\n**Risky categories (require user approval):**\n- Sections with headings containing: \"Philosophy\", \"Principles\", \"Vision\", \"Mission\", \"Security\", \"Threat Model\", \"Architecture Decision\"\n- Paragraphs that express opinion, strategy, or rationale (not just facts)\n- Content under `## Why` or `## Rationale` headings\n- Any changes to `SECURITY.md` or `CONTRIBUTING.md` beyond version bumps\n\n**WHY:** Narrative and philosophy sections reflect human judgment. Silently rewriting them risks misrepresenting the project's intent.\n\nWhen risky changes are detected, present them to the user:\n```\nThe following doc sections may need updating but contain narrative\u002Fphilosophy content.\nI will NOT auto-edit these. Please review and confirm each change:\n\n1. README.md ## Philosophy — mentions \"single-binary deployment\" but diff adds Docker support\n2. SECURITY.md ## Threat Model — new auth endpoint not documented\n\nApprove changes? (list numbers to approve, or \"skip all\")\n```\n\n\n## Step 5: CHANGELOG Voice Polish\n\nApply the \"sell test\" to every CHANGELOG entry: **\"Would a user reading this bullet think 'oh nice, I want to try that'?\"**\n\n**Rules:**\n- Lead with the user benefit, not the implementation detail\n- Use active voice (\"Add X\" not \"X was added\")\n- Keep bullets under 120 characters\n- Never delete existing CHANGELOG entries (append only)\n- Group by: Added, Changed, Fixed, Removed (Keep a Changelog format)\n\n**Example transformations:**\n```\nBAD:  \"Refactored spawn_agent to use parameter expansion instead of basename\"\nGOOD: \"Speed up agent spawning by eliminating 750 subshell forks (92% reduction)\"\n\nBAD:  \"Added SUPPORTS_MCP_ELICITATION flag\"\nGOOD: \"Support MCP elicitation for richer interactive prompts (CC v2.1.76+)\"\n```\n\n**WHY:** The CHANGELOG is marketing copy for developers. Every bullet should make someone want to upgrade.\n\n\n## Step 6: Cross-Doc Consistency\n\nCheck that key values are aligned across all documentation files.\n\n**Consistency checks:**\n- Version numbers match across `README.md`, `CLAUDE.md`, `package.json`, `CHANGELOG.md`, and any other files referencing the current version\n- Feature lists in README match what is actually implemented (cross-reference with command\u002Fskill directories)\n- Badge URLs and shield.io references are up to date\n- Links between docs are not broken (relative path references)\n- Command counts and skill counts match actual directory listings\n\n```bash\n# Example: check version consistency\nPKG_VERSION=$(grep '\"version\"' package.json | head -1 | sed 's\u002F.*\"version\": *\"\u002F\u002F' | sed 's\u002F\".*\u002F\u002F')\necho \"package.json version: $PKG_VERSION\"\n\n# Check README mentions this version\nif ! grep -q \"$PKG_VERSION\" README.md 2>\u002Fdev\u002Fnull; then\n  echo \"WARNING: README.md does not mention version $PKG_VERSION\"\nfi\n\n# Check CHANGELOG has an entry for this version\nif ! grep -q \"$PKG_VERSION\" CHANGELOG.md 2>\u002Fdev\u002Fnull; then\n  echo \"WARNING: CHANGELOG.md has no entry for version $PKG_VERSION\"\nfi\n```\n\n\n## Step 7: Discoverability Check\n\nEnsure every documentation file is reachable from `README.md` or `CLAUDE.md`. Orphaned docs are invisible docs.\n\n**Check:**\n- Every `.md` file in the project should be linked from either `README.md` or `CLAUDE.md` (directly or transitively through another linked doc)\n- Flag orphaned docs that have no inbound links\n- Suggest where to add links for orphaned docs\n\n**WHY:** Documentation that cannot be found does not exist from the user's perspective. Every doc must be one or two clicks from the entry points.\n\n\n## Step 8: TODOS.md Update\n\nUpdate the project's task tracking based on the diff.\n\n**Actions:**\n- Mark completed items: scan TODO\u002FFIXME\u002FHACK comments that were removed in the diff and mark corresponding items as done\n- Flag new deferred work: scan TODO\u002FFIXME\u002FHACK comments that were added in the diff and create new tracking entries\n- Update completion percentages if the project uses progress tracking\n\n```bash\n# Find new TODOs added in the diff\nNEW_TODOS=$(echo \"$DIFF_FULL\" | grep '^+' | grep -iE 'TODO|FIXME|HACK' | grep -v '^+++' || true)\nif [[ -n \"$NEW_TODOS\" ]]; then\n  echo \"New TODOs found in diff:\"\n  echo \"$NEW_TODOS\"\nfi\n\n# Find TODOs removed in the diff\nREMOVED_TODOS=$(echo \"$DIFF_FULL\" | grep '^-' | grep -iE 'TODO|FIXME|HACK' | grep -v '^---' || true)\nif [[ -n \"$REMOVED_TODOS\" ]]; then\n  echo \"Resolved TODOs (removed in diff):\"\n  echo \"$REMOVED_TODOS\"\nfi\n```\n\n\n## Step 9: Commit Doc Changes\n\nCommit all documentation changes to the current branch and update the PR body with a doc-sync summary.\n\n```bash\n# Stage only .md files that were modified by this skill\ngit add *.md docs\u002F*.md 2>\u002Fdev\u002Fnull || true\n\n# Check if there are staged changes\nif git diff --cached --quiet; then\n  echo \"No documentation changes needed — all docs are up to date.\"\nelse\n  git commit -m \"docs: post-ship documentation sync\n\n  - Auto-updated paths, counts, and version references\n  - CHANGELOG entries polished for user benefit\n  - Cross-doc consistency verified\n  - Discoverability check passed\n  \"\n\n  echo \"Documentation sync committed.\"\nfi\n```\n\nIf a PR exists for the current branch, update its body to include a doc-sync section:\n```bash\n# Update PR body with doc-sync summary (if PR exists)\nPR_NUMBER=$(gh pr view --json number -q '.number' 2>\u002Fdev\u002Fnull || true)\nif [[ -n \"$PR_NUMBER\" ]]; then\n  echo \"Updating PR #$PR_NUMBER with doc-sync summary...\"\nfi\n```\n\n\n## Integration\n\nThis skill is designed to work as a sub-step of `flow-deliver`. After validation and review are complete, invoke doc-sync to ensure documentation stays current with the shipped code.\n\n**Invocation from flow-deliver:**\n```\nAfter PR creation and CI passes:\n1. Run doc-sync to update documentation\n2. Push doc changes to the PR branch\n3. Re-run CI if doc changes affect tests\n```\n\n**Standalone invocation:**\n```\nUser: \"sync docs\"\nUser: \"update documentation after merge\"\nUser: \"document changes from last release\"\n```\n",{"name":5,"description":7,"disable-model-invocation":50},true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-doc-sync",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":62,"prompt":72,"zipAvailable":50},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-doc-sync",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-doc-sync",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-doc-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-doc-sync\u002FSKILL.md",[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-doc-sync\u002Fagents\u002Fopenai.yaml",[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",[],[]]