本文へ移動
cccskills
無料GitHub で公開

slides

Create, inspect, and edit editable PowerPoint (`.pptx`) decks with local code execution. Use for slide decks, presentations, speaker notes, charts, tables, images, and layout-sensitive presentation work.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md1.9 KB
  • agents/openai.yaml223 B
  • LICENSE.txt10.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

PowerPoint workflow

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

Workflow

  1. Inspect the source deck before editing. Preserve its theme, layouts, masters, dimensions, and visible identity unless the user asks for a redesign.
  2. Use python-pptx for editable text, tables, images, shapes, charts, and speaker notes. Use one cohesive builder script for a new deck or substantial revision.
  3. Keep real slide text and data editable. Do not flatten an entire slide into a screenshot.
  4. Use consistent margins, alignment, typography, and color. Prefer a clear visual hierarchy over dense bullet lists.
  5. Validate the .pptx as a ZIP package, reopen it with python-pptx, and confirm slide count and key content.
  6. If a permissive renderer is available, render every slide to images and inspect for clipping, overflow, poor contrast, and accidental overlap.
  7. If the deck is open in Interpreter, call interpreter-app tools builtin-interpreter interpreter_refresh_file --json '{"path":"/absolute/path.pptx"}' once after the final write.

Dependencies

uv pip install python-pptx pillow

Use an existing Python installation when available. Install only missing dependencies, and request approval for exact system-level installation commands.

Quality bar

  • Deliver a valid, editable .pptx with no placeholder or implementation text.
  • Keep titles, body text, labels, and charts legible at presentation distance.
  • Check every slide, not only the title slide.
  • Preserve source assets and notes when revising an existing deck.
  • Keep helper scripts and rendered previews outside the final deliverable folder.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

audit-xls

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

openinterpreter/interpreter-workstation222026年10月10日 更新

openinterpreter のスキルをすべて見る

このスキルの問題を報告する