Pageship skills

The Pageship skills teach your agent two jobs: writing a document as a standalone HTML file, and publishing that file with the Pageship CLI. They ship inside the CLI package, and pageship skills install installs them.

The two kinds of skill

The platform skill, pageship, publishes. It runs the CLI, reads each result, signs you in, publishes and revises documents, changes visibility, and lists, downloads and restores what you published. It publishes only when you ask.

The authoring skills write. They never publish. They are:

• pageship-docs, the first step for any document. It settles whether to write HTML or Markdown, picks the document kind and where the file goes, and holds the rules every file follows.
• Kind skills, one for each document kind. A kind skill sets the document’s parts and their order. See the list below.
• Pattern skills, one for each kind of figure or control, such as a chart, a diagram or a table. Any kind can use any pattern. See Patterns.

How your agent uses them

When you ask for a document, your agent:

1. Loads pageship-docs. It settles the format from your request, the file you are editing, a file that is always Markdown such as a README or an ADR, or the format preference in your agent instructions. When none of these settles it, it asks you once, and saves your answer only if you agree. For Markdown, it writes one Markdown file by the content rules and stops there. The steps below are for HTML.
2. Loads the kind skill that fits the request, such as pageship-report. When none fits exactly, it uses the closest one and tells you which.
3. Loads a pattern skill before it writes each figure that has one, such as pageship-chart before a chart.
4. Writes one HTML file, runs the checks, and tells you the file’s path, the structure it added that your source didn’t have, and the open questions.
5. Publishes the file through pageship only if you asked. Otherwise it offers to.

When your agent can start a subagent, as Claude Code, Codex and T3 Code can, it settles the format, the kind and the path itself, then hands the writing and the checks to a subagent. The sources, skill text and check output stay in the subagent, and your conversation gets only the file’s path, the structure it added and the open questions.

Once you ask to publish a document, later changes to it in the same conversation publish as new revisions without asking again. A file that was published before carries a document marker, but the marker is not a request. In a new conversation, the agent offers to publish an edited file and uploads nothing until you agree.

Each new document is private. A request to share a document publishes it privately, then asks whether to make it public.

The authoring skills say only what your source says. A fact the source doesn’t give becomes an open question in the document, never a guess.

Document kinds

Kind	Skill	The reader wants
Report	pageship-report	What was found, what it means and what to do about it
Plan	pageship-plan	Where the work is going, the steps and what is decided
Spec	pageship-spec	A contract for what to build and how to test it
Explainer	pageship-explainer	How something works
Review report	pageship-review-report	Findings on a change or plan, by severity, with a verdict
Decision record	pageship-decision-record	What was decided, the options and the consequences
Slide deck	pageship-slide-deck	Slides to present from a browser

The look of each document comes from your instructions, your project’s design system, an installed design skill, or a plain default. See Recommended skills.

Install the skills

The skills are not yet published on a public skills registry, so install them with the CLI:

pageship skills install

The command copies each skill to ~/.agents/skills/<name>. Codex, Cursor, Copilot, Gemini CLI, OpenCode, Amp, Pi, Goose and Windsurf read that folder. When ~/.claude exists, it also links each skill into ~/.claude/skills for Claude Code. On Windows it copies instead of linking. It installs for your user only, not for one project.

Start a new agent session after installing, so your agent loads the skills.

The skills are MIT licensed. The licence ships with them.

Update the skills

The skills match the CLI version that installed them. After you update the CLI, for example with pageship update, run pageship skills install again. It replaces the folders it wrote and removes the ones the new version no longer ships. It leaves other pageship-* folders alone.

If you edited a skill folder, or the CLI has no record of writing it, the install stops, names the folders and writes nothing. pageship skills install --force replaces them, and you lose your changes.

Check the skills

pageship status reports the skills as missing, current or older than the CLI. Out-of-date skills never block publishing.

status and skills install also list what the CLI looked for and did not find: the recommended skills frontend-design and design-taste-frontend, and Node 20 or later, which the authoring skills’ scripts need. The CLI never installs these.

Remove the skills

There is no remove command yet. Delete the pageship and pageship-* folders in ~/.agents/skills and ~/.claude/skills.

For every flag and result, see skills install in the CLI reference.