Compare commits

...
17 Commits
Author SHA1 Message Date
Corey HainesandClaude Fable 5 5b2c000776 feat: ai-seo 2.5.0 — ChatGPT 5.6 format-volatility guidance (#579)
* feat: add format-volatility guidance to ai-seo (ChatGPT 5.6 shift)

Listicle/comparison citations fell 50%/32% post-5.6 while site:/official
retrieval surged — the skill's format advice and stale citation-share
table needed the correction. Adds LinkedIn AEO guide data, ChatGPT
fan-out extraction diagnostic, and non-deterministic measurement rigor.

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

* chore: release 2.11.1 (ai-seo 2.5.0)

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

* fix: label the per-platform table's unmeasured cells as unreported, not stable

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

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-04 21:48:02 -07:00
Corey HainesandClaude Fable 5 5cd4a7eae3 fix: ploy category → canonical grid name (#578)
The site maps partners.json category directly to the sponsorship-page
category grid (CATEGORIES[].name in partner-program.ts), where the
canonical slot is "Website & landing page builders" — "Website" would
never match. Display surfaces are unaffected (they use categoryShort;
sync confirms README/REGISTRY unchanged).


Claude-Session: https://claude.ai/code/session_01VTdwoFxvAL9yNhkuH1EdpS

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-03 10:18:25 -07:00
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
Corey HainesandClaude Fable 5 4fbe11fd0a feat: stage Ploy as pending Skill Partner in the Website category (#576)
Ploy (ploy.ai) completed Skill Partner checkout (agreement 2026-08 accepted
2026-09-03; $500/mo). Payment has cleared but the onboarding packet (logo,
blurb, docs) hasn't arrived yet, so the entry is staged inactive — the
Converly #571 pattern in reverse order.

- partners.json: ploy entry, category Website (their slot per Corey),
  active:false so no surface publishes yet
- draft integration guide staged locally in .partners-pending/ploy.md
  (gitignored) with TODOs to fill from the onboarding packet

To go live once the packet arrives: finalize the guide into
tools/integrations/ploy.md, flip active:true, run
node scripts/sync-partners.mjs, add the ◆ rows + Website category to
tools/REGISTRY.md.


Claude-Session: https://claude.ai/code/session_01VTdwoFxvAL9yNhkuH1EdpS

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-03 09:33:01 -07:00
Corey HainesandClaude Fable 5 d4ff28a9c8 feat: onboard Converly as a paying Skill Partner (#574)
* feat: onboard Converly as a paying Skill Partner

Aaron Beashel completed payment and the onboarding form, so Converly goes
live — the inverse of the #571 unpublish.

- partners.json: active:true
- README + REGISTRY Verified Partners table: regenerated via sync-partners.mjs
- REGISTRY Tool Index: restore the ◆ converly capability-matrix row
- tools/integrations/converly.md: restored from .partners-pending/

The disclosure header ("Converly sponsors Marketing Skills") is now accurate.
Site picks this up via the live partners.json fetch once merged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* feat: set Converly logoUrl to self-hosted placement asset

Points the live-fetch path at the logo grabbed from converly.io and
self-hosted on the site (/logos/converly.png), so the Skill Partner card
shows the C mark instead of the fallback monogram.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-01 16:00:25 -07:00
Corey HainesandClaude Fable 5 e55de886fe fix: unpublish Converly until payment clears (#571)
Converly was used as the example partner to build out the partner pipeline
and went live across the README, registry, and site before any invoice was
paid. No company should appear as a paying partner before payment clears.

- partners.json: active:false (record kept for history)
- README + tools/REGISTRY.md: regenerated via sync — now "no active partners"
- tools/integrations/converly.md: moved to gitignored .partners-pending/

Restore on payment: flip active:true, restore the guide from .partners-pending/,
run node scripts/sync-partners.mjs.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-28 15:23:46 -07:00
Corey Haines b1aaa3619e Merge pull request #569 from coreyhaines31/docs/partner-program-rules
docs: canonical partner-program rules & boundaries (tools/PARTNERS.md)
2026-08-26 17:05:41 -07:00
Corey HainesandClaude Fable 5 2b92a8f924 docs: tools/PARTNERS.md — canonical partner-program rules & boundaries
Consolidates the previously-scattered rules into one governance doc: the
one principle (sponsorship funds work, never recommendations), the three
tool-entry kinds (neutral integration / ◆ Verified Partner / house tool),
what sponsorship buys and never buys, tiers, the file-level disclosure
format, editorial control + the integrity rubric, the precise category-
exclusivity definition (slot not recommendations), the full partner
lifecycle, and the tools/integrations spec. Nothing new invented —
consolidated from the site FAQs, REGISTRY, CONTRIBUTING, and the
agreement. Cross-linked from REGISTRY, CONTRIBUTING, and the README
Partners section.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-26 15:42:10 -07:00
Corey Haines 0d12b95752 Merge pull request #568 from coreyhaines31/docs/contribution-integrity-rubric
docs: contribution integrity rubric (gate on content, not contributor)
2026-08-26 15:36:59 -07:00
Corey HainesandClaude Fable 5 e90dd3ba6c docs: contribution integrity rubric — gate on content, not contributor
Codifies the editorial policy: anyone (tool makers, partners included) may
contribute to any skill; the bar is whether the content makes agents *aware*
of a tool without manufacturing a recommendation. Adds the rubric (options
not one answer, at the point of relevance, no forced endorsement, facts over
framing, disclose self-interest, the swap test, maintainer final review) to
CONTRIBUTING.md, a checklist item, and a pointer from the tools registry.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-26 15:35:39 -07:00
Corey Haines becd60ee9d Merge pull request #565 from coreyhaines31/feature/partner-converly
feat: verified-partner integrations (Converly, first partner)
2026-08-24 12:30:34 -07:00
Corey HainesandClaude Fable 5 b6fc21ef94 feat: partners.json single source + sync script
partners.json is now the canonical partner registry. scripts/sync-partners.mjs
regenerates the README Partners section and the tools/REGISTRY.md Verified
Partners table (between PARTNERS:START/END markers) from it — run after editing
partners.json, or 'node scripts/sync-partners.mjs --check' in CI. The
marketing-skills.com site reads the same partners.json directly (raw GitHub), so
one edit updates every surface. Deactivate a lapsed partner with active:false.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-24 12:19:23 -07:00
Corey HainesandClaude Fable 5 997ab1a351 refactor: partners are verified integrations, not a separate skill class
Architecture change per the partner UX: a partner is a vetted, disclosed
tool integration in the existing registry — surfaced through the tool
routing core skills already use — not a nested skills/partners/ skill
(which wouldn't install and duplicated the tools layer).

- tools/integrations/converly.md: partner-grade integration doc with a
  disclosure header (◆ Verified Partner; additive, never biasing)
- tools/REGISTRY.md: new Verified Partners section (what the ◆ marker
  means + doesn't) + Converly row marked ◆ in the index
- README: Partners section now points at the registry/integration
- removed skills/partners/ draft (skill + convention doc) — the
  convention now lives in the registry's Verified Partners section

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-24 10:30:38 -07:00
Corey HainesandClaude Fable 5 cf7a1f741f wip: Converly partner skill + partners convention + README placement (DRAFT — needs Converly docs review, do not merge/publish yet)
- skills/partners/converly/SKILL.md: disclosed (sponsored:true, partner:Converly),
  scoped to defer generic tracking/attribution to core skills; CLI/MCP setup
  steps marked TODO pending developers.converly.io + converly.io/mcp
- skills/partners/README.md: partner-skill convention (disclosure, scoping,
  editorial control, not counted as core skills)
- README.md: featured Partners section (the placement), outside SKILLS markers

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-24 09:56:09 -07:00
Corey Haines f557c546c8 Merge pull request #563 from coreyhaines31/development
ci: activate auto-release workflow on main
2026-08-23 15:08:07 -07:00
Corey Haines 8d8098d023 Merge pull request #562 from coreyhaines31/feature/auto-release-workflow
ci: auto-tag + GitHub Release on version bump
2026-08-23 15:04:15 -07:00
Corey HainesandClaude Opus 4.8 eb7f72faa3 ci: auto-tag + GitHub Release on version bump
Adds .github/workflows/release.yml — on push to main, if the plugin.json
version changed and no v<version> tag exists, it creates the tag + a
GitHub Release with notes pulled from the matching VERSIONS.md block.
Idempotent (skips if already tagged). Closes the manual-release gap that
left v2.10.1–v2.11.0 untagged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-08-23 15:03:24 -07:00
16 changed files with 555 additions and 21 deletions
+1 -1
View File
@@ -6,7 +6,7 @@
},
"metadata": {
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, and growth",
"version": "2.11.0",
"version": "2.11.1",
"repository": "https://github.com/coreyhaines31/marketingskills"
},
"plugins": [
+1 -1
View File
@@ -1,7 +1,7 @@
{
"name": "marketing-skills",
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth",
"version": "2.11.0",
"version": "2.11.1",
"author": {
"name": "Corey Haines"
},
+71
View File
@@ -0,0 +1,71 @@
name: Release on version bump
# Auto-creates a git tag + GitHub Release whenever the repo version in
# .claude-plugin/plugin.json changes on main. Release notes are pulled from
# the matching `### x.y.z` block in VERSIONS.md. Idempotent: if the tag
# already exists, it does nothing (safe to re-run / backfill manually).
on:
push:
branches: [main]
paths:
- ".claude-plugin/plugin.json"
- "VERSIONS.md"
permissions:
contents: write
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Determine version and whether it's already tagged
id: ver
run: |
VERSION=$(python3 -c "import json;print(json.load(open('.claude-plugin/plugin.json'))['version'])")
echo "version=$VERSION" >> "$GITHUB_OUTPUT"
if git rev-parse -q --verify "refs/tags/v$VERSION" >/dev/null; then
echo "exists=true" >> "$GITHUB_OUTPUT"
echo "v$VERSION already tagged — nothing to do."
else
echo "exists=false" >> "$GITHUB_OUTPUT"
fi
- name: Extract release notes + title from VERSIONS.md
if: steps.ver.outputs.exists == 'false'
run: |
python3 - "${{ steps.ver.outputs.version }}" <<'PY'
import re, sys
v = sys.argv[1]
text = open("VERSIONS.md").read()
parts = re.split(r"\n### (\d+\.\d+\.\d+) \([^)]*\)\n", text)
blocks = {}
for i in range(1, len(parts), 2):
blocks[parts[i]] = parts[i + 1].split("\n### ")[0].strip()
body = blocks.get(v, f"Release {v}")
open("release-notes.md", "w").write(body + "\n")
# title = first non-empty line, stripped of markdown, truncated
first = next((l for l in body.splitlines() if l.strip()), "")
first = re.sub(r"[*`_]|^- |\[([^\]]+)\]\([^)]+\)", r"\1", first).strip()
title = f"v{v} — {first}"
if len(title) > 100:
title = title[:99].rstrip() + "…"
open("release-title.txt", "w").write(title)
print("Title:", title)
PY
- name: Create tag + release
if: steps.ver.outputs.exists == 'false'
env:
GH_TOKEN: ${{ github.token }}
run: |
VERSION="${{ steps.ver.outputs.version }}"
gh release create "v$VERSION" \
--target "${{ github.sha }}" \
--title "$(cat release-title.txt)" \
--notes-file release-notes.md
echo "Created release v$VERSION"
+1
View File
@@ -28,3 +28,4 @@ skills-lock.json
*~
.idea/
.vscode/
.partners-pending/
+14
View File
@@ -65,6 +65,19 @@ skills/your-skill-name/
3. Keep changes focused and minimal
4. Update the version in metadata if making significant changes
## Mentioning Tools (the integrity rubric)
This library is open source and contributions are welcome from **anyone — including the makers of tools, and paid partners.** We gate on the *content*, not the contributor. A contribution that names a tool (yours or anyone's) is fine as long as it makes an agent **aware** of the right option at the moment it's relevant, without manufacturing a recommendation. Concretely:
- **Options, not one answer.** Present a tool alongside the real alternatives for the same job (including the free / DIY path), so the agent picks on fit — not because only one is named.
- **At the point of relevance.** Surface a tool where an agent genuinely needs it (e.g. the implementation step), not injected into unrelated sections.
- **No forced endorsement.** No "best," "recommended," or "use X instead." Describe what each option does and when it fits.
- **Facts over framing.** Recipes, code, capabilities, and honest tradeoffs (cost, effort, lead time) — verifiable, not marketing copy.
- **Disclose self-interest.** If you're the tool's maker or a partner, say so. Partner tools are marked ◆ in [`tools/REGISTRY.md`](tools/REGISTRY.md#verified-partners); house tools (built by the maintainer) carry stricter disclosure.
- **The swap test.** If you swapped your tool for a competitor, the section should still read as fair. If removing it breaks the guidance, it was shilling — rework it.
The maintainer holds final editorial control and may edit or cut anything for neutrality and accuracy. Core skills stay editorially independent: sponsorship and contributions add content, they never buy a recommendation. Full program rules and boundaries — the tool taxonomy, what sponsorship buys and never buys, disclosure, and the partner lifecycle — are in [`tools/PARTNERS.md`](tools/PARTNERS.md).
## Submitting Your Contribution
1. Fork the repository
@@ -83,6 +96,7 @@ skills/your-skill-name/
- [ ] Instructions are clear and actionable
- [ ] No sensitive data or credentials
- [ ] Follows existing skill patterns in the repo
- [ ] Any tool mentions follow the [integrity rubric](#mentioning-tools-the-integrity-rubric) — options not one answer, disclosed, passes the swap test
## Questions?
+12
View File
@@ -10,6 +10,18 @@ New to the terminal and coding agents? Check out the companion guide [Coding for
Run into a problem or have a question? [Open an issue](https://github.com/coreyhaines31/marketingskills/issues) — we're happy to help.
## Partners
The library is free and MIT-licensed. [Verified Partners](tools/REGISTRY.md#verified-partners) fund the work — vetted, disclosed tool integrations, listed alongside the neutral options and never influencing what the core skills recommend. The full rules and boundaries are in [tools/PARTNERS.md](tools/PARTNERS.md). [Become a partner →](https://marketing-skills.com/sponsorship)
<!-- PARTNERS:START -->
> ◆ **[Converly](https://converly.io?ref=marketingskills)** — *Conversion tracking / attribution.* Server-side conversion tracking that fires when someone submits a form, books a meeting, or starts a chat — passing click IDs and identifiers for Enhanced Conversions (Google) and high EMQ match rates (Meta), across 100+ tools. CLI + MCP so your agent sets it up in minutes. → [Integration guide](tools/integrations/converly.md)
> ◆ **[Ploy](https://ploy.ai?ref=marketingskills)** — *AI website & growth platform.* AI marketing platform built around a Webflow-grade website builder — site optimization, SEO/AEO, visitor identification, and ad creative in one, with WebMCP to expose site actions to AI assistants. → [Integration guide](tools/integrations/ploy.md)
<!-- PARTNERS:END -->
<!-- The Partners block above is generated from partners.json — run `node scripts/sync-partners.mjs` after editing it. -->
## What are Skills?
Skills are markdown files that give AI agents specialized knowledge and workflows for specific tasks. When you add these to your project, your agent can recognize when you're working on a marketing task and apply the right frameworks and best practices.
+6 -1
View File
@@ -6,7 +6,7 @@ Current versions of all skills. Agents can compare against local versions to che
|-------|---------|--------------|
| ab-testing | 2.0.0 | 2026-05-05 |
| ad-creative | 2.8.2 | 2026-08-23 |
| ai-seo | 2.4.0 | 2026-08-21 |
| ai-seo | 2.5.0 | 2026-09-04 |
| analytics | 2.0.1 | 2026-07-22 |
| aso | 2.0.1 | 2026-08-19 |
| attribution | 1.1.0 | 2026-07-23 |
@@ -57,6 +57,11 @@ Current versions of all skills. Agents can compare against local versions to che
## Recent Changes
### 2.11.1 (2026-09-04)
- **ai-seo** (2.4.0 → 2.5.0): new `references/format-volatility.md` — the citation-*format* volatility axis, companion to agent-readiness.md's citation-*source* volatility. Anchored on the **ChatGPT 5.6 format shift** (Aug 2026, Peec AI data via Tomek Rudzki and Lily Ray): fan-out queries dropped the "vs / comparison / top / best / reviews" modifiers while `site:` and "official" searches surged, and citations by page type fell −50.5% for listicles (15.77% → 7.80%) and −32.1% for comparison pages (9.08% → 6.17%) — the two formats companies scaled for GEO, demoted in one release. Covers what changes (stop justifying scaled listicle/comparison production with "wins AI citations"; owned "official" pages rising as the citable class) and what doesn't (comparisons still convert humans and still earn citations on Google AIO / Gemini / Perplexity — a per-platform format table replaces one-size-fits-all advice). Adds **LinkedIn as a citation surface** from LinkedIn's own AEO guide (via Chris Long, platform-reported: most-cited outlet for professional searches; Articles out-cite Posts ~60/40; first words of a post become the URL slug — front-load the target phrase), a **DIY ChatGPT fan-out extraction** diagnostic (DevTools → network payload → literal background queries; explicitly warned against as a mass-generation content-spam input), and a **measurement-rigor** section (AI answers are non-deterministic: 3–5 runs per query, mention *rate* with sample size, rates-over-time not run-vs-run, technical/comprehension/trust cause split; framing credited to Initial Commit's AEO audit skill, Josh Pigford). SKILL.md: Content Types section rewritten around the volatility (stale ~33%-comparison-share table retired to context), ChatGPT fan-out + extraction pointer added to the fan-out section, LinkedIn added to the Presence pillar, non-determinism rule added to DIY monitoring, new triggers ('do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' 'AI citation format shift'). New eval (id 10) covers the scaled-comparison-roadmap prompt that must get the 5.6 pushback plus the one-run-anecdote measurement correction.
### 2.11.0 (2026-08-23)
- Added the **`events`** skill (1.0.0) — event marketing across all four roles: **hosting** (webinar → workshop → dinner → meetup → virtual summit → user conference, governed by "the topic is the targeting" and recurring-beats-one-off), **sponsoring/exhibiting**, **speaking**, and **attending** (target list → pre-booked meetings → the side-event play). Built on the universal arc — **20% event, 80% before-and-after** — with the 24–48h tiered follow-up, capture-context-not-just-contact discipline, an event-as-recording-studio content arc (transcripts compound in AI answers → ai-seo, public-relations), and a three-tier measurement model (vanity / real / decisive) with multi-touch honesty via attribution. Four references: **webinar-funnel.md** (the flagship funnel, closes #485), **sponsorship-roi.md** (ICP-overlap + cost-per-qualified-meeting math, side-event play, tiered follow-up), **speaking.md** (CFP craft, talk storyboard, the recording as the real audience), and **event-portfolio-strategy.md** (which events to invest in: in-person-necessity by segment, the 80/20 of selection, size↔ROI inverse, the owned/trade-show/community frame + economics — distilled from Corey's *Founding Marketing* ch.9). Seven evals. New skill = repo y release; total skills: 50. Closes #485.
+31
View File
@@ -0,0 +1,31 @@
{
"_comment": "Canonical partner registry — single source of truth. Fill one object per partner from their onboarding packet, then run `node scripts/sync-partners.mjs` to regenerate the README Partners section and the Verified Partners table in tools/REGISTRY.md. The marketing-skills.com site fetches this file directly (raw GitHub). Deactivate a lapsed partner with active:false (keeps history, removes it everywhere).",
"partners": [
{
"id": "converly",
"name": "Converly",
"url": "https://converly.io",
"category": "Marketing analytics & attribution",
"categoryShort": "Conversion tracking / attribution",
"tier": "skill-partner",
"tagline": "Server-side conversion tracking",
"blurb": "Server-side conversion tracking that fires when someone submits a form, books a meeting, or starts a chat — passing click IDs and identifiers for Enhanced Conversions (Google) and high EMQ match rates (Meta), across 100+ tools. CLI + MCP so your agent sets it up in minutes.",
"logoUrl": "/logos/converly.png",
"integration": "tools/integrations/converly.md",
"active": true
},
{
"id": "ploy",
"name": "Ploy",
"url": "https://ploy.ai",
"category": "Website & landing page builders",
"categoryShort": "AI website & growth platform",
"tier": "skill-partner",
"tagline": "Turns your website into a growth engine",
"blurb": "AI marketing platform built around a Webflow-grade website builder — site optimization, SEO/AEO, visitor identification, and ad creative in one, with WebMCP to expose site actions to AI assistants.",
"logoUrl": "/logos/ploy.png",
"integration": "tools/integrations/ploy.md",
"active": true
}
]
}
+77
View File
@@ -0,0 +1,77 @@
#!/usr/bin/env node
// Regenerate every partner surface from the canonical partners.json.
//
// node scripts/sync-partners.mjs # write the generated blocks
// node scripts/sync-partners.mjs --check # fail if anything is out of date (CI)
//
// Owns the marked blocks in:
// - README.md → the Partners section list
// - tools/REGISTRY.md → the Verified Partners table
// Everything outside the <!-- PARTNERS:START --> / <!-- PARTNERS:END --> markers
// is left untouched. The marketing-skills.com site reads partners.json directly.
import { readFileSync, writeFileSync } from "node:fs";
import { resolve, dirname } from "node:path";
import { fileURLToPath } from "node:url";
const HERE = dirname(fileURLToPath(import.meta.url));
const ROOT = resolve(HERE, "..");
const REPO = "https://github.com/coreyhaines31/marketingskills/blob/main";
const REF = "?ref=marketingskills";
const START = "<!-- PARTNERS:START -->";
const END = "<!-- PARTNERS:END -->";
const check = process.argv.includes("--check");
const { partners } = JSON.parse(readFileSync(resolve(ROOT, "partners.json"), "utf8"));
const active = partners.filter((p) => p.active);
const readmeBlock = active.length
? active
.map(
(p) =>
`> ◆ **[${p.name}](${p.url}${REF})** — *${p.categoryShort || p.category}.* ${p.blurb} → [Integration guide](${p.integration})`
)
.join("\n\n")
: "_No active partners yet. [Become a partner →](https://marketing-skills.com/sponsorship)_";
const registryBlock = [
"| Partner | Category | Guide |",
"|---------|----------|-------|",
...active.map(
(p) =>
`| ◆ ${p.name} | ${p.categoryShort || p.category} | [${p.integration.split("/").pop()}](${p.integration.replace(/^tools\//, "")}) |`
),
].join("\n");
const targets = [
{ file: "README.md", block: readmeBlock },
{ file: "tools/REGISTRY.md", block: registryBlock },
];
let stale = false;
for (const { file, block } of targets) {
const path = resolve(ROOT, file);
const src = readFileSync(path, "utf8");
const i = src.indexOf(START);
const j = src.indexOf(END);
if (i === -1 || j === -1 || j < i) {
console.error(`✗ ${file}: missing ${START} / ${END} markers`);
process.exitCode = 1;
continue;
}
const next = src.slice(0, i + START.length) + "\n" + block + "\n" + src.slice(j);
if (next === src) {
console.log(`✓ ${file} up to date`);
continue;
}
if (check) {
console.error(`✗ ${file} is out of date — run: node scripts/sync-partners.mjs`);
stale = true;
continue;
}
writeFileSync(path, next);
console.log(`↻ ${file} updated (${active.length} partner${active.length === 1 ? "" : "s"})`);
}
if (check && stale) process.exitCode = 1;
+10 -18
View File
@@ -1,8 +1,8 @@
---
name: ai-seo
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' or 'WebMCP.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema."
metadata:
version: 2.4.0
version: 2.5.0
---
# AI SEO
@@ -105,6 +105,8 @@ Google's own example: a user asking "how to fix lawns" triggers fan-out queries
**Action**: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them.
ChatGPT fans out too — and you can extract its *literal* background queries for your niche via DevTools (method in [references/format-volatility.md](references/format-volatility.md)). Post-5.6, ChatGPT's fan-outs shifted away from "best/vs/top" modifiers toward `site:` and "official" searches — use the extraction to see where your category's fan-outs stand today.
---
## AI Visibility Audit
@@ -253,6 +255,7 @@ AI systems don't just cite your website — they cite where you appear.
- Wikipedia mentions (7.8% of all ChatGPT citations)
- Reddit discussions (volatile: ~1.8% of ChatGPT citations historically, but nearly wiped from ChatGPT by Aug 2026 retrieval changes — still retrieved elsewhere; see the volatility section in [references/agent-readiness.md](references/agent-readiness.md))
- Industry publications and guest posts
- LinkedIn — per LinkedIn's own AEO guide, the most-cited outlet for professional-topic searches; Articles out-cite Posts ~60/40, and a post's first words become its URL slug, so front-load the target phrase (details in [references/format-volatility.md](references/format-volatility.md))
- Review sites (G2, Capterra, TrustRadius for B2B SaaS)
- YouTube (frequently cited by Google AI Overviews)
- Podcasts (episodes get transcribed, show notes published — both get crawled and cited)
@@ -366,24 +369,11 @@ For ecom and local business specifically, Google highlights:
## Content Types That Get Cited Most
Not all content is equally citable. Prioritize these formats:
Not all content is equally citable — and the format mix is **volatile**. The long-standing baseline had comparison articles (~33%) and listicles (~10%) among the top citation earners, but **ChatGPT 5.6 (Aug 2026) demoted the exploited formats: listicle citations fell −50.5% and comparison-page citations −32.1%, while `site:` and "official" retrieval surged** — a shift toward primary sources and owned pages. Format strategy is now per-platform (comparisons still work on Google AIO/Gemini/Perplexity). See [references/format-volatility.md](references/format-volatility.md) for the shift data, the per-platform format table, LinkedIn's citation numbers, and the ChatGPT fan-out extraction diagnostic.
| Content Type | Citation Share | Why AI Cites It |
|-------------|:------------:|----------------|
| **Comparison articles** | ~33% | Structured, balanced, high-intent |
| **Definitive guides** | ~15% | Comprehensive, authoritative |
| **Original research/data** | ~12% | Unique, citable statistics |
| **Best-of/listicles** | ~10% | Clear structure, entity-rich |
| **Product pages** | ~10% | Specific details AI can extract |
| **How-to guides** | ~8% | Step-by-step structure |
| **Opinion/analysis** | ~10% | Expert perspective, quotable |
**Evergreen winners across platforms:** original research and data, definitive guides, and owned "official" pages — product, docs, pricing — with extractable structure.
**Underperformers for AI citation:**
- Generic blog posts without structure
- Thin product pages with marketing fluff
- Gated content (AI can't access it)
- Content without dates or author attribution
- PDF-only content (harder for AI to parse)
**Underperformers:** generic unstructured posts, thin or gated or PDF-only content, and anything undated without author attribution.
**Citation ≠ recommendation.** Getting cited means your content was useful to consult; getting *recommended* — onto the buyer's actual shortlist — is governed by web-wide consensus (reviews, forums, analysts, press) and is largely independent of your own content. Self-promotional "best [category]" listicles can even backfire for emerging brands: in one 100-query B2B study, 69% of the AI Overview citations that self-promotional listicles earned came in answers that recommended competitors instead of the publishing brand. See [references/citations-vs-recommendations.md](references/citations-vs-recommendations.md) for the visibility ladder (retrieved → cited → mentioned → recommended), stage-dependent buyer's-guide strategy, what earns recommendations, and the attribution blind spot.
@@ -419,6 +409,8 @@ Monthly manual check:
3. Record: Are you cited? Who is? What page?
4. Log in a spreadsheet, track month-over-month
AI answers are **non-deterministic** — one run is an anecdote, not a measurement. Run each query 3–5 times per platform and track the mention *rate* with its sample size ("cited 3/5, n=5"), comparing rates over time rather than single runs. Full rigor checklist in [references/format-volatility.md](references/format-volatility.md).
### Search Console expectations
Google's guide is explicit: **there is no AI-specific Search Console reporting**. AI Overviews and AI Mode use core Search ranking, so the standard Search Console reports (Performance, Coverage, Core Web Vitals) are still what you measure with for Google. The third-party tools above are the only way to see cross-platform AI citation behavior.
+5
View File
@@ -125,6 +125,11 @@
"Does not present citation-share statistics as stable facts; recommends verifying against the user's own citation monitoring"
],
"files": []
},
{
"id": 10,
"prompt": "We're a B2B SaaS planning our 2026 content roadmap. The plan is 40 comparison pages ('us vs competitor') and 20 'best tools' listicles, mainly to win ChatGPT citations. Also, how do I know if it's working — I checked ChatGPT once last week and we weren't mentioned.",
"expected_output": "Should load references/format-volatility.md and push back on the rationale with the ChatGPT 5.6 shift (Aug 2026, Peec AI data): listicle citations fell ~50% and comparison-page citations ~32% post-5.6, with fan-out queries dropping 'best/vs/top/comparison' modifiers in favor of site: and 'official' searches — so 'win ChatGPT citations' no longer justifies scaled comparison/listicle production. Should NOT say comparison pages are dead: they still convert humans and still earn citations on Google AI Overviews, Gemini, and Perplexity — format strategy is per-platform. Should steer investment toward owned 'official' pages (product, docs, pricing, original research), which are rising as the citable class and dominate Gemini (~60% business sites). May suggest extracting ChatGPT's real fan-out queries via the DevTools method for coverage planning (while warning against mass-generating a page per query — scaled content abuse). On measurement: one ChatGPT check is an anecdote — AI answers are non-deterministic; run each query 3–5 times per platform, track mention rate with sample size (e.g. 'cited 3/5'), and compare rates over time. Numbers should be treated as dated snapshots to verify against own monitoring."
}
]
}
@@ -0,0 +1,98 @@
# Format Volatility — Which Content Formats AI Cites (and How Fast That Changes)
Citation-*source* volatility (Reddit wiped overnight, Gemini favoring owned sites) is covered in [agent-readiness.md](agent-readiness.md). This reference covers the second volatility axis: citation-*format* — which page types AI engines retrieve and cite, and the August 2026 evidence that heavily-exploited formats get demoted.
Read this before recommending comparison pages, listicles, or "best X" content for AI visibility. The advice changed materially with ChatGPT 5.6.
## The ChatGPT 5.6 format shift (August 2026)
Data from Peec AI (shared by Tomek Rudzki via Lily Ray, Aug 2026), comparing ChatGPT retrieval behavior before and after the 5.6 launch:
**Fan-out queries** — the modifiers that declined most as a share of ChatGPT's background searches:
- "vs"
- "comparison"
- "top"
- "best"
- "reviews"
At the same time: a surge in `site:` searches and modifiers like **"official"**.
**Citations by page type** — share of total ChatGPT citations:
| Page type | Pre-5.6 | Post-5.6 | Change |
|---|---:|---:|---:|
| Listicles ("Top 10 X," "8 best Y") | 15.77% | 7.80% | **−50.5%** |
| Comparison pages ("X vs Y," alternatives) | 9.08% | 6.17% | **−32.1%** |
The interpretation (Lily Ray's, and it fits the fan-out data): these are exactly the two formats companies scaled for GEO over the prior 18 months, and ChatGPT adjusted retrieval to mitigate the spam. The `site:`/"official" surge points the same direction — **toward primary sources and owned domains, away from aggregator formats**.
## What this changes (and what it doesn't)
**It does NOT mean "stop making comparison pages."** Comparison and best-of content still:
- Converts human buyers (its original job)
- Gets cited by Google AI Overviews (which follow core rankings, not ChatGPT's retrieval)
- Feeds Gemini and Perplexity, which haven't shown the same demotion
- Answers real mid-funnel queries on your own site
**It DOES mean:**
1. **Stop justifying scaled listicle/comparison production with "it wins AI citations."** On ChatGPT — the largest AI answer surface — that rationale lost half its force in one release.
2. **The "official"/primary-source shift favors your owned pages.** Product pages, docs, pricing pages, original research — the pages only you can publish — are rising as the citable class. This compounds the Gemini finding (business-owned sites ≈ 60% of citations).
3. **Format strategy is now per-platform.** Check which engines matter for your category before choosing formats:
| Format | ChatGPT (post-5.6) | Google AIO | Gemini | Perplexity |
|---|---|---|---|---|
| Listicles / best-of | Demoted | Rankings-dependent | OK | OK |
| Comparison / vs pages | Demoted | Rankings-dependent | OK | OK |
| Original research + data | Strong | Strong | Strong | Strong |
| Product/docs/pricing (owned, "official") | **Rising** | Strong | **Dominant** | Strong |
| How-to / guides | Steady | Strong | OK | Strong |
*(Table caveat: the demotion was measured on ChatGPT only. "OK" for Gemini/Perplexity means no demotion has been reported there — not that stability was measured. Any engine can ship its own 5.6-style shift.)*
4. **Treat every number above as a dated snapshot.** Same doctrine as source volatility: these are Aug 2026 measurements of a moving system. Verify against your own citation monitoring before betting budget.
## LinkedIn as a citation surface (from LinkedIn's own AEO guide)
LinkedIn quietly published its own AEO/AI-search guidance (surfaced by Chris Long, Sep 2026). The platform-reported numbers:
- LinkedIn is the **most-cited outlet for professional-topic searches**
- **~60% of LinkedIn citations come from Articles**, ~40% from Posts
- Post URLs use the **first words of the post as the slug**
**Tactics:**
- For professional/B2B topics, LinkedIn Articles are a first-class Presence-pillar surface — treat long-form Articles (not just feed posts) as citable assets with the same extractable structure as blog content.
- **Front-load the target phrase in a post's opening words** — they become the URL slug, which is retrieval surface.
- This is platform-reported data (LinkedIn grading its own homework); weight accordingly, but the Articles > Posts split matches the general pattern that long-form structured content out-cites feed content.
## DIY diagnostic: extract ChatGPT's real fan-out queries
You don't need a tool to see what ChatGPT actually searches for in your niche (method circulating publicly, Aug 2026):
1. Run an important query for your category in ChatGPT (with search).
2. Open DevTools → Network tab, refresh the conversation (URL id after `/c/`).
3. Find the conversation response payload and search it for `queries`.
4. You'll see the literal background searches ChatGPT fanned out to.
**Use it for:** building your query-test list from *real* fan-out behavior instead of guesses; checking whether your category's fan-outs still use "best/vs" modifiers or have shifted to `site:`/"official" patterns; finding sub-topics your content doesn't cover.
**Do not use it for:** auto-generating and mass-publishing an article per fan-out query. That's the exact scaled-content pattern 5.6 demoted (and Google's scaled content abuse policy names). The diagnostic is for coverage planning, not content spam.
## Measurement rigor: AI answers are non-deterministic
A single ChatGPT answer is an anecdote, not a measurement — the same prompt returns different sources run-to-run. (The statistical-rigor framing here is popularized by Initial Commit's AEO audit skill, Josh Pigford, Aug 2026; the practice stands on its own.)
When auditing or monitoring:
- **Run each query 3–5 times per platform**, fresh session each time.
- **Track mention/citation *rate*** ("cited in 3 of 5 runs"), never a yes/no from one run.
- **Report the sample size** with every number ("40% mention rate, n=5") so future-you knows how much to trust it.
- **Compare rates over time, not runs.** A drop from 4/5 to 3/5 is noise; a drop from 4/5 to 0/5 sustained across a month is signal.
- Before diagnosing *why* you're not cited, split causes the way an audit should: **technical** (can't be crawled/parsed — see agent-readiness.md), **comprehension** (AI describes you inaccurately or vaguely), or **trust** (understood but not selected — see citations-vs-recommendations.md).
---
*Sources, all labeled and dated: Peec AI pre/post-5.6 citation data via Tomek Rudzki and Lily Ray (Aug 2026); LinkedIn's AEO guide numbers via Chris Long (Sep 2026, platform-reported); fan-out extraction method as publicly circulated (Aug 2026); measurement-rigor framing credited to Initial Commit's AEO audit skill (Josh Pigford, Aug 2026). All snapshots of a volatile system — verify against your own monitoring.*
+108
View File
@@ -0,0 +1,108 @@
# Partner Program & Tools Registry — Rules & Boundaries
The single source of truth for how tools and partners work in this repository. If anything elsewhere is ambiguous, this document governs.
- **Public pitch & pricing:** [marketing-skills.com/sponsorship](https://marketing-skills.com/sponsorship)
- **Content rules for mentioning any tool:** [CONTRIBUTING.md → Mentioning Tools](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric)
- **The tool index itself:** [REGISTRY.md](REGISTRY.md)
- **The legal terms:** the Partner Agreement, provided to each partner (accepted at checkout)
## The one principle
**Sponsorship funds the work, never the recommendations.** Money buys a *disclosed presence*, never a bias. Every rule below follows from this. The library is free and MIT-licensed; sponsors and partners fund maintenance and new skills so the core stays free, open, and editorially independent — whoever is paying.
## Three kinds of tool entries
Every tool in [REGISTRY.md](REGISTRY.md) is exactly one of these:
| Kind | What it is | Who | Marker | Disclosure | Placement |
|---|---|---|---|---|---|
| **Tool integration** | A neutral integration guide for a real marketing tool with a programmatic surface | Anyone (incl. non-partners) can contribute one via PR | none | none required | Listed in the Tool Index / By Category |
| **◆ Verified Partner** | A tool whose maker funds the library (Skill or Category Partner) | Vetted, application-only, paid | ◆ | Disclosure header in its integration guide + ◆ in the registry + entry in `partners.json` | Verified Partners section + README + site + launch announcement |
| **House tool** | A tool built by the maintainer (e.g. Truelist) | The repo author | (noted) | **Stricter** than a partner — its guide states the repo author owns the tool | Held as a category House Tool; that slot is not for sale |
A partner integration is the *same* neutral integration guide as any other tool, plus disclosure and placement. It is not a different kind of content — it earns no softer editorial treatment.
## What sponsorship buys — and never buys
**Buys:**
- A dedicated, disclosed integration guide for the tool (◆).
- Featured placement — logo, link, blurb — on the README and the site.
- A launch announcement (tweet + LinkedIn + Swipe Files newsletter mention).
- For Category Partners: a category *slot* exclusivity + an "Official [Category] Partner" title/badge.
**Never buys:**
- A recommendation. No skill is edited to prefer a partner.
- Bias in any existing skill. Skills recommend the right tool for the job, partner or not.
- Exclusivity over what agents recommend. Category exclusivity is a *sponsorship-slot* exclusivity, never a recommendation exclusivity — a skill may still name a competitor when it's the right answer.
- Removal or demotion of any other tool. Partner entries are additive.
- A claim of "best in category." The badge means "paid, disclosed, vetted for fit."
## Tiers (summary)
Full pricing and perks live on the [sponsorship page](https://marketing-skills.com/sponsorship). In brief:
| Tier | Price | Billing | Gets |
|---|---|---|---|
| Supporter | $1–199/mo | GitHub Sponsors | README + site listing |
| Sponsor | $200/mo | GitHub Sponsors | Featured logo + link + blurb on README and site |
| **Skill Partner** | $500/mo | Stripe · 6-mo min | A disclosed ◆ integration + launch announcement + everything in Sponsor. **Non-exclusive.** |
| **Category Partner** | $1,500/mo | Stripe · 6-mo min | Category-slot exclusivity + official-partner title/badge + top category placement + quarterly Swipe Files feature + YouTube description slot + dual launch. Everything in Skill Partner. |
Partner tiers are **application-only** (vetted, then paid) and carry a **6-month minimum**. Annual prepay = two months free.
## Disclosure travels with the file
Disclosure is on the artifact, not just the site — skills and guides get forked and re-indexed across the ecosystem, so the disclosure must survive that.
A Verified Partner integration guide opens with this header:
```markdown
> **◆ Verified Partner integration.** [Tool] sponsors Marketing Skills. This integration
> is disclosed and vetted for fit; it does **not** change what any skill recommends. It's
> listed 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](../REGISTRY.md#verified-partners).
```
Plus a ◆ marker in [REGISTRY.md](REGISTRY.md) and an entry in [`../partners.json`](../partners.json). A **House tool** additionally states in its guide that the repo author owns the tool.
## Editorial control & the integrity rubric
- **The maintainer holds final editorial control** and may edit or cut anything for neutrality and accuracy, at any time.
- **Any content that names a tool — partner or not — must pass the [integrity rubric](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric):** options not one answer, at the point of relevance, no forced endorsement, facts over framing, disclosed, and the *swap test* (swap the tool for a competitor and it should still read fair).
- **Partner integrations surface only at the point of relevance** — when a user is implementing or working with that tool. They never hijack generic queries and never insert themselves into a skill's recommendation as the answer.
## Category exclusivity (precise definition)
- **Skill Partner is non-exclusive.** Competitors may hold Skill Partner placements in the same category.
- **Category Partner buys a slot, not the answer.** No competing tool receives a Verified Partner integration or partner slot in that category while the agreement is active. It does **not** mean core skills only recommend that partner, and it does not restrict what any skill says. Categories are defined in writing in the agreement; a multi-category tool claims one category.
- **House-tool categories are not for sale** (e.g. email verification is held by Truelist).
## The partner lifecycle
1. **Apply** — application via the sponsorship page (vetted for fit).
2. **Agreement** — the Partner Agreement (6-month minimum), accepted at checkout.
3. **Pay** — Stripe; acceptance (version + timestamp) recorded with the subscription. Nothing publishes until the first payment clears.
4. **Onboard** — the partner submits logo, blurb, docs, and setup specifics via the onboarding form.
5. **Author** — the integration guide is drafted collaboratively; **the maintainer holds the pen** and final editorial control.
6. **Publish** — add the partner to [`../partners.json`](../partners.json), run [`../scripts/sync-partners.mjs`](../scripts/sync-partners.mjs) to regenerate the README + registry blocks, commit. The site reads `partners.json` directly.
7. **Renewal / lapse** — renewal is an explicit conversation, never an automatic charge. On lapse there's a **30-day notice period** where the integration is flagged as unmaintained before removal — installs are never silently broken. Deactivate with `"active": false` (keeps history, removes it from every surface).
## `tools/integrations/` spec (any tool, partner or not)
**What qualifies:** a real marketing tool with a programmatic surface an agent can use — an API, MCP server, and/or CLI. Neutral integrations are welcome from anyone via PR.
**Format** (match the existing guides, e.g. [`integrations/resend.md`](integrations/resend.md)):
- `# Tool Name` + a one-line description
- `## Capabilities` table — API / MCP / CLI / SDK availability with notes
- `## Authentication` — auth type; secrets go in env vars / a secret manager, never in the repo
- Setup + common operations (with real command/code examples)
- Links to official docs
**CLIs** (`../clis/*.js`) are zero-dependency Node 18+ scripts: show usage with no args, support `--dry-run`, and never require credentials just to print help. See [AGENTS.md](../CLAUDE.md) build/verify rules.
**A partner integration** is all of the above **plus** the disclosure header, the ◆ marker, and the `partners.json` entry.
## Single source of truth
The partner data lives once in [`../partners.json`](../partners.json). `sync-partners.mjs` generates the README Partners section and the Verified Partners table from it; the site fetches the same file. Edit one place, run the script, commit — every surface updates together. Run `node scripts/sync-partners.mjs --check` to verify nothing has drifted.
+24
View File
@@ -10,10 +10,34 @@ Quick reference for AI agents to discover tool capabilities and integration meth
---
## Verified Partners
> **Full rules & boundaries:** [PARTNERS.md](PARTNERS.md) — the canonical governance doc (tool taxonomy, what sponsorship buys and never buys, disclosure, the partner lifecycle, and the `integrations/` spec).
◆ **Verified Partners** are tools whose makers fund Marketing Skills through the [partner program](https://marketing-skills.com/sponsorship). What the marker means — and doesn't:
- **Disclosed + vetted for fit.** Each carries a disclosure header in its integration guide and is marked ◆ in the index below.
- **Additive, never biasing.** A partner is listed *alongside* the neutral options for the same job, never instead of them. Partner status never removes or demotes another tool and **never changes what any skill recommends** — if a non-partner is the right answer, that's the answer. The badge means "paid, disclosed, vetted for fit," not "best in category."
Anyone — including tool makers and partners — may contribute content that names a tool, as long as it makes an agent *aware* of the right option without manufacturing a recommendation. The bar is the [integrity rubric in CONTRIBUTING.md](../CONTRIBUTING.md#mentioning-tools-the-integrity-rubric) (options not one answer, disclosed, passes the swap test).
<!-- PARTNERS:START -->
| Partner | Category | Guide |
|---------|----------|-------|
| ◆ Converly | Conversion tracking / attribution | [converly.md](integrations/converly.md) |
| ◆ Ploy | AI website & growth platform | [ploy.md](integrations/ploy.md) |
<!-- PARTNERS:END -->
<!-- The table above is generated from partners.json — run `node scripts/sync-partners.mjs`. -->
---
## Tool Index
| Tool | Category | API | MCP | CLI | SDK | Guide |
|------|----------|:---:|:---:|:---:|:---:|-------|
| ◆ converly | Conversion Tracking | ✓ | ✓ | ✓ | - | [converly.md](integrations/converly.md) |
| ◆ ploy | Website | ✓ | ✓ | ✓ | - | [ploy.md](integrations/ploy.md) |
| ga4 | Analytics | ✓ | ✓ | [✓](clis/ga4.js) | ✓ | [ga4.md](integrations/ga4.md) |
| mixpanel | Analytics | ✓ | - | [✓](clis/mixpanel.js) | ✓ | [mixpanel.md](integrations/mixpanel.md) |
| amplitude | Analytics | ✓ | - | [✓](clis/amplitude.js) | ✓ | [amplitude.md](integrations/amplitude.md) |
+48
View File
@@ -0,0 +1,48 @@
# Converly
> **◆ Verified Partner integration.** Converly 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](../REGISTRY.md#verified-partners).
Server-side conversion tracking: sends conversions to ad platforms and analytics tools when a visitor completes an action on your site — a form submit, a booked meeting, a started chat.
## Capabilities
| Integration | Available | Notes |
|-------------|-----------|-------|
| API | ✓ | REST API — [developers.converly.io](https://developers.converly.io) |
| MCP | ✓ | Converly MCP server — [converly.io/mcp](https://converly.io/mcp) — lets an agent set up tracking end to end |
| CLI | ✓ | Configure conversions and destinations from the terminal |
| SDK | – | Single site snippet + drag-and-drop flow builder |
## What it does
Server-side delivery bypasses ad blockers and browser privacy limits that silently drop browser-pixel events — which is what recovers "missing" conversions and lifts match rates. Converly passes name, email, phone, click IDs, and IP, enabling **Enhanced Conversions** on Google Ads and high **EMQ** (Event Match Quality) scores on Meta.
- **Destinations:** Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Google Analytics.
- **Sources (100+):** form builders (Gravity Forms, WPForms, Contact Form 7, Fluent Forms, Formidable, Ninja Forms, Typeform, Jotform, Tally, Webflow, Elementor, Wix) and CRM/scheduling/chat (HubSpot, Salesforce, Pipedrive, Calendly, HighLevel, Intercom, LiveChat).
- **Build:** one site snippet installed once, then drag-and-drop conversion flows; add/remove destinations in one click.
- **Reported lift (vendor-supplied — verify with your own holdout):** ~19% more conversions on Google Ads, ~23% on Meta Ads with server-side tracking.
## Authentication
- **Type:** API key. Store it in an environment variable / secret manager — never in the repo. `TODO: exact env var name from developers.converly.io`
## Setup (agent-driven via CLI or MCP)
1. **Authenticate** to Converly (CLI login or MCP). `TODO: exact auth command / MCP tool name`
2. **Install the site snippet** once on all pages; confirm it's in the initial HTML.
3. **Define the conversion** — pick the trigger (form submit / meeting booked / chat started) and source tool, and map the fields to capture (email, phone, name, click IDs). `TODO: create-flow command + field-mapping schema`
4. **Connect destinations** — add the ad platforms/analytics tools to send to; one conversion can fan out to several. `TODO: destination-add command + per-platform credentials (e.g. Google Ads conversion action + customer ID; Meta dataset/pixel ID + CAPI token)`
5. **Verify a real conversion** — fire a test action, confirm it lands in each destination with identifiers attached (Enhanced Conversions diagnostics on Google; EMQ on Meta). Don't call tracking done until a real conversion is observed downstream.
> The `TODO` lines are placeholders for Converly's exact syntax; fill from [developers.converly.io](https://developers.converly.io) + [converly.io/mcp](https://converly.io/mcp) during the accuracy review, then remove this note.
## How it fits the skills
- Converly is one way to **implement** the server-side send described in `attribution` → `references/first-party-tracking.md`. The *strategy* (what to count, source of truth, how to read the numbers) still comes from `attribution` and `analytics`; Converly handles the browser→server→platform hop and identity fields.
- After conversions flow, judge results with `ads` discipline: never sum conversions across attribution windows, and treat vendor lift figures as a hypothesis to verify with a holdout.
## Links
- Site: https://converly.io
- Developer docs / API: https://developers.converly.io
- MCP: https://converly.io/mcp
+48
View File
@@ -0,0 +1,48 @@
# 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](../REGISTRY.md#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](https://docs.ploy.ai/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](https://docs.ploy.ai/cli) |
| SDK | – | Agent-first instead: the CLI ships [agent skills + site inspection](https://docs.ploy.ai/cli/local-development) 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](https://docs.ploy.ai/routing-rules).
- **Analytics & visitors** — traffic tracking, visitor identification, GA4 and Google Search Console connections.
- **PloyDB** — structured content database; [CMS migration](https://docs.ploy.ai/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](https://docs.ploy.ai/cli/authentication)). Store tokens in an environment variable / secret manager — never in the repo.
## Setup (agent-driven via CLI)
1. **Install the CLI** — macOS/Linux binary ([install docs](https://docs.ploy.ai/cli/install)).
2. **Authenticate** — interactive sign-in, or set a workspace API token for [remote agents & CI](https://docs.ploy.ai/cli/remote-development) (non-interactive commands, explicit IDs, safe secret handling).
3. **Select context** — workspace and site.
4. **Build or migrate** — create pages via the agent/builder, or import existing CMS content into PloyDB and generate pages from it.
5. **Publish** — push production, connect a custom domain, verify the deploy; roll back if needed.
6. **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.
## Links
- Site: https://ploy.ai
- Docs: https://docs.ploy.ai
- CLI reference: https://docs.ploy.ai/cli/reference
- Support: support@ploy.ai