moonpresschat-skill · skill guide · for humans

moonpresschat-setup

v0.4.0

Safely install, research, plan, connect, configure, and verify MoonPress Chat without exposing credentials to the agent.

For: WordPress site owners and developersActs on: MoonPress Chat setuppublic alpha

The problem

A useful chatbot needs grounded business knowledge, approved wording, consent, escalation rules, and a testable launch decision.

Chat-based setup often tempts people to paste WordPress passwords or provider keys into the AI conversation.

This skill separates human authorization from agent work and stores only non-secret, reviewable setup artifacts.

Public alpha

Version 0.4.0 ships both paths. The API path is the default — MoonPress Chat's stable setup API plus the bundled macOS credential helper — and the human-guided wp-admin path remains the fallback for multisite, older plugins, or unsupported credential backends.

What works in 0.4.0

Cold-start preflightready

Checks official installation, versions, environment, backup, rollback, and visibility.

Public-site researchready

Produces cited facts, unknowns, and confirmation questions.

Owner decisionsready

Records knowledge, consent, voice, handoff, and launch authority.

Configuration planready

Maps every proposed field to a source and verification method.

API-driven setupready

Validate, approve, apply, verify, rollback, and go-live through the shipped setup API, with credentials held by the local helper in the macOS Keychain.

Guided WordPress setupready

Fallback path: walks the human through MoonPress Chat admin without observing the authenticated browser.

Windows/Linux credential backendblocked

The helper is macOS-only in this release; other platforms route to the guided path.

Inside the skill

The public package keeps the executable workflow, security contracts, helper, templates, and verification gate together.

moonpresschat-setup/

SKILL.mdWorkflow router and security boundary

actions/Preflight, research, questions, connect, configure, and verify

contracts/API, guided fallback, fields, installation, rollback, and security

helper/moonpresschat-setup-helper.mjsKeychain-backed local credential bridge

templates/Non-secret setup artifact formats

qa/verification-checklist.mdPrelaunch and postlaunch release gate

How it flows

Preflight

Confirm authority, official installation, compatibility, and recovery.

Research

Read public pages and cite the facts.

Questions

Collect only owner decisions the site cannot answer.

Connect

Temporary credential via the bundled helper; secrets stay out of the transcript.

Configure

Validate, approve, and apply one non-secret envelope through the setup API.

Verify

Expose passes, failures, and blockers before launch.

Say this to your agent

“Set up MoonPress Chat on my WordPress site

“Research my site before configuring MoonPress Chat

“Help me plan the MoonPress Chat knowledge base

“Connect this WordPress site to the MoonPress Chat setup flow

“Review whether MoonPress Chat is ready to go live

“Resume my MoonPress Chat setup

Safety boundaries

No WordPress passwords, Application Passwords, provider keys, or tokens in chat — the helper holds the temporary credential in the macOS Keychain.

No browser automation, SSH, XML-RPC, direct database writes, or internal admin routes; API calls stay inside quipbot/v1/setup.

No arbitrary plugin package, no production change without backup and explicit approval, and go-live is a separate approval that revokes the connection.