Install
$ agentstack add skill-quan0715-open-press-openpress-deploy ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.jsonunder 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
openpressowns generic CLI usage, non-deploy validation, local review, and the source/generated boundary.openpress-create-pagesowns page artifact content and visual readiness.openpress-create-slideowns 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 `` from ``.
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.mdwhen creating or repairing Cloudflare Pages config, project setup, Wrangler auth expectations, or UI deploy-button behavior.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: quan0715
- Source: quan0715/open-press
- License: MIT
- Homepage: https://open-press.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.