[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KK6BAQJXP4068D1R1566S6":3,"skill-same:01M6KK6BAQJXP4068D1R1566S6":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6KK6BAQJXP4068D1R1566S6","structured-document-creation",null,"Create coordinated internal\u002Fexternal documents from reference materials with consistent formatting and cross-references","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fstructured-document-creation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33],"document","structured","creation","structured document creation","documents","create","reference","references","formatting","with","materials","2026-11-10 10:12:30",false,"---\nname: structured-document-creation\ndescription: Create coordinated internal\u002Fexternal documents from reference materials with consistent formatting and cross-references\n---\n\n# Structured Document Creation Workflow\n\nThis skill guides you through creating multiple audience-specific documents from a single reference source while maintaining consistency, proper formatting, and cross-references.\n\n## When to Use This Skill\n\nUse this pattern when you need to:\n- Create both internal and external-facing documents from the same source material\n- Maintain consistent information across multiple documents\n- Extract structured requirements (timelines, roles, steps, policies)\n- Ensure proper cross-referencing between related documents\n\n## Step-by-Step Instructions\n\n### Step 1: Read and Analyze Reference Material\n\nFirst, thoroughly read the reference document to understand the source content.\n\n```python\n# Example: Read reference document\nfrom docx import Document\n\ndef read_reference_doc(path):\n    doc = Document(path)\n    content = []\n    for para in doc.paragraphs:\n        content.append(para.text)\n    return '\\n'.join(content)\n\nreference_content = read_reference_doc('Reference_Document.docx')\n```\n\n**Key actions:**\n- Identify all key sections, policies, and requirements\n- Note any timelines, deadlines, or time-sensitive information\n- Extract role definitions and responsibilities\n- Identify process steps and workflows\n- Flag any sensitive\u002Finternal-only information\n\n### Step 2: Extract Structured Requirements\n\nCreate a structured extraction of key information categories:\n\n```python\nstructured_requirements = {\n    'timelines': [],      # Deadlines, timeframes, schedules\n    'roles': [],          # Who is responsible for what\n    'steps': [],          # Process steps in order\n    'policies': [],       # Rules and guidelines\n    'contacts': [],       # Points of contact\n    'internal_only': []   # Information not for external audiences\n}\n```\n\n**Extraction checklist:**\n- [ ] All dates and timeframes captured\n- [ ] All roles and responsibilities identified\n- [ ] All process steps documented in sequence\n- [ ] All policies and rules extracted\n- [ ] Sensitive information flagged for internal documents only\n\n### Step 3: Plan Document Structure\n\nBefore creating documents, plan the structure for each audience:\n\n| Document Type | Audience | Content Focus | Formatting |\n|--------------|----------|---------------|------------|\n| Internal | Staff\u002FTeam | Full details, sensitive info, operational specifics | Detailed, technical |\n| External | Clients\u002FPartners | Public-facing info, guidelines, high-level process | Clear, professional |\n\n**Document planning template:**\n```\nInternal Document:\n- Title: [Descriptive internal title]\n- Sections: [List all sections with subsections]\n- Cross-refs: [References to external document]\n- Sensitive content: [Mark internal-only sections]\n\nExternal Document:\n- Title: [Client\u002Fpartner-friendly title]\n- Sections: [Public-appropriate sections only]\n- Cross-refs: [References to internal document if applicable]\n- Exclusions: [List what's omitted for external audience]\n```\n\n### Step 4: Create Documents with Consistent Formatting\n\nCreate each document maintaining:\n- Consistent terminology across all documents\n- Matching section numbering where applicable\n- Aligned visual formatting (headers, bullets, tables)\n- Clear cross-references between documents\n\n```python\n# Example: Create document with consistent structure\nfrom docx import Document\nfrom docx.shared import Inches, Pt\nfrom docx.enum.text import WD_ALIGN_PARAGRAPH\n\ndef create_document_template(title, sections):\n    doc = Document()\n    \n    # Title\n    heading = doc.add_heading(title, 0)\n    heading.alignment = WD_ALIGN_PARAGRAPH.CENTER\n    \n    # Add sections\n    for section in sections:\n        doc.add_heading(section['title'], level=1)\n        for content in section['content']:\n            doc.add_paragraph(content)\n    \n    return doc\n```\n\n### Step 5: Add Cross-References\n\nEnsure documents reference each other appropriately:\n\n**Internal document should include:**\n- Reference to external document version\n- Notes on what information is shared externally\n- Links to related internal policies\n\n**External document should include:**\n- Reference to internal contact for questions\n- Version\u002Fdate information\n- Clear scope boundaries\n\n**Cross-reference example:**\n```\nFor internal process details, refer to: [Internal Document Name]\nFor customer-facing guidelines, refer to: [External Document Name]\n```\n\n### Step 6: Quality Check\n\nBefore finalizing, verify:\n\n**Consistency checks:**\n- [ ] Same terminology used in both documents\n- [ ] Dates and timelines match across documents\n- [ ] Role definitions are consistent\n- [ ] No contradictory information\n\n**Audience appropriateness:**\n- [ ] Internal document contains all necessary operational details\n- [ ] External document excludes sensitive\u002Finternal-only information\n- [ ] External document is clear and professional\n- [ ] Both documents serve their intended purpose\n\n**Cross-reference validation:**\n- [ ] All cross-references are accurate\n- [ ] Document titles\u002Fnames match in references\n- [ ] Version numbers are consistent\n\n## Example Structure\n\n```\nReference Document: Return_Issues.docx\n    ↓\nStructured Extraction\n    ↓\n┌─────────────────────────┬─────────────────────────┐\n│  Internal_RA_Process    │  Key_Account_RA_Policy  │\n│  (Internal Document)    │  (External Document)    │\n├─────────────────────────┼─────────────────────────┤\n│ • Full process details  │ • Customer guidelines   │\n│ • Internal contacts     │ • External timelines    │\n│ • Sensitive criteria    │ • Public policies       │\n│ • Operational steps     │ • Contact information   │\n│ • Cross-ref to external │ • Cross-ref to internal │\n└─────────────────────────┴─────────────────────────┘\n```\n\n## Tips for Success\n\n1. **Start with extraction** - Don't create documents until you've fully extracted structured requirements from the reference\n2. **Maintain a content map** - Track which content goes in which document to avoid omissions or contradictions\n3. **Use consistent headers** - Same section titles where content overlaps helps maintain alignment\n4. **Review both together** - Always review documents side-by-side to catch inconsistencies\n5. **Version together** - Keep both documents on the same version cycle to maintain alignment\n\n## Common Pitfalls to Avoid\n\n- ❌ Creating documents before fully understanding reference material\n- ❌ Inconsistent terminology between internal and external versions\n- ❌ Missing cross-references between related documents\n- ❌ Exposing internal-only information in external documents\n- ❌ Contradictory timelines or requirements across documents\n- ❌ Forgetting to update both documents when source material changes","# Structured Document Creation Workflow\n\nThis skill guides you through creating multiple audience-specific documents from a single reference source while maintaining consistency, proper formatting, and cross-references.\n\n## When to Use This Skill\n\nUse this pattern when you need to:\n- Create both internal and external-facing documents from the same source material\n- Maintain consistent information across multiple documents\n- Extract structured requirements (timelines, roles, steps, policies)\n- Ensure proper cross-referencing between related documents\n\n## Step-by-Step Instructions\n\n### Step 1: Read and Analyze Reference Material\n\nFirst, thoroughly read the reference document to understand the source content.\n\n```python\n# Example: Read reference document\nfrom docx import Document\n\ndef read_reference_doc(path):\n    doc = Document(path)\n    content = []\n    for para in doc.paragraphs:\n        content.append(para.text)\n    return '\\n'.join(content)\n\nreference_content = read_reference_doc('Reference_Document.docx')\n```\n\n**Key actions:**\n- Identify all key sections, policies, and requirements\n- Note any timelines, deadlines, or time-sensitive information\n- Extract role definitions and responsibilities\n- Identify process steps and workflows\n- Flag any sensitive\u002Finternal-only information\n\n### Step 2: Extract Structured Requirements\n\nCreate a structured extraction of key information categories:\n\n```python\nstructured_requirements = {\n    'timelines': [],      # Deadlines, timeframes, schedules\n    'roles': [],          # Who is responsible for what\n    'steps': [],          # Process steps in order\n    'policies': [],       # Rules and guidelines\n    'contacts': [],       # Points of contact\n    'internal_only': []   # Information not for external audiences\n}\n```\n\n**Extraction checklist:**\n- [ ] All dates and timeframes captured\n- [ ] All roles and responsibilities identified\n- [ ] All process steps documented in sequence\n- [ ] All policies and rules extracted\n- [ ] Sensitive information flagged for internal documents only\n\n### Step 3: Plan Document Structure\n\nBefore creating documents, plan the structure for each audience:\n\n| Document Type | Audience | Content Focus | Formatting |\n|--------------|----------|---------------|------------|\n| Internal | Staff\u002FTeam | Full details, sensitive info, operational specifics | Detailed, technical |\n| External | Clients\u002FPartners | Public-facing info, guidelines, high-level process | Clear, professional |\n\n**Document planning template:**\n```\nInternal Document:\n- Title: [Descriptive internal title]\n- Sections: [List all sections with subsections]\n- Cross-refs: [References to external document]\n- Sensitive content: [Mark internal-only sections]\n\nExternal Document:\n- Title: [Client\u002Fpartner-friendly title]\n- Sections: [Public-appropriate sections only]\n- Cross-refs: [References to internal document if applicable]\n- Exclusions: [List what's omitted for external audience]\n```\n\n### Step 4: Create Documents with Consistent Formatting\n\nCreate each document maintaining:\n- Consistent terminology across all documents\n- Matching section numbering where applicable\n- Aligned visual formatting (headers, bullets, tables)\n- Clear cross-references between documents\n\n```python\n# Example: Create document with consistent structure\nfrom docx import Document\nfrom docx.shared import Inches, Pt\nfrom docx.enum.text import WD_ALIGN_PARAGRAPH\n\ndef create_document_template(title, sections):\n    doc = Document()\n    \n    # Title\n    heading = doc.add_heading(title, 0)\n    heading.alignment = WD_ALIGN_PARAGRAPH.CENTER\n    \n    # Add sections\n    for section in sections:\n        doc.add_heading(section['title'], level=1)\n        for content in section['content']:\n            doc.add_paragraph(content)\n    \n    return doc\n```\n\n### Step 5: Add Cross-References\n\nEnsure documents reference each other appropriately:\n\n**Internal document should include:**\n- Reference to external document version\n- Notes on what information is shared externally\n- Links to related internal policies\n\n**External document should include:**\n- Reference to internal contact for questions\n- Version\u002Fdate information\n- Clear scope boundaries\n\n**Cross-reference example:**\n```\nFor internal process details, refer to: [Internal Document Name]\nFor customer-facing guidelines, refer to: [External Document Name]\n```\n\n### Step 6: Quality Check\n\nBefore finalizing, verify:\n\n**Consistency checks:**\n- [ ] Same terminology used in both documents\n- [ ] Dates and timelines match across documents\n- [ ] Role definitions are consistent\n- [ ] No contradictory information\n\n**Audience appropriateness:**\n- [ ] Internal document contains all necessary operational details\n- [ ] External document excludes sensitive\u002Finternal-only information\n- [ ] External document is clear and professional\n- [ ] Both documents serve their intended purpose\n\n**Cross-reference validation:**\n- [ ] All cross-references are accurate\n- [ ] Document titles\u002Fnames match in references\n- [ ] Version numbers are consistent\n\n## Example Structure\n\n```\nReference Document: Return_Issues.docx\n    ↓\nStructured Extraction\n    ↓\n┌─────────────────────────┬─────────────────────────┐\n│  Internal_RA_Process    │  Key_Account_RA_Policy  │\n│  (Internal Document)    │  (External Document)    │\n├─────────────────────────┼─────────────────────────┤\n│ • Full process details  │ • Customer guidelines   │\n│ • Internal contacts     │ • External timelines    │\n│ • Sensitive criteria    │ • Public policies       │\n│ • Operational steps     │ • Contact information   │\n│ • Cross-ref to external │ • Cross-ref to internal │\n└─────────────────────────┴─────────────────────────┘\n```\n\n## Tips for Success\n\n1. **Start with extraction** - Don't create documents until you've fully extracted structured requirements from the reference\n2. **Maintain a content map** - Track which content goes in which document to avoid omissions or contradictions\n3. **Use consistent headers** - Same section titles where content overlaps helps maintain alignment\n4. **Review both together** - Always review documents side-by-side to catch inconsistencies\n5. **Version together** - Keep both documents on the same version cycle to maintain alignment\n\n## Common Pitfalls to Avoid\n\n- ❌ Creating documents before fully understanding reference material\n- ❌ Inconsistent terminology between internal and external versions\n- ❌ Missing cross-references between related documents\n- ❌ Exposing internal-only information in external documents\n- ❌ Contradictory timelines or requirements across documents\n- ❌ Forgetting to update both documents when source material changes",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Fstructured-document-creation","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add AG064\u002FOpenSpace --skill structured-document-creation",{"tool":52,"command":53},"bunx","bunx skills add AG064\u002FOpenSpace --skill structured-document-creation",{"tool":55,"command":56},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill structured-document-creation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fstructured-document-creation\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fstructured-document-creation\u002F.skill_id",[67,91,107,116,145,161],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":34},"01M6KKMPWA0B5SCCH766F8M5EA","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python","typescript",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":34},"01M6KKMJXVBNVEY3TRK055F4A7","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[98,99,76,87,100,101,88,89,102,103,104,105,106,80,82,32],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":34},"01M6KKMEGX9M9NC105J0W3Q5B9","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[76,114,89,80,104,87,115,88,82],"write special chars heredoc","shell",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":34},"01M6KKM8EJ2AATVHZBNB916WT0","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,128,129,130,90,131,132,133,134,135,80,136,137,138,139,140,141,142,143,144],"worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":34},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[152,153,154,155,80,156,32,157,158,159,160],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":34},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[168,169,170,171,172,173,88,174,175,176],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]