MoonPress Chat Setup

What it does

MoonPress Chat Setup takes a WordPress owner through six visible stages: preflight, public-site research, owner questions, connection, configuration, and verification. It creates a cited, field-level plan before any setting changes and keeps the public widget off until the launch gate passes.

The skill is product-specific. It does not become a general WordPress administrator, edit plugin code, or invent a package source, provider choice, consent decision, or business fact. The official product guide lives at moonpresschat.com/setup.

Use it for

• Install or review MoonPress Chat on staging or production.
• Research the public site before configuring the knowledge base.
• Record approved facts, exclusions, consent, handoff, and lead-routing decisions.
• Validate and apply a reviewed configuration.
• Expose every readiness blocker before a separate go-live approval.
• Resume a prior setup from its non-secret local artifacts.

Two setup paths

API path

When the public compatibility endpoint advertises API version 1.0 and the required capabilities, the bundled helper opens WordPress core’s consent screen. The owner signs in and approves in their own browser; the helper stores the temporary Application Password in macOS Keychain and prints only a redacted connection summary.

The skill validates the non-secret configuration first. It applies only the exact fingerprint the owner approves, records rollback evidence, verifies readiness, and treats go-live as a separate approval that revokes the temporary connection.

Guided path

Multisite, plugins that predate the setup API, owners who decline the helper, and Windows or Linux machines use the human-operated wp-admin path. The skill prepares the same plan and verification gate; the human performs authenticated actions and reports only non-secret status.

First run

The skill confirms management authority, canonical origin, staging or production, official plugin installation, compatibility, visibility, backup or reset checkpoint, and rollback path. Production configuration stops until a restorable backup is confirmed.

It then researches public pages and writes cited findings before asking the owner for private decisions the website cannot answer. No public page, owner answer, or plugin default silently becomes an approved production setting.

Inside the skill

The installed package separates its workflow, stage procedures, security contracts, local API bridge, completion gate, and reusable artifact formats.

What it creates

moonpresschat-setup/
├── preflight.md
├── research.md
├── owner-answers.md
├── configuration-plan.md
├── configuration-envelope.json
└── verification.md

The envelope exists only on the API path and contains no secret. None of these files may contain a WordPress password, Application Password, provider key, token, cookie, reset link, or secret-bearing URL.

Safety and boundary

The helper—not the agent transcript—touches the temporary WordPress Application Password. The human enters an AI-provider key in the helper’s hidden terminal prompt or the plugin’s write-only field. The skill may see provider, model, key-present status, and test outcome, never the key.

It never takes over an authenticated browser, calls private admin routes, uses SSH, XML-RPC, SQL, or an unofficial plugin package. A failed public behavior turns visibility off before rollback or troubleshooting.

Setup operator, not a general WordPress copilot.

Ready check

• Authority, origin, environment, official installation, compatibility, and recovery path are explicit.
• Provider and model match the approved plan; the stored key test passes without exposing the key.
• Business facts map to cited or owner-supplied sources; consent, handoff, privacy, and prohibited claims are explicit.
• Supported, unknown, refusal, unrelated-request, consent, handoff, offline, mobile, and desktop tests are recorded.
• Every blocking row passes before the owner is asked separately to approve public go-live.