Documentation

Agent Skills

Add Pagr publishing instructions to agent workspaces from Skills.sh, Smithery, or the Pagr CLI.

Docs

Start

Getting started

Build

CLI API MCP Skills ChatGPT App

Operate

Troubleshooting

Quick actions

View on Skills.shBrowse the official Pagr skill on Skills.sh.
View on SmitheryBrowse the official Pagr skill on Smithery.
Copy Skills.sh installInstall the Pagr skill with the Skills CLI.
Copy Smithery installInstall the Pagr skill from Smithery.

Badges and listings

skills.sh smithery badge

The official Pagr skill is published on Skills.sh and Smithery as getpagr/pagr.

Install the skill

Install the Pagr skill from Skills.sh:

npx -y skills add https://github.com/getpagr/skills --skill pagr

Install the Pagr skill from Smithery.ai:

npx -y skills add https://smithery.ai/skills/getpagr/pagr

Both registries install the same Pagr skill. It gives agents Pagr-specific instructions for publishing HTML artifacts. It does not replace authentication; the CLI still needs pagr login, pagr login --key pagr_..., or PAGR_API_KEY when the agent uses authenticated workflows.

You can also generate workspace-specific skill files from the Pagr CLI:

npm install -g @getpagr/cli
pagr init

pagr init writes SKILL.md, .agents/skills/pagr/SKILL.md, and, when Claude Code is selected, .claude/skills/pagr/SKILL.md. It can also write .codex/instructions.md, .cursor/rules/pagr.mdc, and a remote MCP entry in .claude/settings.json depending on the wizard choices.

What the skill does

The Pagr skill tells agents to:

  • publish local HTML files with pagr upload <file>
  • return the URL printed by the CLI instead of inventing a URL
  • update pages when the file contains <meta name="pagr-id"> or <meta name="pagr-slug">
  • use PAGR_API_KEY in CI and shared automation instead of writing local config
  • surface exact CLI or API errors when upload, update, list, or delete calls fail

The skill is best for generated HTML reports, dashboards, planning documents, prototype pages, and other artifacts that should be returned as a public https://uc.pagr.link/<slug> URL.

Install from Smithery

Smithery’s Pagr skill page provides a downloadable SKILL.md and the same agent instructions shown in the Skills.sh listing.

npx -y skills add https://smithery.ai/skills/getpagr/pagr

Use the Smithery skill when you prefer Smithery’s skill directory and download flow. Use the MCP docs separately when an agent should call Pagr through MCP tools.

Use in agent workflows

A good agent instruction is:

Create the final HTML artifact locally, publish it with Pagr, and return the public URL. If @getpagr/cli is not installed, install it with npm install -g @getpagr/cli. Use PAGR_API_KEY from the environment or run pagr login if interactive authentication is available. Use pagr upload <file> --title "<title>" and return the exact URL printed by the command.

For agents without MCP tools, ask them to use the CLI workflow described by the skill. For MCP-enabled agents, use the separate MCP integration and ask them to call upload_file for new pages or update_file_by_id when a stored pagr-id is available.

Security notes

Treat Pagr API keys as secrets. Do not paste real keys into prompts, public docs, READMEs, or generated HTML. Prefer environment variables, MCP client secret fields, or local ~/.pagr/config.json.

Published Pagr pages are public by default. Use password protection on Pro or Team plans when the page should require a passphrase.