Index of every page on this site: llms.txt
All skills
apple avatar

/creator-studio-doc-format

@995911c
Run it yourself

Read, create, and edit Keynote presentations in Keynote Interchange Format (.keyx) as files, with no app running. Use when the user asks to create, make, generate, or build slides, a slideshow, a deck, a presentation, or a Keynote file, or to change, restyle, summarize, or extract text from an existing .keyx.

Use this Skill: https://skilld.dev/gh/apple/creator-studio-doc-format/creator-studio-doc-format

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈84 tokens for metadata: the name and description. ≈1k when used: this file.

Description uses 4.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈338 characters, or 4.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Keynote presentations

You read, create, and edit Keynote presentations (Keynote Interchange Format .keyx files) by writing a small Python program with the creator_studio_doc_format library.

Workflow

0. Check the setup

Neither placeholder in this skill is a shell environment variable. Substitute the actual value for each one everywhere it appears:

  • <PYTHON> is the interpreter that has creator_studio_doc_format installed. Run every script with it as the first token of the shell command.
  • <PKG> is the installed library's package directory. Read and search it by absolute path.

If your context already gives a value for each, use those. Otherwise use the python in the project's active virtual environment. Then print <PKG> with:

<PYTHON> -c "import creator_studio_doc_format as m, os; print(os.path.dirname(m.__file__))"

If the import fails, creator-studio-doc-format isn't installed. Tell the user to run pip install creator-studio-doc-format in that environment, and stop. Don't install it yourself.

1. Look up the API in the installed package

Start from the examples, then look up exact fields:

  • Start at <PKG>/examples/README.md. It indexes every sample script and says what each covers. Then read the sample scripts it points to, which are working patterns to copy. Take filenames from that index, not from memory.
  • Search for exact field names and types when the examples don't cover something. Search <PKG>/core/models.py for a pattern such as class Shape. The file is large, so search it rather than reading it whole. Enumeration values are exact strings, so look them up rather than guessing a synonym.

What the script does depends on the request:

  • To create a presentation, build the top-level document and save it.
  • To edit a presentation, open the user's file with KeyxDocument.open, change the models, and save. Save to a new filename unless the user asks to overwrite the original.
  • To analyze a presentation, open the file and read it. No save is needed.

A real document can hold thousands of models, so print only a depth-limited view of one and filter navigation.iterate_models to find a model, instead of printing a whole subtree. <PKG>/examples/inspection.py shows both.

2. Run and deliver

Write the script in the user's working directory, and run it with the interpreter:

<PYTHON> <script>.py

Pass validate_document to save as a pre_save_hooks entry, as the examples do. validate_document raises before anything is written if the document breaks the format's rules. If the script raises, read the error, fix the script, and rerun it. Keep validate_document in pre_save_hooks on every run, including the rerun after a failed save, because removing it to force a save isn't a fix. Hand over only a document that has passed it.

After a save, tell the user the output path. After an analysis, report what you found.

Design defaults

These apply when you create or restyle slides. Commit to a clear aesthetic direction, such as bold minimalism, editorial density, warm organic, or sharp corporate. Intentionality matters more than intensity. Give each presentation a look of its own, rather than the same generic one.

The following are soft priors, so deviate when the content justifies it:

  • Hold colors, typography, and spatial logic consistent throughout.
  • Limit icons and emoji to an intentional, consistent visual language.
  • Prefer negative space over filling the canvas, and fragments over full sentences.
  • Scale the following point sizes proportionally if you change the canvas from its default of 1920 x 1080 pt.
  • Set titles at about 90–150 pt, and body text at about 40–60 pt and at least 32 pt. Body text is anything the audience reads as content, including descriptions, bullets, and captions under icons or images. Only footers, slide numbers, and source notes go smaller.
  • Give one section of a multisection grid more weight than the rest, so the slide keeps its hierarchy.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill includes security considerations such as the dynamic generation and execution of Python scripts and the processing of external Keynote files. While these warrant review, they are used within the skill's intended functionality for document formatting. See detailed analysis for context.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

Signed by skilld at 995911c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 19 hours ago.

Activeupdated 4 days ago

README badge

README badge for apple/creator-studio-doc-format