[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJ0XA56NASCBEC870PD2EA":3,"skill-same:01M6KJ0XA56NASCBEC870PD2EA":69},{"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":27,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6KJ0XA56NASCBEC870PD2EA","docx-shell-extract",null,"Extract text from DOCX files using shell commands when python-docx is unavailable","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\u002Fdocx-shell-extract\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36],"docx","shell","extract","docx shell extract","python","text","files","commands","python-docx","2026-11-10 10:12:30",false,"---\nname: docx-shell-extract\ndescription: Extract text from DOCX files using shell commands when python-docx is unavailable\n---\n\n# DOCX Shell Extraction\n\n## When to Use This Skill\n\nUse this pattern when you need to read or extract text from Microsoft Word (.docx) files in constrained environments where:\n- The `python-docx` library is not available\n- You cannot install additional Python packages\n- You need a quick, reliable shell-based solution\n\n## Core Technique\n\nDOCX files are ZIP archives containing XML files. The main document content is stored in `word\u002Fdocument.xml`. You can extract and parse this using standard shell tools.\n\n## Step-by-Step Instructions\n\n### Step 1: Extract the document.xml content\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml\n```\n\nThe `-p` flag pipes the content to stdout without extracting to disk.\n\n### Step 2: Strip XML tags to get plain text\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | sed 's\u002F\u003C[^>]*>\u002F\u002Fg'\n```\n\nThis removes all XML tags, leaving the text content.\n\n### Step 3: Clean up whitespace (optional)\n\nFor cleaner output, add additional sed processing:\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' | \\\n  sed 's\u002F&[^;]*;\u002F\u002Fg' | \\\n  sed 's\u002F^[[:space:]]*\u002F\u002F' | \\\n  sed 's\u002F[[:space:]]*$\u002F\u002F' | \\\n  sed '\u002F^$\u002Fd'\n```\n\nThis removes:\n- XML tags\n- XML entities (like `&amp;`, `&lt;`)\n- Leading\u002Ftrailing whitespace\n- Empty lines\n\n### Step 4: Save to a text file (optional)\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' > output.txt\n```\n\n## Complete Example\n\n```bash\n# Extract text from a Word document\nDOCX_FILE=\"report.docx\"\nOUTPUT_FILE=\"report_text.txt\"\n\nunzip -p \"$DOCX_FILE\" word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' | \\\n  sed 's\u002F&[^;]*;\u002F\u002Fg' | \\\n  sed '\u002F^$\u002Fd' > \"$OUTPUT_FILE\"\n\necho \"Extracted text saved to $OUTPUT_FILE\"\n```\n\n## Verification\n\nAfter extraction, verify the content was captured:\n\n```bash\n# Check if output file has content\nif [ -s \"$OUTPUT_FILE\" ]; then\n    echo \"Successfully extracted $(wc -l \u003C \"$OUTPUT_FILE\") lines\"\n    head -5 \"$OUTPUT_FILE\"\nelse\n    echo \"Warning: Output file is empty\"\nfi\n```\n\n## Limitations\n\n- This method extracts raw text without formatting\n- Complex layouts, tables, and images are not preserved\n- Some special characters may need additional handling\n- Works best for text-heavy documents\n\n## Alternatives to Explore\n\nIf this approach fails or the DOCX structure differs:\n- Check for `word\u002Fdocument.xml` existence: `unzip -l filename.docx | grep document.xml`\n- Some documents may use `word\u002F*.xml` with different naming\n- Consider `pandoc` if available: `pandoc filename.docx -t plain`","# DOCX Shell Extraction\n\n## When to Use This Skill\n\nUse this pattern when you need to read or extract text from Microsoft Word (.docx) files in constrained environments where:\n- The `python-docx` library is not available\n- You cannot install additional Python packages\n- You need a quick, reliable shell-based solution\n\n## Core Technique\n\nDOCX files are ZIP archives containing XML files. The main document content is stored in `word\u002Fdocument.xml`. You can extract and parse this using standard shell tools.\n\n## Step-by-Step Instructions\n\n### Step 1: Extract the document.xml content\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml\n```\n\nThe `-p` flag pipes the content to stdout without extracting to disk.\n\n### Step 2: Strip XML tags to get plain text\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | sed 's\u002F\u003C[^>]*>\u002F\u002Fg'\n```\n\nThis removes all XML tags, leaving the text content.\n\n### Step 3: Clean up whitespace (optional)\n\nFor cleaner output, add additional sed processing:\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' | \\\n  sed 's\u002F&[^;]*;\u002F\u002Fg' | \\\n  sed 's\u002F^[[:space:]]*\u002F\u002F' | \\\n  sed 's\u002F[[:space:]]*$\u002F\u002F' | \\\n  sed '\u002F^$\u002Fd'\n```\n\nThis removes:\n- XML tags\n- XML entities (like `&amp;`, `&lt;`)\n- Leading\u002Ftrailing whitespace\n- Empty lines\n\n### Step 4: Save to a text file (optional)\n\n```bash\nunzip -p filename.docx word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' > output.txt\n```\n\n## Complete Example\n\n```bash\n# Extract text from a Word document\nDOCX_FILE=\"report.docx\"\nOUTPUT_FILE=\"report_text.txt\"\n\nunzip -p \"$DOCX_FILE\" word\u002Fdocument.xml | \\\n  sed 's\u002F\u003C[^>]*>\u002F\u002Fg' | \\\n  sed 's\u002F&[^;]*;\u002F\u002Fg' | \\\n  sed '\u002F^$\u002Fd' > \"$OUTPUT_FILE\"\n\necho \"Extracted text saved to $OUTPUT_FILE\"\n```\n\n## Verification\n\nAfter extraction, verify the content was captured:\n\n```bash\n# Check if output file has content\nif [ -s \"$OUTPUT_FILE\" ]; then\n    echo \"Successfully extracted $(wc -l \u003C \"$OUTPUT_FILE\") lines\"\n    head -5 \"$OUTPUT_FILE\"\nelse\n    echo \"Warning: Output file is empty\"\nfi\n```\n\n## Limitations\n\n- This method extracts raw text without formatting\n- Complex layouts, tables, and images are not preserved\n- Some special characters may need additional handling\n- Works best for text-heavy documents\n\n## Alternatives to Explore\n\nIf this approach fails or the DOCX structure differs:\n- Check for `word\u002Fdocument.xml` existence: `unzip -l filename.docx | grep document.xml`\n- Some documents may use `word\u002F*.xml` with different naming\n- Consider `pandoc` if available: `pandoc filename.docx -t plain`",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Fdocx-shell-extract","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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add AG064\u002FOpenSpace --skill docx-shell-extract",{"tool":55,"command":56},"bunx","bunx skills add AG064\u002FOpenSpace --skill docx-shell-extract",{"tool":58,"command":59},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill docx-shell-extract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdocx-shell-extract\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},".skill_id","OTHER","其他",32,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdocx-shell-extract\u002F.skill_id",[70,92,109,117,145,161],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":37},"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",[],[77,78,79,80,81,82,83,84,85,86,87,34,88,89,90,32,91],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","only","template","file","typescript",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":37},"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",[],[99,100,79,89,101,102,90,32,103,104,105,106,107,83,85,108],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper","with",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":37},"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",[],[79,116,32,83,105,89,29,90,85],"write special chars heredoc",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":126,"publishedAt":37},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000033","数据分析师",[127,128,129,130,91,131,132,133,134,135,83,136,137,138,139,140,141,142,143,144],"reference","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":37},"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,83,156,108,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":37},"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,90,174,175,176],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]