[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBZYZBH7HSR2YWCS4JDTS5":3,"skill-same:01M6MBZYZBH7HSR2YWCS4JDTS5":98},{"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":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MBZYZBH7HSR2YWCS4JDTS5","developer-docs-editing-review",null,"Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"review","docs","developer docs editing review","developer","editing","refactoring","when","developer-docs","claims","developer documentation","brevity","technical-writing","structure","edit","testing","verification","qa","release","code","documentation","writing","2026-11-10 10:12:30",false,"---\nname: developer-docs-editing-review\ndescription: Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Developer Docs Editing Review\n  category: Writing\n  tags: developer-docs,technical-writing,documentation,editing,review\n---\n\n# Developer Docs Editing Review\n\nUse this skill to improve developer documentation after a draft exists. It treats editing as validation and refactoring: check whether the doc is accurate, complete, structured, clear, brief, and reviewable.\n\nThis skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 4, \"Editing documentation.\" It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 15, \"Technical Editing,\" and Chapter 16, \"Technical Verification.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify doc type, audience, source of truth, and release risk.\n3. Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.\n4. Use `workflows\u002Fverify-technical-doc.md` when procedures, migrations, security, data, or production changes need formal verification.\n5. Use `workflows\u002Fedit-developer-doc.md` for a full edit.\n6. Return findings first when the user asks for a review; return revised text when the user asks for an edit.\n\n## Default Output\n\nWhen reviewing documentation, return:\n\n1. **Findings** - ordered by reader risk, with file\u002Fsection references when available.\n2. **Missing validation** - commands, examples, screenshots, API facts, or source claims not checked.\n3. **Verification route** - self-test, SME review, QA test, or release blocker.\n4. **Recommended edits** - exact changes or rewrites.\n5. **Review routing** - who should validate technical details.\n6. **Residual risk** - assumptions that remain after the edit.\n\nWhen editing directly, return the revised doc plus a brief change summary and unresolved questions.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand editing passes | `references\u002Fcore\u002Fknowledge.md` |\n| Apply review rules | `references\u002Fcore\u002Fknowledge.md` |\n| See examples of edits and feedback | `references\u002Fcore\u002Fknowledge.md` |\n| Run a full edit | `workflows\u002Fedit-developer-doc.md` |\n| Verify risky technical docs | `workflows\u002Fverify-technical-doc.md` |\n| Route by task | `guidelines.md` |\n\n## Core Posture\n\n- Separate writing from editing; do not polish around an unverified flaw.\n- Prioritize reader-impacting errors over style preferences.\n- Ask for specific reviews from the right technical owners.\n- Treat high-risk procedures as release-blocking until verified or explicitly accepted.\n- Integrate feedback by user need, not by reviewer rank or comment volume.\n","# Developer Docs Editing Review\n\nUse this skill to improve developer documentation after a draft exists. It treats editing as validation and refactoring: check whether the doc is accurate, complete, structured, clear, brief, and reviewable.\n\nThis skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 4, \"Editing documentation.\" It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 15, \"Technical Editing,\" and Chapter 16, \"Technical Verification.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify doc type, audience, source of truth, and release risk.\n3. Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.\n4. Use `workflows\u002Fverify-technical-doc.md` when procedures, migrations, security, data, or production changes need formal verification.\n5. Use `workflows\u002Fedit-developer-doc.md` for a full edit.\n6. Return findings first when the user asks for a review; return revised text when the user asks for an edit.\n\n## Default Output\n\nWhen reviewing documentation, return:\n\n1. **Findings** - ordered by reader risk, with file\u002Fsection references when available.\n2. **Missing validation** - commands, examples, screenshots, API facts, or source claims not checked.\n3. **Verification route** - self-test, SME review, QA test, or release blocker.\n4. **Recommended edits** - exact changes or rewrites.\n5. **Review routing** - who should validate technical details.\n6. **Residual risk** - assumptions that remain after the edit.\n\nWhen editing directly, return the revised doc plus a brief change summary and unresolved questions.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand editing passes | `references\u002Fcore\u002Fknowledge.md` |\n| Apply review rules | `references\u002Fcore\u002Fknowledge.md` |\n| See examples of edits and feedback | `references\u002Fcore\u002Fknowledge.md` |\n| Run a full edit | `workflows\u002Fedit-developer-doc.md` |\n| Verify risky technical docs | `workflows\u002Fverify-technical-doc.md` |\n| Route by task | `guidelines.md` |\n\n## Core Posture\n\n- Separate writing from editing; do not polish around an unverified flaw.\n- Prioritize reader-impacting errors over style preferences.\n- Ask for specific reviews from the right technical owners.\n- Treat high-risk procedures as release-blocking until verified or explicitly accepted.\n- Integrate feedback by user need, not by reviewer rank or comment volume.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"developer-docs,technical-writing,documentation,editing,review","0.1.0","Writing","Developer Docs Editing Review","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-editing-review",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-editing-review",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-editing-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002FSKILL.md",true,[80,86,90,94],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"guidelines.md","REFERENCE","参考文档",1785,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002Fguidelines.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcore\u002Fknowledge.md",8547,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"workflows\u002Fedit-developer-doc.md",2221,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002Fworkflows\u002Fedit-developer-doc.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"workflows\u002Fverify-technical-doc.md",2877,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-editing-review\u002Fworkflows\u002Fverify-technical-doc.md",[99,108,116,124,132,140],{"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":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"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.","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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":107},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":107},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":107},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":107},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":107},"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",[],[]]