Skip to content
cccskills
FreePublished on GitHub

doc

Create, inspect, and edit Word documents (`.docx`) with local code-execution tools. Use for document drafting, structured edits, tables, comments, and layout-sensitive Word deliverables.

The English summary is being prepared. Showing the original description.

Works withWord
See how to install

Files included (6)

  • SKILL.md2.2 KB
  • agents/openai.yaml295 B
  • assets/doc-small.svg1.6 KB
  • assets/doc.png1.2 KB
  • LICENSE.txt10.5 KB
  • scripts/render_docx.py8.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Word documents

This is workflow guidance, not a callable tool. Use the shell or code-execution tool exposed by the active OIX harness. Do not look for a tool named doc.

Workflow

  1. Inspect the source before editing. Preserve its structure, styles, identifiers, and branding unless the user asks for a redesign.
  2. Use python-docx for creation and structured edits. For unsupported features such as tracked changes or complex comments, edit OOXML deliberately and keep the change narrowly scoped.
  3. Write one cohesive script for a substantial change instead of a chain of fragile one-line mutations.
  4. Save to a new file while iterating unless the user explicitly asked to replace the original.
  5. Verify content by reopening the saved document with python-docx and checking the requested text, tables, and section structure.
  6. When layout matters, render every page with scripts/render_docx.py or an available permissive office renderer, inspect the images, fix defects, and render again.
  7. If the file is open in Interpreter, call interpreter-app tools builtin-interpreter interpreter_refresh_file --json '{"path":"/absolute/path.docx"}' once after the final write.

Dependencies

Prefer uv and install only what the task needs:

uv pip install python-docx

Use an existing Python installation when available. If installation is blocked, ask for approval for the exact dependency command.

Quality bar

  • Use named styles and a consistent type, spacing, margin, and heading system.
  • Keep tables within page bounds; avoid clipped text, broken pagination, and accidental blank pages.
  • Preserve source identity and exact requested facts.
  • Keep scratch files outside the final deliverable folder.
  • Reopen the final .docx and inspect all rendered pages before delivery when rendering is available.

This skill is derived from an Apache-2.0 OpenAI document workflow and has been modified for OIX code execution and Workstation refresh behavior.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build a period-end accrual schedule by computing each accrual, citing support, and drafting journal entries for controller approval. Use during month-end close; this drafts entries only and must not post them.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Audit a spreadsheet for formula accuracy, errors, and common financial-model mistakes. Use for selected ranges, single sheets, or whole-workbook model checks including balance-sheet balance, cash tie-out, roll-forwards, and logic sanity.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Use this skill when the user needs advanced Playwright control of an already running browser session through Interpreter's app-managed browser bridge and the `builtin-js-repl` `js_repl` tool, after simple browser page work cannot be handled by the unified `builtin-interpreter` browser page tools.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Drive a native desktop app through Interpreter's builtin-cua-driver. Use get_app_state, click/type/scroll/drag, and verify by calling get_app_state again when the user asks to operate a real desktop app, browser chrome, native dialog, menu, secure prompt, file chooser, or hidden/background window.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Design or revise Interpreter UI for non-developers with an ultra-minimal, utilitarian style inspired by the OpenAI website and ChatGPT, not the developer platform. Use when simplifying settings, onboarding, chat, forms, empty states, or helper copy; when removing extra containers, labels, or visual noise; when replacing technical wording with plain language; when clarifying hierarchy and making the main user action obvious; when making every visible label and status understandable to an average HR admin or other non-technical user; when hiding implementation details such as logs, IDs, endpoints, paths, or protocol names; or when a screen must respect the app's existing CSS variables and light/dark theme behavior.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Use for AI image, video, audio, or 3D generation/editing. Prefer configured media tools when present, estimate cost before running a paid model, and keep provider credentials in the user's environment or provider configuration.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

See all skills by openinterpreter

Report a problem with this skill