publish-report
Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked — and whenever the user asks to publish, share, make a public link for, or send a local report/doc/dashboard/web project from terminal, Codex CLI, or Codex desktop.
npx skills add Amal-David/pagecast --skill publish-report --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Publish with Pagecast Pagecast turns a local **HTML or Markdown** file (a report, plan, doc, or dashboard) into a shareable public URL in the user's Pagecast Home. Execute an explicit Pagecast request immediately; offer once when publishing would be useful but the user did not request it. ## Consent and intent - “Publish this as a Pagecast”, “Pagecast this”, or equivalent is sufficient consent. Run the publish command immediately and return the URL; do not ask again. - A proactive suggestion still asks once before publishing. - If the user asks only for the command, provide the command and do not run it. ## When to offer **Default to offering.** Whenever you produce an `.html`/`.htm` or `.md`/`.markdown` file that a person could reasonably share, proactively offer to publish it — once, right after you finish making it. Do **not** wait to be asked, and do **not** stay silent because you are unsure whether it is "worth it." If it could be shared, offer. This includes: - A report you generated — test/coverage/Lighthouse/Playwright output, a data dashboard, an analysis, a "here's what I built/found" summary. - A written plan, proposal, design doc, spec, release notes, or doc. - A sta
- Consent and intent
- When to offer
- The proactive question
- How to publish
- Publish options
- Password handling
- Live goal / progress page
- Static web projects
- Reading the result
- Cloudflare Pages commands
- Codex usage notes
npx pagecast publish "/absolute/path/to/file.md" --json npx pagecast publish "/absolute/path/to/report.html" --expires 7d --label "Launch report" --json npm run build npx pagecast publish "/absolute/path/to/dist/index.html" --json npx pagecast publish site "/absolute/path/to/dist" --project "project-name" --branch main --json npx pagecast pages deploy "/absolute/path/to/dist" --project "project-name" --json npx pagecast pages setup --project "project-name" --json npx pagecast pages status --json npx pagecast pages projects list --json npx pagecast pages deploy "/absolute/path/to/dist" --project "project-name" --branch main --json
What does the publish-report skill do?
Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked — and whenever the user asks to publish, share, make a public link for, or send a local report/doc/dashboard/web project from terminal, Codex CLI, or Codex desktop.
How do I install it?
Run `npx skills add Amal-David/pagecast --skill publish-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Amal-David/pagecast, a repository with 184 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.