ııı motion.mdVideo style specification
Notion / V088

Notion Skills API — skills for ChatGPT and Claude

Use three corresponding sections to show how shared knowledge flows: edit together, enter the repository, then be used by different agents.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 23.77 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Notion Skills API — skills for ChatGPT and Claude · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ffffff}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsSkill documentRepository directoryMultiple agent windowsMessage captions
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Follow every message with a specific interface

Follow the collaborative-editing message with the skill document, the automatic-sync message with the repository directory, and the cross-agent message with the consumption interface. Short headings appear first, immediately followed by interfaces; give the three sections similar holds to establish a clear rhythm.

02

One document across three containers

8.00s · Composition reference

Keep the skill name and file identity visible in the editor, repository and agent windows. Change containers during transitions while retaining key terms, so viewers can recognize the same content without floating arrows.

03

Make content more prominent than application decoration

White backgrounds, thin borders and medium-bold sans-serif headings create a lightweight tool style. Use light blue, apricot and purple only to distinguish sections and key selections; give body text ample line spacing, with one focal point each in the repository hierarchy and agent input area.

04

Adapt to specifications or design systems

Choose content that can be shared across tools and align its editing name, repository file and agent invocation text. Preserve authoring → distribution → usage, and have each interface show its specific role.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 2.00 seconds
2.00s
Composition reference at 8.00 seconds
8.00s
Composition reference at 12.00 seconds
12.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 21.00 seconds
21.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to specifications, design systems or other shared knowledge; preserve authoring → distribution → consumption.

Production constraints

Skill document / Repository directory / Multiple agent windows / Message captions

  • The same skill moves from document editing to repository synchronization to use by multiple agents, retaining its identity across containers.
  • Short messages lead and corresponding interfaces follow, creating a three-part structure.