How do I install the Openpress Deploy skill?

Run npx skillmds@latest add quan0715/openpress-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openpress Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openpress Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openpress Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openpress Deploy?

quan0715 (@quan0715) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openpress Deploy by quan0715 — Agent Skill

Name: Openpress Deploy
Author: quan0715

Openpress Deploy

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.

quan0715 ccb396c 2 files · 4.6 KB Updated Sep 17, 2026

File contents

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 openpress/settings.json under the "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 the public URL and, when included, the 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.). OpenPress does not currently expose an authored external-PDF URL field, so do not invent one in openpress/settings.json; report the separate URL in the delivery handoff.

Deploy Commands

Dry run:

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

Publish after explicit confirmation:

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

Remove --no-pdf only when the user explicitly includes the PDF in the confirmed publication target.

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.

---name: openpress-deploydescription: 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 Deployopen-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 `openpress/settings.json` under the `"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 the public URL and, when included, the 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 RuleNever publish without a clear confirmation that names the target project.Good confirmation shape:```txtThis will publish the current open-press build to Cloudflare Pages project `<projectName>` from `<deploy.source>`.Do you want me to deploy now?```## PreflightBefore real deploy, run the commands that prove the output is ready:```bashnpm run build # validates + renders dist-react/```Also scan public-facing source for unfinished markers:```bashrg "\\[TODO:|\\[FIX:|\\[DRAFT:" "press/*/chapters" press/design.md```### PDF Size LimitCloudflare 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:```bashnpm 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:```bashnpm run openpress:pdfdu -sh .deploy/**/*.pdf 2>/dev/null```If the PDF is over 25 MB and the user still wants it publicly hosted, recommenda separate host (Cloudflare R2, S3, etc.). OpenPress does not currently exposean authored external-PDF URL field, so do not invent one in`openpress/settings.json`; report the separate URL in the delivery handoff.## Deploy CommandsDry run:```bashnpm run openpress:deploy:dry-run -- --no-pdf```Publish after explicit confirmation:```bashnpm run openpress:deploy -- --confirm --no-pdf```Remove `--no-pdf` only when the user explicitly includes the PDF in theconfirmed publication target.## 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.

Frequently asked questions