AGENT SKILL

document-processing-and-graphics

Create, read, edit, and redline documents; create diagrams, charts, and data visualizations, including standalone graphics.

License 许可
MIT
最近更新
2026-08-31
Stars
★ 1
Forks
0

01 前言 Front Matter

name
document-processing-and-graphics
description
Create, read, edit, and redline documents; create diagrams, charts, and data visualizations, including standalone graphics.

03 SKILL.md 正文

Document Processing, Visualizations, and Graphics

In 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.

Before 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.

Style

Do 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.

If there are patterns in user's existing documents, follow them.

Typography

For boring documents, use the default font. For creative work like diagrams or PowerPoint, choose a font based on context:

  • on macOS: San Francisco (SFNS.ttf), HelveticaNeue.ttc, Futura.ttc, Georgia.ttf, etc.
  • on Windows/Linux: Arial, Trebuchet MS, Verdana, Georgia, etc.

If you need to use fonts in Pillow, stage the font files first. NEVER use Arial over Helvetica. NEVER set a negative letter-spacing.

Color Palette

For documents and diagrams, start with one of these palettes:

  • Formal: #F6F7F8, #18212B, #0868E0, #9CBFDF, #C66A36
  • Casual 1: #F5F1E8, #26332F, #F48067, #00B49B, #FFEFAE
  • Casual 2: #EDF2EF, #24312D, #217F73, #A5CBB4, #E46146
  • Modernist: #F2F0E9, #181817, #E33B2E, #1458C0, #F0BB24

Redlining

For 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.

For 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.

When editing DOCX XML directly:

  • Use a namespace-aware XML parser, not regex or string replacement.
  • A w:p has at most one leading w:pPr; inside w:del, use w:delText, not w:t.
  • Preserve non-text markup and keep comments, relationships, and content types synchronized.

Filling Forms / Templates

When asked to fill forms or templates, do only what the user asked. Do not make unnecessary content or appearance changes.

Diagrams

When 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.

Inspect 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/text 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.

PDF

Visually 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.

PowerPoint

Refer to the power-point-processing skill.

Excel

Spreadsheet 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.

04 同仓库更多 Skills

nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

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).

★ 1
nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

★ 1
nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

★ 1
nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

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).

★ 1
nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

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.

★ 1
nguyenhungtran18
nguyenhungtran18/skill-and-tool-tracker

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

★ 1