[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC08TT9DQKMCF17QFKQDQT":3,"skill-same:01M6MC08TT9DQKMCF17QFKQDQT":107},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6MC08TT9DQKMCF17QFKQDQT","developer-docs-technical-research",null,"Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.","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-technical-research\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"docs","developer docs technical research","technical research","technical","developer","research","technical-writing","drafting","when","writing","developer-docs","meaning","developer documentation","interviews","release notes","ready","documentation","api","notes","product","release","code","2026-11-10 10:12:30",false,"---\nname: developer-docs-technical-research\ndescription: Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Developer Docs Technical Research\n  category: Writing\n  tags: developer-docs,technical-writing,documentation,research,sme-interviews\n---\n\n# Developer Docs Technical Research\n\nUse this skill to investigate product behavior before planning or writing developer documentation. It turns specs, code, prototypes, tickets, SMEs, and hands-on tests into traceable research notes.\n\nThis skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 13, \"Research for Technical Writers,\" Chapter 16, \"Technical Verification,\" Chapter 19, \"Working with Engineers,\" and Chapter 22, \"Working with Product Management.\" 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. State the documentation question, audience, feature, release context, and risk.\n3. Build a source map from code, product surfaces, specs, tickets, SMEs, QA, support, and existing docs.\n4. Use `workflows\u002Fresearch-feature-docs.md` when feature behavior or user consequences are unclear.\n5. Use `workflows\u002Finterview-doc-sources.md` when the main work is extracting facts from SMEs.\n6. Return verified facts, assumptions, contradictions, source owners, and open questions.\n\n## Default Output\n\nWhen completing a documentation research pass, return:\n\n1. **Research brief** - doc question, audience, scope, and decision needed.\n2. **Verified facts** - behavior, limits, defaults, prerequisites, permissions, errors, and examples with source.\n3. **User consequences** - what readers can do, decide, risk, or misunderstand.\n4. **Source map** - authoritative owner or artifact for each important fact.\n5. **Contradictions and gaps** - unresolved disagreements, missing access, or untested behavior.\n6. **Recommended docs action** - plan, draft, defer, file product issue, or request review.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand technical research concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Build a feature research plan | `workflows\u002Fresearch-feature-docs.md` |\n| Interview engineers, PMs, QA, support, or field teams | `workflows\u002Finterview-doc-sources.md` |\n| Route by task or symptom | `guidelines.md` |\n\n## Core Posture\n\n- Research user-facing consequences, not only implementation.\n- Verify directly when the product, API, CLI, UI, or environment is available.\n- Treat named owners and durable artifacts as the source of truth.\n- Keep uncertainty visible until it is resolved.\n- File product or UX defects when documentation would be forced to explain avoidable confusion.\n","# Developer Docs Technical Research\n\nUse this skill to investigate product behavior before planning or writing developer documentation. It turns specs, code, prototypes, tickets, SMEs, and hands-on tests into traceable research notes.\n\nThis skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 13, \"Research for Technical Writers,\" Chapter 16, \"Technical Verification,\" Chapter 19, \"Working with Engineers,\" and Chapter 22, \"Working with Product Management.\" 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. State the documentation question, audience, feature, release context, and risk.\n3. Build a source map from code, product surfaces, specs, tickets, SMEs, QA, support, and existing docs.\n4. Use `workflows\u002Fresearch-feature-docs.md` when feature behavior or user consequences are unclear.\n5. Use `workflows\u002Finterview-doc-sources.md` when the main work is extracting facts from SMEs.\n6. Return verified facts, assumptions, contradictions, source owners, and open questions.\n\n## Default Output\n\nWhen completing a documentation research pass, return:\n\n1. **Research brief** - doc question, audience, scope, and decision needed.\n2. **Verified facts** - behavior, limits, defaults, prerequisites, permissions, errors, and examples with source.\n3. **User consequences** - what readers can do, decide, risk, or misunderstand.\n4. **Source map** - authoritative owner or artifact for each important fact.\n5. **Contradictions and gaps** - unresolved disagreements, missing access, or untested behavior.\n6. **Recommended docs action** - plan, draft, defer, file product issue, or request review.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand technical research concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Build a feature research plan | `workflows\u002Fresearch-feature-docs.md` |\n| Interview engineers, PMs, QA, support, or field teams | `workflows\u002Finterview-doc-sources.md` |\n| Route by task or symptom | `guidelines.md` |\n\n## Core Posture\n\n- Research user-facing consequences, not only implementation.\n- Verify directly when the product, API, CLI, UI, or environment is available.\n- Treat named owners and durable artifacts as the source of truth.\n- Keep uncertainty visible until it is resolved.\n- File product or UX defects when documentation would be forced to explain avoidable confusion.\n",{"name":5,"license":15,"metadata":59,"description":7,"compatibility":64},{"tags":60,"version":61,"category":62,"displayName":63},"developer-docs,technical-writing,documentation,research,sme-interviews","0.1.0","Writing","Developer Docs Technical Research","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research",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":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-technical-research",{"tool":81,"command":82},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-technical-research",{"tool":84,"command":85},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill developer-docs-technical-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research\u002FSKILL.md",true,[89,95,99,103],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"guidelines.md","REFERENCE","参考文档",2144,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research\u002Fguidelines.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fcore\u002Fknowledge.md",7139,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":100,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":101,"sourceHtmlUrl":102},"workflows\u002Finterview-doc-sources.md",3315,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research\u002Fworkflows\u002Finterview-doc-sources.md",{"path":104,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":105,"sourceHtmlUrl":106},"workflows\u002Fresearch-feature-docs.md",3631,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdeveloper-docs-technical-research\u002Fworkflows\u002Fresearch-feature-docs.md",[108,117,125,133,141,149],{"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":116},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":116},"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":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":116},"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":116},"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":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":116},"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":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":116},"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",[],[]]