Claude skill and plugin
The skill **x3-connect-website** teaches Claude the complete job of connecting a website to X3:
select or create the project, install the SDK or script tag in the site's code, wire the cookie banner,
instrument forms, bookings, WhatsApp/phone/mail clicks, quizzes, CTAs and videos, add server-side lead
and conversion calls, verify that data arrives, and set up goals, conversions and presets. Connecting
ad accounts or operating the dashboard happens only on explicit request, and Claude never changes
anything in an ad account.
The skill contains only the workflow, decisions, safety rules and verification steps. Everything
concrete comes from this documentation at run time – /llms.txt on the API origin (index of all guides),
the guides as markdown and the MCP tools docs_search, docs_read, setup_get_instructions and
setup_get_prompt – so the skill stays correct when X3 changes.
Install
The skill ships in the Claude plugin **x3** of the public marketplace
X3Growth/x3-claude. The plugin also adds the X3 MCP server
(https://api.x3growth.io/mcp, sign-in with OAuth – Claude asks for it when you connect, because every
request needs it).
| Where | How |
|---|---|
| claude.ai, Claude Desktop, Cowork | Customize › Plugins → Add → Add marketplace → X3Growth/x3-claude → install x3 → connect x3 in the plugin's Connectors tab |
| Claude Code | claude plugin marketplace add X3Growth/x3-claude and claude plugin install x3@x3growth, then /mcp to sign in |
| Upload instead | Add › Upload plugin with x3-plugin.zip, or only the skill under Customize › Skills with x3-connect-website.zip – both downloads are on the dashboard card Zu Claude hinzufügen |
| Team / Enterprise | an Owner provides the plugin for everyone (Organization settings › Plugins & skills), installed by default or required |
In the X3 dashboard the card Zu Claude hinzufügen offers all of these paths with one click each.
Without installing anything
If you only added the X3 connector (claude.ai, Claude Code), the same guidance is built into the MCP server:
- Prompt **
connect_website** (argumentssite_url,project,framework) – the skill text with its references, ready to follow. In Claude Code:/mcp__x3__connect_website. - Resources
x3://skills/x3-connect-website/SKILL.mdandx3://skills/x3-connect-website/references/…(Resources).
Or just ask: "Connect my website to X3" – the server instructions point Claude to the prompt.
No X3 account yet? The same prompt and skill resources are on the public docs endpoint
https://api.x3growth.io/mcp/public (no sign-in, no data – Public docs endpoint),
e.g. claude mcp add --scope user --transport http x3-docs https://api.x3growth.io/mcp/public. The plugin's
.mcp.json keeps pointing at /mcp.
What Claude asks you for
- The site URL, which project to use, whether ads run on Meta, Google, LinkedIn or TikTok.
- Confirmation before every write: creating a project, changing tracking settings, goals, presets, conversion definitions, and before committing code.
- Secrets are never handled in chat: you create the proxy key and the secret key in the dashboard and put them into your environment yourself. Claude only writes the variable names.
- A test visit: Claude asks you to open the site with the test parameter and watches the events arrive.
Ad accounts and dashboard (on request only)
Ask explicitly, for example "connect our Meta ad account to project shop". Claude then follows the platform guide (Ads overview), gives you the hosted sign-in link and you complete the login yourself; it can also prepare a client connection link. Conversion uploads are only tested in the platforms' test modes (Test modes).