Manage an existing website through AI chat in Codex and Claude Code.
One website skill coordinates GitHub, SiteOS, Prime, Sanity and Vercel when used
by the website, with guided setup and connection checks. These providers stay independently
installed and updated; their skills and MCP servers are never copied into this package.
Open your website project in your coding assistant and paste:
Set up Website Toolkit from https://github.com/pixel-point/website-toolkit. First connect the official GitHub plugin through the host catalog when using GitHub. Install missing Git/GitHub CLI tools, follow supported browser sign-in and verify local Git access to my existing repository. Handle commands for me; explain only required confirmations or missing invitations. Reuse working credentials and never ask me to create tokens or configure SSH. Read its README and setup instructions, identify whether this session is Codex or Claude Code, and check the available runtime and host CLI. Find my existing website checkout or help me obtain the authorized repository. Install Website Toolkit and missing SiteOS, Prime and Sanity plugins from their own sources, along with the required CLIs. During this full setup, refresh plugins through their official marketplaces and resolve the CLIs' latest stable releases. Verify the actual installed versions and required commands, then follow the updated provider instructions. For a Vercel-hosted website, also install the official Vercel plugin through the host's supported catalog, reusing existing connections. Guide me through confirmation and authorization, and check the Vercel CLI's sign-in separately for local settings export. Preserve my existing configuration. Read the website's project instructions and verify its domain, components and provider context. Guide me through sign-in to Sanity, SiteOS and Prime, select the existing projects, and verify access. If a reload is needed, save progress and give me one resume prompt. Do not publish content, deploy code, create replacement projects or run paid checks during setup. Tell me what is ready and the next step for anything missing. Prepare the website's local settings from its existing hosting provider (Vercel Development settings when applicable), install its dependencies, start its development server and open a verified preview. Keep secrets out of chat and Git, preserve existing settings, and explain missing access or values without substituting Production secrets. Keep a checklist of every required connection. Follow each installed provider's current sign-in flow; for Prime use browser approval, not an emailed Terminal command. Keep its login process running while I approve, then resume. Verify SiteOS CLI and MCP separately against the same existing target. Do not skip Prime or SiteOS because the preview works. If a required connection is pending, say setup is incomplete and guide the next action. After a reload, carry the completed and pending items forward.
If this repository or the website source is private, the assistant needs your authorized Git access to download it. Public plugin distribution does not grant access to website source, CMS data or service accounts. Email/OAuth confirmations and team invitations may need your action; the assistant performs supported setup around those steps.
Then ask naturally:
- “Show me the most useful actions from the latest saved SEO report.”
- “Create a draft landing page from this brief using our existing blocks.”
- “Update this page's headline and SEO description and show me a preview.”
- “Build this section from my design. Reuse our components first, then use Prime if needed.”
Website pages use the current project's layout, Header/Footer, fonts, colors, buttons and components. Prime supplies missing pieces adapted to that design. The toolkit's standalone setup guide is documentation, not a client website template.
Content starts in drafts unless publication is requested. Code changes, CMS publication and live deployment are separate outcomes. Paid checks follow the authorized scope.
After cloning this repository, confirm Node.js 22+ and a host CLI with plugin support.
Use the website checkout, not this toolkit repository, as --project.
node plugins/website-toolkit/scripts/setup.mjs doctor --host codex --project /path/to/website
node plugins/website-toolkit/scripts/setup.mjs update --host codex --project /path/to/website --with-cli --applyUse --host claude for Claude Code. If PATH selects the wrong host version, pass
--host-bin /path/to/the/correct/host. Start a new session or use a supported plugin
reload, then ask the website skill to finish sign-in and resource verification.
Installation does not authenticate you or prove access.
Full setup finishes only after the completion gate: verified project access for each required provider and a real local preview. A pending Prime/SiteOS connection means setup is incomplete, even if the preview already works. The assistant handles the remaining steps; the client completes required confirmations.
The common installer adds four independent plugins: Website Toolkit, SiteOS, Prime and the official Sanity plugin. Website Toolkit contributes its orchestrator and setup helpers. Each provider owns its skills, MCP configuration and authentication flow.
| Plugin | Codex | Claude Code |
|---|---|---|
| Website Toolkit | website-toolkit@website-toolkit |
website-toolkit@website-toolkit |
| SiteOS | siteos@siteos |
siteos@siteos |
| Prime | prime@prime-skills |
prime@prime-skills |
| Sanity | sanity@sanity |
sanity@sanity-agent-toolkit |
Both hosts use Sanity's own sanity-io/agent-toolkit repository. An existing Claude
Code installation from anthropics/claude-plugins-official is also recognized and
reused. Sanity's plugin provides its MCP connection and skills.
Complete the host's Sanity authorization prompt, then verify access to the existing
website project and dataset. No manual MCP server entry or copied token is needed.
The setup conversation starts with the official GitHub plugin through the Codex catalog for GitHub-hosted websites, plus local Git/GitHub CLI preparation as needed. This happens before an authenticated repository download, including the toolkit itself. Plugin authorization, local Git credentials and repository access are checked separately. The assistant performs installation and clone commands; the client confirms account/OS steps. See GitHub setup.
For Vercel-hosted websites, the same setup conversation also installs the official Vercel plugin through the Codex catalog. GitHub and Vercel are host-guided steps outside the four-plugin helper; the assistant must verify each installation and authorization separately. Their updates stay with the owning catalog. See Vercel setup for the current source compatibility and other-host guidance.
The client guide can focus on Codex: install the desktop app, choose a local folder, and paste one setup prompt. The assistant handles authorized repository download, required software, provider plugins, local settings and the preview. GitHub is an account access step, not a client Git tutorial. The toolkit continues to support both hosts; the dedicated client documentation may present only the selected host.
For a Vercel-hosted website, use the official Vercel CLI to retrieve Development settings from the verified existing project into the repository-supported, Git-ignored environment file. Preserve existing local values and never return secrets through chat tools, show or commit them. Plugin authorization and CLI sign-in are separate. Missing access or settings requires an invitation or an approved handoff from the website team. Do not fall back to Production. The assistant must verify a real page in the browser before calling local setup ready. See website files and local preview.
The website owns its context. During setup, the agent can create
.website-toolkit/project.json in the website checkout from the bundled
example. It records the domain,
repository identities, non-secret provider IDs and source-path hints. Unresolved IDs
stay null. The profile is optional; verified context from the current task and provider
configuration is still required before operating on client resources.
Keep a local profile out of Git using the website repository's local exclude file. A team may explicitly track a non-secret profile in its own website repository. Never place a real client profile or credentials in this toolkit's public distribution. See project context.
node plugins/website-toolkit/scripts/setup.mjs update --host codex --project /path/to/website --with-cli --apply
node plugins/website-toolkit/scripts/setup.mjs cli siteos -- --help
node plugins/website-toolkit/scripts/setup.mjs cli prime -- --helpUse --source . only for local development and retain it on local updates.
Client installations use the canonical remote marketplace, even when the helper runs
from a clone. Doctor and mutation commands without --apply do not write.
Setup preserves working installations and reports source conflicts, disabled plugins,
ambiguous scopes and pinned-ref upgrades instead of silently replacing them. Resolve
reported blockers before applying the plan.
Full setup refreshes plugins through their official marketplaces and reads back their
versions before loading current instructions. Managed CLI installation resolves each
provider's current npm latest, checks that it is stable, and verifies the installed
executable's version and help. A matching installation is reused; no upstream release
number is frozen in the setup requirements. Required commands and authenticated reads
are checked separately. Registry failures, explicit pins and disabled plugins remain
visible blockers. Ordinary website tasks do not automatically update all tools.
install fills missing plugins; use update --with-cli --apply for full setup or updates.
The helper reports verificationScope: local_installation_only, setupComplete: false
and providerAccess: not_verified. Even a successful exit, no installation blockers or a
present Prime binding file cannot establish access; the agent must perform the provider reads.
Version 0.2.0 moves Sanity MCP ownership to the official Sanity plugin. Setup upgrades an older Website Toolkit first and verifies the new version before installing Sanity. Reload the host afterwards and complete Sanity authorization if prompted. Existing manually configured Sanity servers are inspected by the skill; setup never silently removes a working connection or rewrites the website's MCP configuration.
Managed CLIs and non-secret checkpoints live under ~/.local/share/website-toolkit;
override with WEBSITE_TOOLKIT_HOME. A separate npm cache avoids global installs,
sudo and shell-profile changes. Authentication stays in provider-owned stores.
Normal upstream plugin updates do not require a new Website Toolkit release.
Automatic helper mutations target macOS/Linux; Windows needs guided host commands until validated. Existing non-Sanity sites can use relevant provider workflows, but the bundled CMS draft workflow is Sanity-specific and does not migrate another CMS.
npm run check
npm run test:hosts
npm run docs:previewNo dependency installation is needed for repository checks. Host acceptance installs
plugins into disposable configuration roots, repeats setup and checks the installed
state. It does not sign in, mutate provider data or change your normal installation.
Use the CMS workflow evaluation cases to check agent
decisions separately. Package/host tests do not prove that a generated section is CMS-editable.
Set WEBSITE_TOOLKIT_CODEX_BIN or WEBSITE_TOOLKIT_CLAUDE_BIN if needed.
Set WEBSITE_TOOLKIT_TEST_SOURCE=remote to verify the published marketplace instead of
the local source. The repository must already be pushed and accessible for that check.
The static guide can be hosted separately. A Git push does not host it or grant client access; a localhost preview is only visible on the machine running it.
Website Toolkit's plugin, skills, setup scripts and documentation are licensed under the MIT License. Copyright (c) 2026 Pixel Point.
A copy of the license is included in the installable plugin directory. Independently installed provider plugins and services retain their own licenses and terms.