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.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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.python-docx and checking the requested text, tables, and section structure.scripts/render_docx.py or an available permissive office renderer, inspect the images, fix defects, and render again.interpreter-app tools builtin-interpreter interpreter_refresh_file --json '{"path":"/absolute/path.docx"}' once after the final write.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.
.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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。