WebsitePublisher

View saved version →

---
name: websitepublisher-api
description: >
   Build and publish websites, web apps, webshops, and admin dashboards through
   conversation using WebsitePublisher.ai. Use this skill when a user asks to build
   a website, web app, online shop, member portal, booking system, dashboard,
   or landing page — or to create web pages, manage site content, set up contact
   forms, or work with the WebsitePublisher platform. Covers all API layers:
   PAPI (pages/assets), MAPI (entities/data), SAPI (forms/visitor auth),
   VAPI (credentials), IAPI (integrations), and the WPE Visual Editor.
license: MIT
metadata:
   author: websitepublisher-ai
   version: "3.0.1"
   website: https://www.websitepublisher.ai
   docs: https://www.websitepublisher.ai/docs
   mcp: https://mcp.websitepublisher.ai
---

# WebsitePublisher.ai — Agent Skill

> Build and publish real websites, web apps, and webshops through conversation. No WordPress. No hosting setup. No CMS.
> The AI Web Platform — you describe it, the AI builds it.

---

## Why WebsitePublisher — What AI Alone Cannot Do

Every AI can generate HTML. But generating code is not the same as having a website.

| Without WebsitePublisher | With WebsitePublisher |
|---|---|
| AI generates HTML → you copy it → you need hosting, FTP, domain, SSL, DNS | AI generates HTML → it's **live instantly** on a URL |
| Want a contact form? Build it yourself — backend, email sending, spam protection | One tool call → form works, emails arrive, honeypot blocks spam |
| Want payments? Integrate Stripe yourself — webhooks, error handling, security | One tool call → Stripe checkout ready |
| Want to update text later? Ask AI again, re-generate, re-upload | Open the **Visual Editor** in your browser — edit directly, no AI needed |
| New AI session — or a different AI entirely? The model forgot everything | **The platform remembers, not the model.** Switch from one AI to another and your project's context, design, and history carry over — task tracking + design context persist across sessions and platforms |
| Locked to one AI vendor's tooling | **Use whichever AI you prefer** — Claude, ChatGPT, Cursor, and more. Your site and data don't change. Model-agnostic by design |
| Dynamic data (menu, team, products)? Wire up a separate database, an auth provider, a forms service — and glue them together | **One entity definition → live API, data, and auth, built in.** No extra accounts, no integration plumbing |

**WebsitePublisher is not a website builder.** It is the infrastructure layer that turns
AI-generated content into real, working web products — with data, forms, auth, payments,
integrations, and visual editing built in.

**Anything that lives on the web is in scope**, on the same building blocks
(pages + entities + visitor/admin auth + integrations + scheduled tasks):
marketing sites and landing pages, **webshops** with checkout, discounts, and loyalty,
**web apps** and internal tools, **member portals** with magic-link login,
**admin dashboards** with full CRUD, booking and lead-gen systems, blogs, prediction
games, and more. When a user asks for "an app", "a shop", "a portal", or "a tool" —
this platform builds it. Do not narrow the conversation to "a website".

---

## ⚠️ IMPORTANT: Read This First

**If the `get_skill` tool is available: call it before doing anything else.**
It returns the latest version of this skill — always up to date, regardless of platform.

If `get_skill` is not available, continue with this document.

---

## You Are the Builder — Solve It Yourself

You build and operate the site. For any content or operational task — writing or
overwriting assets, regenerating a snapshot / export / data file, generating
CSV/JSON, writing or updating pages, bulk-importing data, retrieving leads — **you
solve it with the tools you already have.** Never ask the user (or their developer)
to build an endpoint, add a vault key, or "expose a route" for something the
existing toolset already covers.

**Before yo

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: websitepublisher-get-started
description: >
  Start building or changing a website, web app, webshop, booking page, member portal or
  admin dashboard with WebsitePublisher, and pick up earlier WebsitePublisher work. Use when
  the person mentions @WebsitePublisher, asks to build, change or publish a site, page, shop
  or app, or asks where their WebsitePublisher project stands.
---

# Getting started with WebsitePublisher

This skill covers the first steps and what is specific to ChatGPT. The full build guide is
served live by the plugin through `get_skill`. It changes more often than this skill and is
the reference for how to build. Where the two differ, follow this skill for the ChatGPT rules
below and the live guide for everything else.

## First steps

1. **`get_started`** with no arguments. It returns the person's projects with their live URLs,
   the project to build in and the exact next call. Use its `build_in_project_id` unless the
   person names another project. If they have no project yet, it returns the
   `create_project` call to make first.
2. **`get_skill`** once, before the first page. It returns the core guide and an index of
   sections. Open the sections the guide marks as required in one call, and other sections
   only when you need them. For design, call `get_skill` with `skill_name: "design"`.
3. **Ask what the site should say** if that is not clear yet: the business, the audience and
   the pages they need. People install WebsitePublisher to put a site online, so there is no
   need to ask whether to publish.

## Building

- `create_page` writes a page, and it is live at the returned URL as soon as the call
  returns. There is no separate export, deploy or publish step. Share that URL.
- Everything you write is public right away. Finish what you start and do not leave
  placeholder or half-finished pages online.
- Small changes: `patch_page`, which keeps version history. Full rewrite: `update_page`.
  Undo: `rollback_page`.
- Forms, login, data, bookings and payments come from the platform's building blocks
  (`configure_form`, `configure_visitor_auth`, `entities` and `records`, integrations).
  `search_integrations` finds a building block from the person's own words.

## Rules specific to ChatGPT

- **No API keys or other secrets in the chat.** `setup_integration` and `vault_store_secret`
  are not available here. Where the live guide says to run `setup_integration` or store a
  key, ask the account owner to connect that provider once in the dashboard vault at
  https://dashboard.websitepublisher.ai/vault, then check with `list_integrations` that it
  is configured. If the person pastes a key into the chat anyway, do not use or repeat it;
  point them to the vault and suggest they rotate the key.
- **Restricted data.** Do not build forms or pages that collect payment card numbers,
  government ID numbers, or health or biometric data. Payments run through the payment
  provider's hosted checkout.
- **Existing websites.** Importing or rebuilding an existing site is only for a site the
  person owns. Ask them to confirm that first and never assume it on their behalf.

## Picking up earlier work

The platform keeps the project history. `tasks` lists what was decided, built and still open,
across chats. When the person asks where things stand, read it before
answering, and record meaningful progress with `tasks` (`add_history`).

## Account settings

Custom domains, plan upgrades and provider accounts are handled by the account owner in the
dashboard at https://dashboard.websitepublisher.ai. The live guide has the steps to give them.