New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Publish Report

by Amal-David in Amal-David/pagecast

Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous.

MITAuto-check passedDocuments & Office

Install Publish Report

skills CLI
$ npx skills add Amal-David/pagecast --skill publish-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Amal-David/pagecast publish-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Amal-David/pagecast.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/publish-report .claude/skills/publish-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
publish-report
GitHub stars
191
Token cost
~2.7k tokens
SKILL.md length
1,407 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous.

  • Works in 4 steps: Write a pagecast-goal.md in the working… → Run npx pagecast goal publish… → After each meaningful step, rewrite… → …
  • S publish request is ambiguous
  • SKILL.md covers Consent and intent, When to offer, The question to ask and How to publish, plus 3 more sections
  • Calls npx and npm

What it does

Publish Report is an agent skill from Amal-David/pagecast. Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous. Use when a report, plan, doc, dashboard, analysis, or static build output should be shared from Claude Code, especially when the user says publish, share, make a public link, or send this. If the user explicitly says Pagecast, publish with Pagecast.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Markdown. It works with Cloudflare Pages. The repository describes itself as: Publish HTML, Markdown and static mini apps to shareable Cloudflare Pages URLs from the terminal or coding agents. The licence is MIT.

When your agent uses it

  • S publish request is ambiguous
  • Static build output should be shared from Claude Code
  • Especially when the user says publish
  • Make a public link

Example prompts

  • “/publish-report”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Write a pagecast-goal.md in the working dir with the goal, status, a
  2. Run npx pagecast goal publish "/pagecast-goal.md" --json and give
  3. After each meaningful step, rewrite pagecast-goal.md and re-run the
  4. When the goal is met, do a final update; optionally npx pagecast goal stop.

What it can do on your machine

Read from SKILL.md and the folder at commit aa48964. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Publish Report loads about 2.7k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 1,407 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Amal-David/pagecast at commit aa48964, republished under its MIT licence (© Amal-David). 1,407 words, ~2,718 tokens.

Download SKILL.mdSave it as .claude/skills/publish-report/SKILL.md (or your agent's skills folder).
name
publish-report
description
Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous. Use when a report, plan, doc, dashboard, analysis, or static build output should be shared from Claude Code, especially when the user says publish, share, make a public link, or send this. If the user explicitly says Pagecast, publish with Pagecast.
version
0.7.0

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.

  • “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.

Claude Code Artifacts are also a valid publishing path. Do not disable or block Artifacts. When the user explicitly asks for a Claude Artifact, claude.ai artifact, or org-private artifact, use the Artifact flow. When the user explicitly asks for Pagecast or a Cloudflare Pages link, use Pagecast. When the user only says "publish", "share", "make a link", or similar, ask them which publishing path they want before doing anything.

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 static web project that was just built, with a generated entry file such as dist/index.html, build/index.html, out/index.html, or public/index.html.
  • Any time the user says "share", "publish", "make a link for", or "send" a doc.
  • A PostToolUse hint fired saying an HTML/Markdown file was created — treat that as a cue to offer.

If the user says only "publish this" or "make this shareable" for a local report/doc/dashboard, ask them to choose between Claude Code Artifacts and Pagecast. The built-in Claude Code Artifact publisher is useful for claude.ai private/org pages. Pagecast is useful for external Cloudflare Pages URLs that can be renamed, re-synced, revoked, password-protected, or expired.

The only files to skip (don't offer): scratch/draft notes the user is clearly keeping private, source code, config files, secrets, and repo-meta files (README, CHANGELOG, CONTRIBUTING, LICENSE, AGENTS.md, CLAUDE.md, TODO/tasks), or anything under node_modules/dist build internals. When it is borderline, offer — the user can just say no.

Ask at most once per file. If the user declines or ignores the offer, drop it and don't re-ask for that file. Never nag across multiple turns.

The question to ask

When the user has not specified a publishing path, ask:

"How do you want to publish this?

  1. Claude Code Artifact — private/org claude.ai page that can update in place.
  2. Pagecast — Cloudflare Pages link you can share outside Claude, rename, re-sync, revoke, password-protect, or expire.
  3. Don't publish."

Accept the number or the name. Only proceed after an explicit choice. An explicit request for Pagecast already selects Pagecast and provides publishing consent. If they choose Pagecast, run the Pagecast CLI below. If they choose Claude Code Artifact, use the Claude Artifact publishing flow and do not run Pagecast. Publishing may make content reachable outside the current chat, especially with Pagecast — never publish without confirmation.

How to publish

Run the headless CLI with the absolute path and --json:

sh
npx pagecast publish "/absolute/path/to/file.md" --json

(HTML and Markdown both work — Markdown is rendered to a clean page. If pagecast is installed globally/in the project, pagecast publish "<path>" --json is the same.)

New links are unlisted capability URLs: a memorable prefix plus 128 bits of opaque entropy. Anyone with the URL can view it; unlisted does not mean private. The user can rename a link, add password protection, or make a short, shareable "drop" link from the npx pagecast app. Existing word-only links remain valid.

Managed links live in one user-level Home at ~/.pagecast/home/, under /p/<slug>/. The same item in the same agent context updates the existing URL; a new item or context creates a new URL. Pagecast stores only a local hash of the agent context identifier.

Publish options

Add any of these to a publish command:

  • --expires <7d|12h|never> — edge-enforced link expiry (default 30d). The page returns 410 once expired; --expires never keeps it live until revoked. The result JSON reports expiresAt (or none when never).
  • --label "<name>" — set the page's display name in the Pagecast app.
  • --context-id "<id>" — explicitly select the local agent context.
  • --new-link — force a fresh URL.
  • --update "<url|slug|token>" — update a known publication.
  • --non-interactive — never open browser authentication; return a structured authentication-required result instead.
sh
npx pagecast publish "/absolute/path/to/report.html" --expires 7d --label "Launch report" --json
Password handling

Never ask the user to provide a page password in chat and never place a secret in an agent-generated command or tool argument. Publish the page first, then tell the user to open the local npx pagecast app and set password protection there. This keeps the credential out of the model and tool transcript.

Publishing a plan (e.g. after plan mode): the plan lives in your context, not a file yet. If the user wants it shared, first write the plan markdown to a file (e.g. ./plan.md), then publish that path. Don't overwrite an existing file the user cares about — pick a clear new name.

Show full SKILL.md (566 more words)Show less

Live goal / progress page

When you're working toward a /goal (you'll see the goal condition in your context) and the work will span many turns / a long autonomous run, the user often can't see what's happening. Proactively offer once:

"Want me to publish a live progress page for this goal? You'll get a public link you can open anytime to see status and what's done."

On an explicit yes:

  1. Write a pagecast-goal.md in the working dir with the goal, status, a done/next checklist, and a one-line "latest", e.g.:
    markdown
    # <short goal title>

**Goal:** <the goal condition, in your own words>
**Status:** In progress · updated <time>
**Progress:** 3 / 8 steps

## Done
- [x] <step>

## Next
- [ ] <step>

## Latest
<one line: what you just did / any blocker>
  2. Run npx pagecast goal publish "<abs path>/pagecast-goal.md" --json and give the user the returned url.
  3. After each meaningful step, rewrite pagecast-goal.md and re-run the same npx pagecast goal publish … --json — it guarantees the dedicated goal URL and keeps goal lifecycle separate from normal context upserts.
  4. When the goal is met, do a final update; optionally npx pagecast goal stop.

There is one goal page per workspace. If a command reports recreated: true, the old link was gone and the URL changed — tell the user the new URL.

For static web projects that should get a new shareable /p/<slug>/ link, build first and publish the generated entry file:

sh
npm run build
npx pagecast publish "/absolute/path/to/dist/index.html" --json

If the user asks to deploy or update an entire static site/project, deploy the built folder directly to a named Cloudflare Pages project:

sh
npx pagecast publish site "/absolute/path/to/dist" --project "project-name" --branch main --json

--branch is optional and defaults to main, so this also works:

sh
npx pagecast pages deploy "/absolute/path/to/dist" --project "project-name" --json

Use this instead of raw Wrangler commands like npx wrangler pages deploy. Direct site deploys replace the target Pages project contents, so do not guess the --project; use the user's named project or ask for it. Direct deploys do not change Pagecast's managed /p/... target, so use a separate project unless replacing that managed site is intentional.

Parse the JSON on stdout:

  • Success → { "ok": true, "action": "created" | "updated", "publicationToken": "...", "contextMatched": true | false, "url": "https://<home>.pages.dev/p/<slug>/", ... }
    • Give the user the url, say whether Pagecast created or updated it, offer to drop it into a PR/Slack message, and mention they can rename the URL, re-sync, or revoke it from npx pagecast.
  • Not signed in → { "ok": false, "statusCode": 401, ... }
    • Interactive publishing normally starts Wrangler's browser authorization and resumes automatically. This result is expected only for CI, --non-interactive, rejection, or timeout; relay it without sending the user to Settings.
  • Multiple accounts → { "ok": false, "statusCode": 409, ... }
    • Open npx pagecast, choose the Home account in the main onboarding canvas, then retry. Settings remains available for later account switching.
  • Any other error → relay error concisely and offer to retry.

Cloudflare Pages commands

Use these lower-level commands when the user explicitly asks about Cloudflare setup, status, project listing, or direct Pages deployment:

sh
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

If the user does not specify a branch, omit --branch; Pagecast deploys to main.

Notes

  • Always pass an absolute path (resolve relative paths against the cwd first).
  • The first interactive publish starts Wrangler login, creates the Home, and resumes automatically.
  • Use npx pagecast publish site or npx pagecast pages deploy for direct static-folder deploys to a named Pages project.
  • Use npx pagecast for source-folder build settings, URL renaming, re-sync, and revoke controls.
  • Re-running publish for the same item and agent context updates the same URL. Use --new-link only when the user asks for another URL.

© Amal-David, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugin/skills/publish-report of Amal-David/pagecast.

Open the folder on GitHubat commit aa48964

Compare with similar skills

Publish Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Publish Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Publish Report this skillAmal-David/pagecast191—~2.7kAutomated safety check: PassMIT
Markdown Article FormatterJimLiu/baoyu-skills27k6 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
Crosspostingwasp-lang/wasp19k—~1.1kAutomated safety check: PassMIT
Gzh Designisjiamu/gzh-design-skill4k—~2.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    27k GitHub starsUsed in 6 repos~3.5k tokens
    Documents & OfficeAuto-check passed

  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes

  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed

  • Crossposting

    wasp-lang/wasp

    Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.

    19k GitHub stars~1.1k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…

    4k GitHub stars~2.2k tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed

  • Review The Docs

    supabase/supabase

    Official

    Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).

    111k GitHub stars~4.6k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from Amal-David/pagecast

  • Publish Report

    Amal-David/pagecast

    Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs.

    191 GitHub stars~2.4k tokensUpdated 20 days ago
    Auto-check passed

Works with

Categories

Questions about Publish Report

What does Publish Report do?

Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous. Publish Report is an agent skill from Amal-David/pagecast. Help publish local HTML, Markdown, or built static web projects by asking whether to use Claude Code Artifacts or Pagecast/Cloudflare Pages when the user's publish request is ambiguous.

When should I use Publish Report?

Publish Report fits situations like: S publish request is ambiguous; static build output should be shared from Claude Code; especially when the user says publish; make a public link.

How do I install Publish Report in Claude Code?

Run `npx skills add Amal-David/pagecast --skill publish-report -a claude-code`. Or copy the skill folder (plugin/skills/publish-report in Amal-David/pagecast) into .claude/skills/publish-report in your project. Claude Code loads it when a task matches its description.

How do I install Publish Report in Codex?

Run `npx skills add Amal-David/pagecast --skill publish-report -a codex`. Or copy the skill folder (plugin/skills/publish-report in Amal-David/pagecast) into .agents/skills/publish-report in your project. Codex loads it when a task matches its description.

Can I use Publish Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Amal-David/pagecast --skill publish-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-report, .gemini/skills/publish-report, .github/skills/publish-report and .opencode/skills/publish-report in your project.

What does Publish Report need to run?

Going by SKILL.md and its folder, Publish Report needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.

Does Publish Report access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Publish Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Publish Report use?

Publish Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Publish Report use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Publish Report?

Skills that share tags, products or a category with Publish Report: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Crossposting (wasp-lang/wasp, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Publish Report?

Amal-David (a GitHub user) maintains it in Amal-David/pagecast, which has 191 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 21, 2026.

Source: Amal-David/pagecast on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.