Agent skill

Website Publisher

Manage your author website — auto-publish books on completion, draft blog posts from your projects, render and deploy with one command

MITAuto-check passedWriting & Content

Install Website Publisher

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a claude-code

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

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher --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/Ckokoski/AuthorAgent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/marketing/website-publisher .claude/skills/website-publisher && 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/

Paste into Claude Code

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .claude/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ckokoski/AuthorAgent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/marketing/website-publisher .agents/skills/website-publisher && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .agents/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ckokoski/AuthorAgent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/marketing/website-publisher .cursor/skills/website-publisher && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .cursor/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ckokoski/AuthorAgent.git --path skills/marketing/website-publisher

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ckokoski/AuthorAgent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/marketing/website-publisher .gemini/skills/website-publisher && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .gemini/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ckokoski/AuthorAgent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/marketing/website-publisher .github/skills/website-publisher && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .github/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ckokoski/AuthorAgent --skill website-publisher -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ckokoski/AuthorAgent website-publisher --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ckokoski/AuthorAgent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/marketing/website-publisher .opencode/skills/website-publisher && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "website-publisher" agent skill from https://github.com/Ckokoski/AuthorAgent/tree/main/skills/marketing/website-publisher into .opencode/skills/website-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-publisher", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: website-publisher
GitHub stars: 124
Token cost: ~1.5k tokens
SKILL.md length: 631 words
Files: 1
Skills in repo: 23
Repo updated: Jul 11, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage your author website — auto-publish books on completion, draft blog posts from your projects, render and deploy with one command

Works in 4 steps: Sites — register, link, manage → Auto-add books on project completion → Blog post drafter → …
Tasks that involve Blog and article writing
SKILL.md covers What it does, What this skill does NOT do, Recommended workflow and When to NOT use this skill
Calls netlify, vercel and wrangler

What it does

Website Publisher is an agent skill from Ckokoski/AuthorAgent. Manage your author website — auto-publish books on completion, draft blog posts from your projects, render and deploy with one command

Its SKILL.md is about 1.5k 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 Writing & Content, covering Blog and article writing. The repository describes itself as: The Autonomous AI Writing Agent — a secure, author-focused AI for fiction and nonfiction authors (Planning, Revision, Promotion, and more). The licence is MIT.

When your agent uses it

Tasks that involve Blog and article writing

Example prompts

“/website-publisher”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Sites — register, link, manage
Auto-add books on project completion
Blog post drafter
Render + deploy

What it can do on your machine

Read from SKILL.md and the folder at commit 47e9570. 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:
- netlify
- vercel
- wrangler
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use netlify, vercel and wrangler, 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

Website Publisher loads about 1.5k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 631 words of instructions outside code blocks.

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

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 Ckokoski/AuthorAgent at commit 47e9570, republished under its MIT licence (© Ckokoski). 631 words, ~1,500 tokens.

Download SKILL.mdSave it as .claude/skills/website-publisher/SKILL.md (or your agent's skills folder).

name: website-publisher
description: Manage your author website — auto-publish books on completion, draft blog posts from your projects, render and deploy with one command
author: AuthorAgent
version: 1.0.0
triggers: publish my site, publish my website, update my website, update my site, deploy my website, deploy my site, render my site, render my website, draft a blog…
permissions: file_write, shell_exec

Website Publisher

The management layer on top of AuthorAgent's static-site builder. Generates your site, keeps it in sync with your books, drafts blog posts from your project artifacts, and pushes the rendered site to your host.

This skill is deliberately not a CMS. AuthorAgent is for producing books — shipping a working site is part of that, but maintaining a fully interactive web property isn't. Authors who need comments, forms, ESP integration UIs, or deep analytics should keep using the WordPress / Squarespace / Ghost they already have.

What it does

1. Sites — register, link, manage

A "site" is a deployable unit (one author or one pen name typically). Each site has:

A config (slug, name, tagline, base URL, primary color, social links)
A list of linked projects (when those projects complete, their books auto-publish to the site's books list)
A list of blog posts (drafts + published — drafted by this skill)
A deploy target (Netlify / Vercel / Cloudflare Pages / rsync / manual zip / none)

POST /api/sites           Create a site
GET  /api/sites           List all sites + freshness status
PATCH /api/sites/:id       Update config / linked projects / deploy target
DELETE /api/sites/:id      Remove a site
POST /api/sites/:id/link-project   { projectId }

2. Auto-add books on project completion

When a book-production or novel-pipeline project completes AND the project is linked to one or more sites, the book is auto-added to each site's books list. Idempotent on slug — re-completing the project updates the existing entry.

The author still has to render + deploy explicitly — auto-publishing a brand-new book without review would be too aggressive. The dashboard shows each site's pendingChanges count so the author knows when a render is needed.

3. Blog post drafter

Four post types, each pulling different project artifacts into a focused prompt:

Type	What it produces
`release_announcement`	New-release post: 500-700 words, conversational, with buy-link CTAs
`behind_the_scenes`	Process post: 700-900 words pulling from chapter summaries + user-model + craft-critic flags
`excerpt`	Excerpt-with-tease post: lead-in → verbatim scene → tease → CTA
`teaser`	Coming-soon post: 350-500 words building anticipation without overselling

POST /api/blog-posts/draft
{
  "postType": "behind_the_scenes",
  "projectId": "project-12",
  "siteId": "my-pen-name-site",   // optional — auto-add to site's queue
  "authorAngle": "I want to talk about how I cut chapter 7 four times"
}

Drafts go to pending review. Author edits in the dashboard, then the post is rendered + deployed with the next publish.

4. Render + deploy

POST /api/sites/:id/render    Re-render the static site files
POST /api/sites/:id/deploy    Push the rendered files to the host
POST /api/sites/:id/publish   Combined: render + deploy in one call
GET  /api/site-deploy/doctor  Probe which deploy CLIs are installed

Deploy adapters supported (each shells out to the host's CLI; we don't bundle them):

netlify — netlify deploy --prod (requires netlify-cli)
vercel — vercel deploy --prod (requires vercel)
cloudflare-pages — wrangler pages deploy (requires wrangler)
rsync — push to your own server via SSH (requires rsync)
manual-zip — produces a ZIP file at workspace/exports/website/ that you upload manually via your host's web UI. The safe default. Works on every host without auth setup.
none — render only, no deploy

Tokens are read from process.env at deploy time using a configured tokenEnvVar name. Tokens are never stored in AuthorAgent config.

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

What this skill does NOT do

❌ Not a CMS (no comments, forms, plugins, themes marketplace)
❌ Not an ESP integration (paste your own ConvertKit / MailerLite / Beehiiv embed code into the site config — already supported)
❌ Not an SEO settings panel (we already auto-emit sitemap.xml, RSS feed, and OG tags from your config)
❌ Not multi-tenant (local-first; one author's machine, their sites)
❌ Not a scheduling system (a future cron handler can do this; it's not built in v1)

Recommended workflow

Set up — POST /api/sites once. Configure title, baseUrl, social links, deploy target.
Link your projects — POST /api/sites/:id/link-project for each book project you want featured on the site.
Write your books — when projects complete, books auto-add to the site's books list. Author sees pendingChanges increment.
Draft blog posts as new releases ship — release announcements, behind-the-scenes, excerpts, teasers.
Publish — POST /api/sites/:id/publish renders + deploys in one call. Or render and deploy separately for control.

When to NOT use this skill

If you already have a working WordPress / Squarespace / Ghost / Wix site that fits your workflow, AuthorAgent can still complement it (cover gen, blog post drafts you paste into your CMS, etc.) — but you don't need this skill. Use it when you want a clean static site that auto-syncs with your AuthorAgent projects with minimal hosting cost ($0 on Netlify free tier for most authors).

Files

Just SKILL.md in skills/marketing/website-publisher of Ckokoski/AuthorAgent.

Open the folder on GitHubat commit 47e9570

Compare with similar skills

Website Publisher 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.

Website Publisher compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Website Publisher this skillCkokoski/AuthorAgent	124	—	~1.5k	Automated safety check: Pass	MIT	3 mo ago
Khazix WeChat Article WriterKKKKhazix/khazix-skills	21k	1 repos	~2.9k	Automated safety check: Pass	MIT	9 days ago
Figurevectorize-io/hindsight	48k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
SepiaNanako0129/sepia	3.1k	—	~3.6k	Automated safety check: Pass	MIT	yesterday
Blog Post Draftingluongnv89/claude-howto	42k	—	~2.1k	Automated safety check: Pass	MIT	10 days ago
Notion To Blogwasp-lang/wasp	19k	—	~922	Automated safety check: Pass	MIT	yesterday

Similar skills

Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
21k GitHub starsUsed in 1 repo~2.9k tokens
Writing & ContentAuto-check passed
Figure
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
48k GitHub stars~1.9k tokensUpdated yesterday
Writing & ContentAuto-check passed
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
3.1k GitHub stars~3.6k tokensUpdated yesterday
Writing & ContentAuto-check passed
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
42k GitHub stars~2.1k tokensUpdated 10 days ago
Writing & ContentAuto-check passed
Notion To Blog
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
19k GitHub stars~922 tokensUpdated yesterday
Writing & ContentAuto-check passed
Blog Post
nteract/semiotic
Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.
2.7k GitHub stars~3.4k tokensUpdated today
Writing & ContentAuto-check passed

Questions about Website Publisher

What does Website Publisher do?

Manage your author website — auto-publish books on completion, draft blog posts from your projects, render and deploy with one command. Website Publisher is an agent skill from Ckokoski/AuthorAgent.

When should I use Website Publisher?

Website Publisher fits situations like: tasks that involve Blog and article writing.

How do I install Website Publisher in Claude Code?

Run `npx skills add Ckokoski/AuthorAgent --skill website-publisher -a claude-code`. Or copy the skill folder (skills/marketing/website-publisher in Ckokoski/AuthorAgent) into .claude/skills/website-publisher in your project. Claude Code loads it when a task matches its description.

How do I install Website Publisher in Codex?

Run `npx skills add Ckokoski/AuthorAgent --skill website-publisher -a codex`. Or copy the skill folder (skills/marketing/website-publisher in Ckokoski/AuthorAgent) into .agents/skills/website-publisher in your project. Codex loads it when a task matches its description.

Can I use Website Publisher 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 Ckokoski/AuthorAgent --skill website-publisher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/website-publisher, .gemini/skills/website-publisher, .github/skills/website-publisher and .opencode/skills/website-publisher in your project.

What does Website Publisher need to run?

Going by SKILL.md and its folder, Website Publisher needs the command-line tools its instructions call (netlify, vercel and wrangler).

Does Website Publisher access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Website Publisher 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 Website Publisher use?

Website Publisher 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 Website Publisher use?

About 1.5k tokens (SKILL.md is roughly 6k 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 Website Publisher?

Skills that share tags, products or a category with Website Publisher: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 48k stars), Sepia (Nanako0129/sepia, 3.1k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Website Publisher?

Ckokoski (a GitHub user) maintains it in Ckokoski/AuthorAgent, which has 124 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on July 11, 2026.

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

Install Website Publisher

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Website Publisher

What it does

1. Sites — register, link, manage

2. Auto-add books on project completion

3. Blog post drafter

4. Render + deploy

What this skill does NOT do

Recommended workflow

When to NOT use this skill

Files

Compare with similar skills

Similar skills

More from Ckokoski/AuthorAgent

Related

Questions about Website Publisher