paper
/paper
Otwiera, zapisuje i eksportuje dokumenty Paper w OpenPaperDesign, także w chmurze Notion i na serwerze.
- Autor
- gustavonline ↗
- Repozytorium
- openpaperdesign ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 13
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Otwiera, zapisuje i eksportuje dokumenty Paper w OpenPaperDesign, także w chmurze Notion i na serwerze.
Oryginalny opis (EN)
Find, open, create, save, share and export OpenPaperDesign Papers, including personal Papers outside the project and cloud snapshots in Notion. Use for Home, Paper files, Notion save/open, workspace setup and server controls.
Jak działa
- Native plugin app and MCP first
- Find and open
- Work on the Paper
- Share and manage servers
Podgląd SKILL.md
---
name: paper
description: Find, open, create, save, share and export OpenPaperDesign Papers, including personal Papers outside the project and cloud snapshots in Notion. Use for Home, Paper files, Notion save/open, workspace setup and server controls.
metadata:
version: "0.7.0-preview.23"
---
# Paper
Use the plugin's existing editor and MCP tools. Node.js 22+ is the runtime requirement. The bundled references describe the installed version and work offline; the [repository](https://github.com/gustavonline/openpaperdesign) has installation and development documentation.
## Native plugin app and MCP first
In Codex, open Paper as the plugin's embedded app in the side panel. Call `paper_home` (or `paper_join` for an invitation); these tools carry the native app UI metadata. Returned localhost URLs are internal routing data, not instructions to open a browser tab. Do not navigate the built-in browser, Browser Use, Playwright or an external browser to those URLs for ordinary Paper work. A browser is appropriate for external reference websites, not a substitute Paper app.
Use `openpaperdesign_workspace` MCP tools for the work: `paper_read`, factual `paper_activity`, `paper_add_asset`, revision-checked `paper_save`, and the note/feedback tools. Locally generating JSON or a sourceFile is fine; commit it through `paper_save` rather than direct file writes, raw HTTP or browser automation. MCP saves preserve agent attribution and drive real work/arrival effects. Save useful completed changes, without artificial delays or fabricated activity.
Discover deferred plugin tools before declaring them unavailable. If the host cannot expose the app or MCP, report that limitation instead of silently switching to browser/CLI authoring. Use the standalone browser/CLI route only when the person explicitly chooses it. Read-only file lookup can help diagnose missing tools, but does not prove the native app or agent animations worked.
## Find and open
Home defaults to Personal. Its library selector separates personal Papers from project libraries. A Paper's ⋯ menu reveals its folder. Creating or importing uses the selected library. Projectless Papers belong in native personal storage, never a temporary output folder.
After an update, the desktop host may retain the previous Home view. `paper_home {}` returns Home, MCP and running-server versions; verify those before diagnosing navigation. The current server keeps its shipped editor in memory so pruning its installation does not break open Papers. Open a fresh plugin app view after an update; an existing chat may retain older tools. Use the host’s supported plugin reload or a fresh chat when necessary. Do not restore deleted cache versions, and verify sidebar navigation separately from browser navigation.
- For an existing Paper, especially when its project is unknown or it is absent from the current project, call `paper_home` with `{}` first. It lists the personal library and explicitly remembered projects with Paper IDs, names and workspace IDs. Match the requested Paper before creating anything. Resolve ambiguous matches with the person.
- Call `paper_home` with `action:"open"`, the returned `workspaceId` and `paperId`. It opens that Paper in the native app and returns its internal URL and absolute `workspace`. Then call `paper_open` with that workspace to select it for document tools, followed by `paper_read` with the Paper ID. Home navigation does not switch the agent's active workspace.
- For a known project folder, use `paper_open` with its absolute path and `paper_list`. For personal Papers, use `paper_open` with `{}`. Create with `paper_create` only when a new Paper is wanted. Then call `paper_home` with `action:"open"`, its discovered `workspaceId` and the new `paperId` to show it in the native app. For a default-sized Paper, `paper_home` with `action:"create"`, the selected `workspaceId` and `name` creates and displays it directly; select its returned workspace with `paper_open` before artwork tools.
- For an invitation link, call `paper_join {url}`; pass the whole invitation message as `url` if you have it, or the owner's access code as `code` when the invitation has one and it is not in the message (ask the user; never guess codes). A protected invitation without its code, or with a wrong one, is refused and wrong codes are rate-limited. It opens the shared canvas and selects it for artwork tools. Do not create a local duplicate or add another MCP server. Call `paper_read` with the returned `paperId`. Joined saves use full `paper` JSON and assets use `base64`; filesystem `sourceFile`, private notes, packaging and Notion are unavailable through invitations. Use `paper_open` to return to local work. Never log or save invitation keys or codes in the Paper or repository.
- Project files are `<workspace>/Paper/<id>/`. Personal files use the native application data folder: `~/Library/Application Support/OpenPaperDesign/Paper/` on macOS, `%LOCALAPPDATA%/OpenPaperDesign/Paper/` on Windows, and `$XDG_DATA_HOME/openpaperdesign/Paper/` or `~/.local/share/openpaperdesign/Paper/` on Linux. `PAPER_HOME` overrides the personal root. Home's project pointers stay in that root's `projects/` folder. Do not search unrelated directories or put Papers in the plugin cache.
- The standalone CLI/browser instructions in the repository are an explicitly chosen fallback, not the normal Codex plugin workflow.
## Work on the Paper
`paper_read` returns the revision, source paths, Page summary and note revisions. Read its brief, guide and existing assets before changing them. Preserve IDs, layer order and unrelated content. Read a returned note path when its text is marked truncated.
Use `paper_save` with the read revision and exactly one of `paper` or an in-workspace `sourceFile`. A stale save is refused: read, reconcile the intended edit and retry. `paper_write_note` saves DESIGN.md or CONTEXT.md with its own revision. The context file holds the brief, decisions and next work. Feedback has separate read/save tools and its own revision.
For layer JSON, text, images and coordinates read the [Paper format](references/paper-format.md). For image uploads, feedback, recovery and transport details read the [MCP/HTTP contract](references/http-api.md). Uploading an image does not place it: add the returned asset/path to `paper.assets`, use it in a layer fill, then save. Verify the actual rendered result and reopen the saved Paper in the embedded app. If native visual access is unavailable, report that gap; do not claim a browser inspection verified the app.
Call `paper_activity` before external work such as image generation or research, with a factual status and optional target layer/rectangle. Use a known Page/layer/rectangle only when it is the real work area; omit the location for research with no canvas target. Clear the status when finished or cancelled; completed or failed Paper tool calls clear their temporary activity. Successful artwork saves can briefly reveal added visible layers and label changed layers. These are transient editor effects, never saved artwork. People and agents receive automatic display names and avatars.
For visual composition and design systems use [Design](../paper-design/SKILL.md). For architecture, process, data or infrastructure diagrams use [Diagrams](../paper-diagram/SKILL.md). For text inside either artifact use [Paper Copy](../paper-copy/SKILL.md), which returns to the selected Design/Diagram workflow for layout and rendered review. All use the same editor and files. Keep existing React/HTML, Mermaid, draw.io and Excalidraw sources in their native format when appropriate; see [native routes](references/native-routes.md).
## Share and manage servers
Share exports selected artwork to PNG or HTML, the layer records to JSON, or the complete editable Paper to `.paper.zip`. `paper_package` exports/imports a ZIP within the active workspace; import allocates a new Paper identity. The archive includes referenced images, guides and feedback; history and connection credentials stay local.
For Notion use the existing Share/Home UI or `paper_notion`: status, connect, pages, save, open and disconnect. Read the [Notion workflow](references/notion.md) for authentication, destination selection and cloud conflicts. The UI operates directly; it does not ask the person to prompt an agent for each save. Cloud open creates a local copy. A successful explicit save links its page and enables background file snapshots while the workspace server runs; pause/resume is in the Notion dialog. Status alone never starts saving. Prefer an existing matching Paper/page before creating a duplicate. The person controls account consent and publishing. Never copy connection credentials into a Paper or notes.
Read [sharing](references/sharing.md) before configuring invitations, another agent or external hosting. Share offers Can view / Can edit, an expiry (1 hour, 1 day, 7 days or Never) and Code protection; Copy invitation gives a short message with the link and code. Share → Internet uses optional cloudflared for a temporary HTTPS link, with no account or separate backend. Start public sharing only when the person requests it; never forward the owner server. Install the native CLI only when authorized; ordinary local use does not need it. Clean views receive live saves; conflicting edits are retained for reconciliation. A saved Notion snapshot and interactive preview do not turn Notion into the live editing server.
Home → Shared lists active invitations across known libraries. `paper_home {action:"sharing"}` returns their metadata (including whether a code is required and `expiresAt`, `null` for Never) without keys or codes. Use `action:"stop-sharing"` with `workspaceId`, `paperId`, current server `instance` and optionally `invitationId` to remove one link or all links for that Paper. Labels describe links, not verified people.
`paper_home {}` also reports servers for the known collections. To stop one when requested, use `action:"stop"`, its `workspaceId` and current server `instance`. Stopping closes that server's browser connections and invitations; it preserves files. Use the listed identity, not a process-name search or blanket kill. Reopen with `paper_open` when needed. Home offers the same operation under Sharing.
`paper_home` also supports `rename` with `workspaceId`, `paperId`, `name`; `reveal` to show that Paper's folder; and reversible `trash`. `trash-list` lists recoverable items and `restore` takes the returned `workspaceId` and `trashId`. Trashing stops that Paper's invitations and moves its complete folder into the library's `.trash`. Do not permanently remove files as part of this flow.
Pliki w paczce (13)
- SKILL.md 10 KB
- references/CRAFT-LICENSE.txt 1 KB
- references/DIORAMA-LICENSE.txt 1 KB
- references/UI-SKILLS-LICENSE.txt 1 KB
- references/agent-motion.md 8 KB
- references/design-md.md 1 KB
- references/diagrams.md 7 KB
- references/http-api.md 25 KB
- references/methods.md 1 KB
- references/native-routes.md 1 KB
- references/notion.md 9 KB
- references/paper-format.md 5 KB
- references/sharing.md 15 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · gustavonline/openpaperdesign | 100 | Apache-2.0 |
| piabrota/skills | 100 | MPL-2.0 |
| 0xS4N4TG/kinetograph-ui | 100 | MIT |
| skymanbp/sci-paper | 100 | MIT |
| solankipravin374/visuals-skills | 100 | MIT |
| tpc-pascal/skillsmith | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ed536e295f31 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 96notion
Przeszukuje, czyta, tworzy i aktualizuje strony oraz bazy danych w Notion przez API. - 90notion
Czyta, szuka, zapisuje i aktualizuje treści w przestrzeni Notion przez serwer MCP z listą dozwolonych baz danych. - 100mcp-server-notion
Instaluje serwer MCP Notion do wyszukiwania stron, tworzenia ich i pracy z bazami danych oraz obsługuje jego narzędzia. - 100notion-docs
Zarządza przestrzenią Notion przez MCP: tworzy bazy danych, strony, komentarze i bazy wiedzy, na przykład przy dokumentacji i wiki projektowych. - 100notion
Zapisuje, porządkuje, wyszukuje i syntetyzuje wiedzę w przestrzeni roboczej Notion, w tym zapis treści i research z wewnętrznych stron. - 100notion
Tworzy, wyszukuje i aktualizuje strony i bazy Notion przez API Notion, do dokumentowania pracy, generowania runbooków i automatyzacji bazy wiedzy.