[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVFXFT41W6D3ZWDJJSSDAT":3,"skill-same:01M7BVFXFT41W6D3ZWDJJSSDAT":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BVFXFT41W6D3ZWDJJSSDAT","document-processing-and-graphics",null,"Create, read, edit, and redline documents; create diagrams, charts, and data visualizations, including standalone graphics.","nguyenhungtran18\u002Fskill-and-tool-tracker","nguyenhungtran18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F297063550?v=4","01M7BV0BFPRRFP84F2ME0FYZ9D","01M7BV0BG83FA5P22NJV0GR0A5",1,"MIT","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Foffice-document-processing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: document-processing-and-graphics\ndescription: Create, read, edit, and redline documents; create diagrams, charts, and data visualizations, including standalone graphics.\n---\n\n## Document Processing, Visualizations, and Graphics\n\nIn general, when the user asks for a change to an existing document, make the smallest surgical change. Keep the existing document content and style intact unless the user asks otherwise.\n\nBefore overwriting an Office file, check for signs it is open, like a nearby `~$` lock file. Warn that Word may not refresh an already-open document until it is reopened.\n\n### Style\n\nDo not overly use gradients and shadows. Do not use pale, low opacity, low vibrancy colors that look \"calm\". Make text and shapes legible, use clean colors. When text is on background, check contrast and adjust text color if needed.\n\nIf there are patterns in user's existing documents, follow them.\n\n#### Typography\n\nFor boring documents, use the default font. For creative work like diagrams or PowerPoint, choose a font based on context:\n* on macOS: San Francisco (SFNS.ttf), HelveticaNeue.ttc, Futura.ttc, Georgia.ttf, etc.\n* on Windows\u002FLinux: Arial, Trebuchet MS, Verdana, Georgia, etc.\n\nIf you need to use fonts in Pillow, stage the font files first. NEVER use Arial over Helvetica. NEVER set a negative letter-spacing.\n\n#### Color Palette\n\nFor documents and diagrams, start with one of these palettes:\n* Formal: `#F6F7F8`, `#18212B`, `#0868E0`, `#9CBFDF`, `#C66A36`\n* Casual 1: `#F5F1E8`, `#26332F`, `#F48067`, `#00B49B`, `#FFEFAE`\n* Casual 2: `#EDF2EF`, `#24312D`, `#217F73`, `#A5CBB4`, `#E46146`\n* Modernist: `#F2F0E9`, `#181817`, `#E33B2E`, `#1458C0`, `#F0BB24`\n\n### Redlining\n\nFor redlining, review, or comment requests in Word documents, use Office's tracked changes feature. Understand the context, and do not overdo it if the user asked for casual comments.\n\nFor each change, add a brief comment only when helpful. Make tracked changes as surgical as possible: instead of deleting and replacing a whole section just to insert two words, delete or add only the exact terms needed. Minimize the visible change in the document.\n\nWhen editing DOCX XML directly:\n* Use a namespace-aware XML parser, not regex or string replacement.\n* A `w:p` has at most one leading `w:pPr`; inside `w:del`, use `w:delText`, not `w:t`.\n* Preserve non-text markup and keep comments, relationships, and content types synchronized.\n\n### Filling Forms \u002F Templates\n\nWhen asked to fill forms or templates, do only what the user asked. Do not make unnecessary content or appearance changes.\n\n### Diagrams\n\nWhen asked to create graphs or diagrams, hand-generate them in SVG format unless the user explicitly asks otherwise. If `render_svg` is available, use it to inspect the rendered image.\n\nInspect every rendered diagram. Treat the initial layout and container bounds as provisional. Check every label, especially right and bottom padding; no text may overlap or overflow. Resize containers and position their icon\u002Ftext content as one balanced group with consistent gaps. Check connectors and make sure arrowheads are sized correctly. Keep refining until the diagram looks intentional and 100% perfect.\n\n### PDF\n\nVisually inspect every PDF you create or modify before delivering it, using `pdf_to_images` when available. Check page breaks, clipping, margins, overlaps, blank pages, inconsistent spacing, and text or images crossing page bounds. Keep refining until the PDF looks intentional and polished.\n\n### PowerPoint\n\nRefer to the `power-point-processing` skill.\n\n### Excel\n\nSpreadsheet data is high-stakes. Always double-check before and after exporting or overwriting the user's files. When creating Excel files, aim for a simple structure by default.\n","## Document Processing, Visualizations, and Graphics\n\nIn general, when the user asks for a change to an existing document, make the smallest surgical change. Keep the existing document content and style intact unless the user asks otherwise.\n\nBefore overwriting an Office file, check for signs it is open, like a nearby `~$` lock file. Warn that Word may not refresh an already-open document until it is reopened.\n\n### Style\n\nDo not overly use gradients and shadows. Do not use pale, low opacity, low vibrancy colors that look \"calm\". Make text and shapes legible, use clean colors. When text is on background, check contrast and adjust text color if needed.\n\nIf there are patterns in user's existing documents, follow them.\n\n#### Typography\n\nFor boring documents, use the default font. For creative work like diagrams or PowerPoint, choose a font based on context:\n* on macOS: San Francisco (SFNS.ttf), HelveticaNeue.ttc, Futura.ttc, Georgia.ttf, etc.\n* on Windows\u002FLinux: Arial, Trebuchet MS, Verdana, Georgia, etc.\n\nIf you need to use fonts in Pillow, stage the font files first. NEVER use Arial over Helvetica. NEVER set a negative letter-spacing.\n\n#### Color Palette\n\nFor documents and diagrams, start with one of these palettes:\n* Formal: `#F6F7F8`, `#18212B`, `#0868E0`, `#9CBFDF`, `#C66A36`\n* Casual 1: `#F5F1E8`, `#26332F`, `#F48067`, `#00B49B`, `#FFEFAE`\n* Casual 2: `#EDF2EF`, `#24312D`, `#217F73`, `#A5CBB4`, `#E46146`\n* Modernist: `#F2F0E9`, `#181817`, `#E33B2E`, `#1458C0`, `#F0BB24`\n\n### Redlining\n\nFor redlining, review, or comment requests in Word documents, use Office's tracked changes feature. Understand the context, and do not overdo it if the user asked for casual comments.\n\nFor each change, add a brief comment only when helpful. Make tracked changes as surgical as possible: instead of deleting and replacing a whole section just to insert two words, delete or add only the exact terms needed. Minimize the visible change in the document.\n\nWhen editing DOCX XML directly:\n* Use a namespace-aware XML parser, not regex or string replacement.\n* A `w:p` has at most one leading `w:pPr`; inside `w:del`, use `w:delText`, not `w:t`.\n* Preserve non-text markup and keep comments, relationships, and content types synchronized.\n\n### Filling Forms \u002F Templates\n\nWhen asked to fill forms or templates, do only what the user asked. Do not make unnecessary content or appearance changes.\n\n### Diagrams\n\nWhen asked to create graphs or diagrams, hand-generate them in SVG format unless the user explicitly asks otherwise. If `render_svg` is available, use it to inspect the rendered image.\n\nInspect every rendered diagram. Treat the initial layout and container bounds as provisional. Check every label, especially right and bottom padding; no text may overlap or overflow. Resize containers and position their icon\u002Ftext content as one balanced group with consistent gaps. Check connectors and make sure arrowheads are sized correctly. Keep refining until the diagram looks intentional and 100% perfect.\n\n### PDF\n\nVisually inspect every PDF you create or modify before delivering it, using `pdf_to_images` when available. Check page breaks, clipping, margins, overlaps, blank pages, inconsistent spacing, and text or images crossing page bounds. Keep refining until the PDF looks intentional and polished.\n\n### PowerPoint\n\nRefer to the `power-point-processing` skill.\n\n### Excel\n\nSpreadsheet data is high-stakes. Always double-check before and after exporting or overwriting the user's files. When creating Excel files, aim for a simple structure by default.\n",{"name":5,"description":7},"main","900ea3c9eb045fd5b0317dc1103777ecf3ea4aeb","skills\u002Foffice-document-processing",0,"https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker","https:\u002F\u002Fnguyenhungtran18.github.io\u002Fskill-and-tool-tracker\u002F","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18","2026-08-31 18:36:09",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill document-processing-and-graphics",{"tool":37,"command":38},"bunx","bunx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill document-processing-and-graphics",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill document-processing-and-graphics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Foffice-document-processing\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7BVP4P83TK60JZ4P8RP9VP7","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fxcode_project_setup\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7BVP01K4CSJJ8G90FT8S2D5","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7BVNY22GXD871GYTSH599F1","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7BVNQWF24RNKA8A4KM2HJ3T","workflow-skill-creator","Distills a completed user workflow or interaction into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say \"make this a skill\", \"create a skill from what we just did\", \"package this workflow\" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow_skill_creator\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7BVNNY67XPCQAQHY3FBKDGC","verify-and-stop","Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverify-and-stop\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7BVNKB4Z7SZT85B73ZZ90Y6","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[]]