Files

T

Corey HainesandClaude Fable 5 88de9fd15d feat: publish Ploy as a live Skill Partner (Website) (#577 )

* feat: publish Ploy as a live Skill Partner (Website)

Ploy's payment cleared (agreement 2026-08, accepted 2026-09-03), so the
staged entry goes live. The integration guide was finalized against
docs.ploy.ai (llms.txt + CLI/auth/webhooks docs) rather than waiting on
the onboarding packet — the maintainer holds the pen either way.

- partners.json: ploy active:true
- README + REGISTRY Verified Partners table: regenerated via sync-partners.mjs
- REGISTRY Tool Index: add the ◆ ploy capability-matrix row (Website)
- tools/integrations/ploy.md: disclosed ◆ guide — CLI, WebMCP, API tokens,
  webhooks, PloyDB/Ploybooks, and how it fits the website-build/seo skills
- .partners-pending/ploy.md draft removed (superseded, was gitignored)

Logo ships separately in the marketingskills-website repo (/logos/ploy.png).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VTdwoFxvAL9yNhkuH1EdpS

* review: fix dangling skill references in ploy guide

website-build-* and ai-integration live in other skill libraries, not this
repo — the same defect class 5339aad fixed. Reference only skills that
exist here; add schema to the SEO pairing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VTdwoFxvAL9yNhkuH1EdpS

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-09-03 10:07:17 -07:00

3.9 KiB

Raw Permalink Blame History

Ploy

◆ Verified Partner integration. Ploy sponsors Marketing Skills. This integration is disclosed and vetted for fit; it does not change what any skill recommends. It's listed here alongside the neutral options for the same job — use it when it's the right fit, not because it's a partner. See Verified Partners.

AI marketing platform built around a website builder: one system for building the site, optimizing it (SEO/AEO, CRO), identifying and engaging visitors, and generating ad creative with attribution. An in-app agent builds pages, writes copy, analyzes performance, and manages deploys through conversation.

Capabilities

Integration	Available	Notes
API	✓	Workspace-scoped API tokens for CI/headless use; inbound webhooks trigger Ploybooks; OpenAPI spec published at `/.well-known/api-catalog`
MCP	✓	WebMCP — exposes selected website actions to compatible AI assistants while preserving the site's existing interface, permissions, and application logic
CLI	✓	Standalone binary (macOS/Linux) — workspaces, sites, domains, publishing, PloyDB, Ploybooks, variables/secrets, Code Sync — docs.ploy.ai/cli
SDK	–	Agent-first instead: the CLI ships agent skills + site inspection for coding agents working in a checked-out site

What it does

Site builder — pages, sections, components on a design system; publish, deploy history, rollback, custom domains. Can serve alongside an existing site via routing rules.
Analytics & visitors — traffic tracking, visitor identification, GA4 and Google Search Console connections.
PloyDB — structured content database; CMS migration imports existing CMS content and builds pages from the imported tables.
Ploybooks — scheduled/triggered marketing playbooks; fire them from external systems via webhooks.
WebMCP — expose chosen site actions (forms, booking, etc.) to AI assistants via the Model Context Protocol without rebuilding the interface.
Integrations — GitHub, Figma, Google Analytics, Search Console, Notion, Slack, HubSpot, and more.

Authentication

Type: sign-in via Ploy for interactive use; workspace-scoped API token for CI and headless environments (docs). Store tokens in an environment variable / secret manager — never in the repo.

Setup (agent-driven via CLI)

Install the CLI — macOS/Linux binary (install docs).
Authenticate — interactive sign-in, or set a workspace API token for remote agents & CI (non-interactive commands, explicit IDs, safe secret handling).
Select context — workspace and site.
Build or migrate — create pages via the agent/builder, or import existing CMS content into PloyDB and generate pages from it.
Publish — push production, connect a custom domain, verify the deploy; roll back if needed.
Optionally enable WebMCP — choose which site actions to expose to AI assistants.

How it fits the skills

Ploy is one way to implement the site itself — an alternative to a Webflow/Framer or hand-coded stack. The strategy layer (what pages, what copy, what structure) still comes from site-architecture, copywriting, and cro.
Its SEO/AEO surface pairs with seo-audit, ai-seo, and schema; judge its analytics, visitor-identification, and attribution output with analytics / attribution discipline.

3.9 KiB Raw Permalink Blame History Unescape Escape