Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

openpress-deploy

Étoiles10

Forks1

Mis à jour5 juin 2026 à 05:51

Use when preparing, configuring, checking, staging, or publishing an open-press document to public hosting, especially Cloudflare Pages, deploy setup, deploy buttons, deploy status, public release checks, or safe deployment workflow.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

quan0715

quan0715/open-press

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	openpress-deploy
description	Use when preparing, configuring, checking, staging, or publishing an open-press document to public hosting, especially Cloudflare Pages, deploy setup, deploy buttons, deploy status, public release checks, or safe deployment workflow.

open-press Deploy

open-press deploy owns the public-release gate. Use it only when the user asks to configure, inspect, dry-run, or publish an open-press document.

Responsibilities

Inspect deploy config in the workspace package.json under the "openpress.deploy" field.
Check target adapter, staging source, project name, and confirmation settings.
Run deploy preflight and dry runs.
Keep secrets out of source files.
Require explicit confirmation before publishing.
Report public URL and PDF URL after successful deploy.

Boundaries

openpress owns generic CLI usage, non-deploy validation, local review, and the source/generated boundary.
openpress-create-pages owns page artifact content and visual readiness.
openpress-create-slide owns slide deck content and visual readiness.
This skill owns public target confirmation and deploy execution.

Public Deploy Rule

Never publish without a clear confirmation that names the target project.

Good confirmation shape:

This will publish the current open-press build to Cloudflare Pages project `<projectName>` from `<deploy.source>`.
Do you want me to deploy now?

Preflight

Before real deploy, run the commands that prove the output is ready:

npm run build              # validates + renders dist-react/

Also scan public-facing source for unfinished markers:

rg "\\[TODO:|\\[FIX:|\\[DRAFT:" "press/*/chapters" press/design.md

PDF Size Limit

Cloudflare Pages rejects any single file larger than 25 MB. A multi-press or image-heavy PDF commonly exceeds this limit.

Unless the user explicitly asks to publish the PDF, deploy without it:

npm run openpress:deploy -- --confirm --no-pdf

--no-pdf skips PDF generation and excludes it from the deploy source entirely.

If the user wants to check the PDF size first:

npm run openpress:pdf
du -sh .deploy/**/*.pdf 2>/dev/null

If the PDF is over 25 MB and the user still wants it publicly hosted, recommend a separate host (Cloudflare R2, S3, etc.) and set deploymentInfo.pdf to the external URL in the workspace config.

Deploy Commands

Dry run:

npm run openpress:deploy:dry-run

Publish after explicit confirmation:

npm run openpress:deploy -- --confirm

When To Read References

Read references/cloudflare-pages.md when creating or repairing Cloudflare Pages config, project setup, Wrangler auth expectations, or UI deploy-button behavior.

Plus depuis ce dépôt

même dépôt

openpress-create-pages

quan0715/open-press

Use when the user wants to create, draft, scaffold, or add a page-based OpenPress artifact such as a report, proposal, whitepaper, paper, book, teaching note, handbook, or long-form document. This skill owns fresh workspace bootstrap for pages, adding a pages Press to an existing Workspace, page-based Press Tree generation, first-pass theme intake, page components, hierarchy, prose structure, captions, factual boundaries, learner-facing document rules, and portable language skill routing.

2026-07-0210

openpress

quan0715/open-press

Use when operating an open-press workspace through CLI commands, discovering project status, validating/exporting/rendering/PDF/Word output, inspecting structure/issues, searching or safely replacing source text, routing pending @openpress-comment marker work to openpress-apply-comments, routing framework upgrade work to openpress-upgrade, or deciding which open-press skill owns a task.

2026-07-0210

openpress-apply-comments

quan0715/open-press

Use when applying, resolving, clearing, or inspecting pending open-press @openpress-comment markers, including requests like /apply-comments, apply comment, resolve comments, read comments and modify the document, or remove resolved comment markers.

2026-06-2410

openpress-create-slide

quan0715/open-press

Use when the user wants to create, draft, scaffold, edit, reorder, add, or revise an OpenPress slide deck or presentation from topic selection through outline, narrative, visual style, production, and tuning; create or revise slide-style templates; use the slide CLI to add/remove/reorder/skip template-backed slides; define slide theme tokens; convert data-prop layouts to frame/object JSX; or reference a specific slide, template, opener, or column page. This skill owns stable slide delivery workflow, slide Press creation, slide editing, slide-style template authoring, core Object API composition, theme token setup, Tailwind semantic slide styling, deck narrative, slide density, assets, motion discipline, and verification.

2026-06-2410

chinese-ai-writing-polish

quan0715/open-press

Use when producing or editing Traditional Chinese professional content, especially business, product, proposal, report, pitch, website, documentation, or marketing copy that may contain AI-like sentence patterns, empty contrast phrasing, vague transformation slogans, exaggerated claims, or repetitive polished-but-thin language.

2026-06-2110

openpress-diagram-drawing

quan0715/open-press

Use when drawing or revising open-press document diagrams, especially concept diagrams, comparison figures, process states, data-structure nodes, pointers, arrows, before/after states, linked lists, stacks, queues, trees, or memory relationship figures.

2026-06-2110

name	openpress-deploy
description	Use when preparing, configuring, checking, staging, or publishing an open-press document to public hosting, especially Cloudflare Pages, deploy setup, deploy buttons, deploy status, public release checks, or safe deployment workflow.

open-press Deploy

open-press deploy owns the public-release gate. Use it only when the user asks to configure, inspect, dry-run, or publish an open-press document.

Responsibilities

Inspect deploy config in the workspace package.json under the "openpress.deploy" field.
Check target adapter, staging source, project name, and confirmation settings.
Run deploy preflight and dry runs.
Keep secrets out of source files.
Require explicit confirmation before publishing.
Report public URL and PDF URL after successful deploy.

Boundaries

openpress owns generic CLI usage, non-deploy validation, local review, and the source/generated boundary.
openpress-create-pages owns page artifact content and visual readiness.
openpress-create-slide owns slide deck content and visual readiness.
This skill owns public target confirmation and deploy execution.

Public Deploy Rule

Never publish without a clear confirmation that names the target project.

Good confirmation shape:

This will publish the current open-press build to Cloudflare Pages project `<projectName>` from `<deploy.source>`.
Do you want me to deploy now?

Preflight

Before real deploy, run the commands that prove the output is ready:

npm run build              # validates + renders dist-react/

Also scan public-facing source for unfinished markers:

rg "\\[TODO:|\\[FIX:|\\[DRAFT:" "press/*/chapters" press/design.md

PDF Size Limit

Cloudflare Pages rejects any single file larger than 25 MB. A multi-press or image-heavy PDF commonly exceeds this limit.

Unless the user explicitly asks to publish the PDF, deploy without it:

npm run openpress:deploy -- --confirm --no-pdf

--no-pdf skips PDF generation and excludes it from the deploy source entirely.

If the user wants to check the PDF size first:

npm run openpress:pdf
du -sh .deploy/**/*.pdf 2>/dev/null

If the PDF is over 25 MB and the user still wants it publicly hosted, recommend a separate host (Cloudflare R2, S3, etc.) and set deploymentInfo.pdf to the external URL in the workspace config.

Deploy Commands

Dry run:

npm run openpress:deploy:dry-run

Publish after explicit confirmation:

npm run openpress:deploy -- --confirm

When To Read References

Read references/cloudflare-pages.md when creating or repairing Cloudflare Pages config, project setup, Wrangler auth expectations, or UI deploy-button behavior.