---
name: creator-studio-doc-format
description: 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.
title: creator-studio-doc-format
canonical_url: https://skilld.dev/gh/apple/creator-studio-doc-format
last_updated: 2026-11-20T12:30:21.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install apple/creator-studio-doc-format/creator-studio-doc-format`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/creator-studio-doc-format`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/apple/creator-studio-doc-format/creator-studio-doc-format) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/creator-studio-doc-format`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/creator-studio-doc-format --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/creator-studio-doc-format --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

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