Notion Skills — teach agents how your team works
Generate a skill from existing work, then show team sharing and local export separately. Both distribution paths center on the same document.
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 — teach agents how your team works · 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>Motion and composition
Local motion · Composition rules
Keep the skill's source on screen

Open the skill document after the menu and first invocation, making its name and content the common reference for subsequent actions. Overlay the sharing dialog on the document, and return to the original content when it closes.
Explain one clear action for sharing and one for downloading
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 — teach agents how your team works · 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="clip" data-start="13" data-end="29"><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>Present sharing settings first, then download options and confirmation. Let selected menu states, dialog titles and completion messages hand off attention in sequence; do not combine permissions and local export in one hard-to-read window.
Terminal invocation continues from the package just exported
Use the same skill name when switching to the terminal. Allow a brief pause between the light document and black terminal; finish once the command completes, without introducing new files or workflows.
Keep the tool demonstration straightforward
Build the main style from a white workspace, thin borders, medium-bold sans-serif headings and small menu text. Use pale blue, apricot yellow and purple backgrounds for section changes, and dark monospace text for commands; always frame the current selection in a clear local close-up.
Adapt to another distributable resource
Replace the skill name, document body, sharing recipients, download file and command together. Rule packages, research templates or design guides can use this structure, provided the editable source and usage entry point remain clear.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to rule packages; preserve the editable source, sharing permissions and usage entry point.
Production constraints
Skill menu / Input field / Document / Sharing dialog / Download menu / Terminal
- Team sharing and local export are two distribution paths, each explained through a dialog before converging on usage.
- Interaction close-ups follow the current setting while keeping the document as the source.