{
  "schemaVersion": "1.0",
  "item": {
    "slug": "word-docx",
    "name": "DOCX",
    "source": "tencent",
    "type": "skill",
    "category": "内容创作",
    "sourceUrl": "https://clawhub.ai/ivangdavila/word-docx",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/word-docx",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/word-docx",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=word-docx",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/word-docx"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/word-docx",
    "agentPageUrl": "https://openagent3.xyz/skills/word-docx/agent",
    "manifestUrl": "https://openagent3.xyz/skills/word-docx/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/word-docx/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "When to Use",
        "body": "Use when the main artifact is a Microsoft Word document or .docx file, especially when tracked changes, comments, headers, numbering, fields, tables, templates, or compatibility matter."
      },
      {
        "title": "1. Treat DOCX as OOXML, not plain text",
        "body": "A .docx file is a ZIP of XML parts, so structure matters as much as visible text.\nThe critical parts are usually word/document.xml, styles.xml, numbering.xml, headers, footers, and relationship files.\nText may be split across multiple runs; never assume one word or sentence lives in one XML node.\nUse different workflows on purpose: structured extraction for quick reading, style-driven generation for new files, and OOXML-aware editing for fragile existing documents.\nIf the job is mainly reading, extracting, or reviewing, prefer a structure-preserving read path before touching OOXML.\nFor deep edits, inspect the package layout instead of relying only on rendered output.\nReading, generating, and preserving an existing reviewed document are different jobs even when the format is the same.\nLegacy .doc inputs usually need conversion before you can trust modern .docx assumptions."
      },
      {
        "title": "2. Preserve styles and direct formatting deliberately",
        "body": "Prefer named styles over direct formatting so the document stays editable.\nStyles layer: paragraph styles, character styles, and direct formatting do not behave the same.\nRemoving direct formatting is often safer than stacking more inline formatting on top.\nWhen editing an existing file, extend the current style system instead of inventing a parallel one.\nCopying content between documents can silently import foreign styles, theme settings, and numbering definitions."
      },
      {
        "title": "3. Lists and numbering are their own system",
        "body": "Bullets and numbering belong to Word's numbering definitions, not pasted Unicode characters.\nabstractNum, num, and paragraph numbering properties all matter, so restart behavior is rarely \"visual only\".\nIndentation and numbering are related but not identical; a list can have broken numbering even if the indent looks right.\nA list that looks correct in one editor can restart, flatten, or renumber itself later if the underlying numbering state is wrong."
      },
      {
        "title": "4. Page layout lives in sections",
        "body": "Margins, orientation, headers, footers, and page numbering are section-level behavior.\nFirst-page and odd/even headers can differ inside the same document, so one header fix may not fix the document.\nSet page size explicitly because A4 and US Letter defaults change pagination and table widths.\nUse section breaks for layout changes; manual spacing and stray page breaks usually create drift.\nHeader and footer media use part-specific relationships, so copied IDs often break images or links.\nTables, page breaks, and headers often drift together, so treat layout fixes as document-wide, not local cosmetic edits.\nTable geometry depends on page width, margins, and fixed widths, so \"close enough\" table edits often break later in Google Docs or LibreOffice."
      },
      {
        "title": "5. Track changes, comments, and fields need precise edits",
        "body": "Visible text is not the full document when tracked changes are enabled.\nInsertions, deletions, and comments carry metadata that can survive careless edits.\nDeleted text may still exist in the XML even when it no longer appears on screen.\nComment anchors and review ranges can break if edits move text without preserving the surrounding structure.\nComment markers and review wrappers do not behave like inline formatting, so moving text carelessly can orphan or misplace them.\nComments, footnotes, bookmarks, and linked media may live in separate parts, not only in the main document body.\nTables of contents, page numbers, dates, cross-references, and mail merge placeholders are fields.\nEdit the field source carefully and expect cached display values to lag until refresh.\nHyperlinks, bookmarks, and references can break if IDs or relationships stop matching.\nBookmarks, footnotes, comment ranges, and cross-references depend on stable anchors even when the visible text seems untouched.\nA document can look correct while still containing stale field output that refreshes later into something different.\nFor review workflows, make minimal replacements instead of rewriting whole paragraphs.\nIn tracked-change workflows, only the changed span should look changed; broad rewrites create noisy reviews and can destroy the original formatting context.\nFor legal, academic, or business review documents, default to review-style edits over wholesale paragraph rewrites unless the user explicitly wants a rewrite."
      },
      {
        "title": "6. Verify round-trip compatibility before delivery",
        "body": "Complex documents can shift between Word, LibreOffice, Google Docs, and conversion tools.\nTables, headers, embedded fonts, and copied styles are common sources of layout drift.\nTreat .docm as macro-bearing and higher risk; treat .doc as legacy input that may need conversion first.\nWhen layout matters, explicit table widths are safer than auto-fit or percentage-style behavior that different editors reinterpret.\nA document that passes a text check can still fail on pagination, table widths, or reference refresh after the recipient opens it."
      },
      {
        "title": "Common Traps",
        "body": "Copy-paste can import unwanted styles and numbering definitions.\nHeader or footer images use part-specific relationships, so reusing IDs blindly breaks them.\nEmpty paragraphs used as spacing make templates fragile; spacing belongs in paragraph settings.\nA clean-looking export can still hide unresolved revisions, comments, or stale field values.\nRestarting lists \"by eye\" usually fails because numbering state lives outside the paragraph text.\nOne visible phrase can be split across several runs, bookmarks, revision tags, or field boundaries.\nReplacing a whole paragraph to change one clause often breaks review quality, bookmarks, comments, or nearby inline formatting.\nDeleting all visible text from a paragraph or list item can still leave behind an empty paragraph mark, empty bullet, or unstable numbering.\nTable auto-fit and percentage-like width behavior can look acceptable in Word and still drift in Google Docs or LibreOffice.\nLibreOffice and Google Docs can shift complex tables, section behavior, and embedded fonts even when Word looks perfect.\nCompatibility mode can silently cap newer features or change pagination behavior.\nA single change in page size or margin defaults can ripple through tables, headers, TOC, and cross-references.\nA revision workflow can look accepted on screen while leftover metadata, comments, or field caches still make the file unstable later.\nTOC entries, footnotes, and cross-references can look correct until the recipient updates fields and exposes broken anchors."
      },
      {
        "title": "Related Skills",
        "body": "Install with clawhub install <slug> if user confirms:\n\ndocuments — General document handling and format conversion.\nbrief — Concise business writing and structured summaries.\narticle — Long-form drafting and editorial structure."
      },
      {
        "title": "Feedback",
        "body": "If useful: clawhub star word-docx\nStay updated: clawhub sync"
      }
    ],
    "body": "When to Use\n\nUse when the main artifact is a Microsoft Word document or .docx file, especially when tracked changes, comments, headers, numbering, fields, tables, templates, or compatibility matter.\n\nCore Rules\n1. Treat DOCX as OOXML, not plain text\nA .docx file is a ZIP of XML parts, so structure matters as much as visible text.\nThe critical parts are usually word/document.xml, styles.xml, numbering.xml, headers, footers, and relationship files.\nText may be split across multiple runs; never assume one word or sentence lives in one XML node.\nUse different workflows on purpose: structured extraction for quick reading, style-driven generation for new files, and OOXML-aware editing for fragile existing documents.\nIf the job is mainly reading, extracting, or reviewing, prefer a structure-preserving read path before touching OOXML.\nFor deep edits, inspect the package layout instead of relying only on rendered output.\nReading, generating, and preserving an existing reviewed document are different jobs even when the format is the same.\nLegacy .doc inputs usually need conversion before you can trust modern .docx assumptions.\n2. Preserve styles and direct formatting deliberately\nPrefer named styles over direct formatting so the document stays editable.\nStyles layer: paragraph styles, character styles, and direct formatting do not behave the same.\nRemoving direct formatting is often safer than stacking more inline formatting on top.\nWhen editing an existing file, extend the current style system instead of inventing a parallel one.\nCopying content between documents can silently import foreign styles, theme settings, and numbering definitions.\n3. Lists and numbering are their own system\nBullets and numbering belong to Word's numbering definitions, not pasted Unicode characters.\nabstractNum, num, and paragraph numbering properties all matter, so restart behavior is rarely \"visual only\".\nIndentation and numbering are related but not identical; a list can have broken numbering even if the indent looks right.\nA list that looks correct in one editor can restart, flatten, or renumber itself later if the underlying numbering state is wrong.\n4. Page layout lives in sections\nMargins, orientation, headers, footers, and page numbering are section-level behavior.\nFirst-page and odd/even headers can differ inside the same document, so one header fix may not fix the document.\nSet page size explicitly because A4 and US Letter defaults change pagination and table widths.\nUse section breaks for layout changes; manual spacing and stray page breaks usually create drift.\nHeader and footer media use part-specific relationships, so copied IDs often break images or links.\nTables, page breaks, and headers often drift together, so treat layout fixes as document-wide, not local cosmetic edits.\nTable geometry depends on page width, margins, and fixed widths, so \"close enough\" table edits often break later in Google Docs or LibreOffice.\n5. Track changes, comments, and fields need precise edits\nVisible text is not the full document when tracked changes are enabled.\nInsertions, deletions, and comments carry metadata that can survive careless edits.\nDeleted text may still exist in the XML even when it no longer appears on screen.\nComment anchors and review ranges can break if edits move text without preserving the surrounding structure.\nComment markers and review wrappers do not behave like inline formatting, so moving text carelessly can orphan or misplace them.\nComments, footnotes, bookmarks, and linked media may live in separate parts, not only in the main document body.\nTables of contents, page numbers, dates, cross-references, and mail merge placeholders are fields.\nEdit the field source carefully and expect cached display values to lag until refresh.\nHyperlinks, bookmarks, and references can break if IDs or relationships stop matching.\nBookmarks, footnotes, comment ranges, and cross-references depend on stable anchors even when the visible text seems untouched.\nA document can look correct while still containing stale field output that refreshes later into something different.\nFor review workflows, make minimal replacements instead of rewriting whole paragraphs.\nIn tracked-change workflows, only the changed span should look changed; broad rewrites create noisy reviews and can destroy the original formatting context.\nFor legal, academic, or business review documents, default to review-style edits over wholesale paragraph rewrites unless the user explicitly wants a rewrite.\n6. Verify round-trip compatibility before delivery\nComplex documents can shift between Word, LibreOffice, Google Docs, and conversion tools.\nTables, headers, embedded fonts, and copied styles are common sources of layout drift.\nTreat .docm as macro-bearing and higher risk; treat .doc as legacy input that may need conversion first.\nWhen layout matters, explicit table widths are safer than auto-fit or percentage-style behavior that different editors reinterpret.\nA document that passes a text check can still fail on pagination, table widths, or reference refresh after the recipient opens it.\nCommon Traps\nCopy-paste can import unwanted styles and numbering definitions.\nHeader or footer images use part-specific relationships, so reusing IDs blindly breaks them.\nEmpty paragraphs used as spacing make templates fragile; spacing belongs in paragraph settings.\nA clean-looking export can still hide unresolved revisions, comments, or stale field values.\nRestarting lists \"by eye\" usually fails because numbering state lives outside the paragraph text.\nOne visible phrase can be split across several runs, bookmarks, revision tags, or field boundaries.\nReplacing a whole paragraph to change one clause often breaks review quality, bookmarks, comments, or nearby inline formatting.\nDeleting all visible text from a paragraph or list item can still leave behind an empty paragraph mark, empty bullet, or unstable numbering.\nTable auto-fit and percentage-like width behavior can look acceptable in Word and still drift in Google Docs or LibreOffice.\nLibreOffice and Google Docs can shift complex tables, section behavior, and embedded fonts even when Word looks perfect.\nCompatibility mode can silently cap newer features or change pagination behavior.\nA single change in page size or margin defaults can ripple through tables, headers, TOC, and cross-references.\nA revision workflow can look accepted on screen while leftover metadata, comments, or field caches still make the file unstable later.\nTOC entries, footnotes, and cross-references can look correct until the recipient updates fields and exposes broken anchors.\nRelated Skills\n\nInstall with clawhub install <slug> if user confirms:\n\ndocuments — General document handling and format conversion.\nbrief — Concise business writing and structured summaries.\narticle — Long-form drafting and editorial structure.\nFeedback\nIf useful: clawhub star word-docx\nStay updated: clawhub sync"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/word-docx",
    "publisherUrl": "https://clawhub.ai/ivangdavila/word-docx",
    "owner": "ivangdavila",
    "version": "1.0.2",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/word-docx",
    "downloadUrl": "https://openagent3.xyz/downloads/word-docx",
    "agentUrl": "https://openagent3.xyz/skills/word-docx/agent",
    "manifestUrl": "https://openagent3.xyz/skills/word-docx/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/word-docx/agent.md"
  }
}