NotFair Plugin: 48 Marketing Skills That Turn Claude Code Into an SEO and Ads Operator

Marketing is where coding agents usually fall apart: the work is procedural, the data lives in ad and analytics platforms, and one vague prompt produces one vague answer. The NotFair plugin — a 4k-star, MIT-licensed repository — takes the opposite approach. It splits marketing into 48 focused skills, each with a defined job, required inputs, decision rules, and an output format, and it wires them to live account data.

Why This Skill Matters

The README's catalog counts out to 48 skills across eight groups: 20 for SEO and GEO, 14 for paid media, 5 for Google Ads, 3 for Meta Ads, 2 for analytics, plus one each for WordPress and GoHighLevel CRM, and 2 for cross-model review and maintenance. On the SEO side, skills cover full-site audits, keyword research, schema markup, hreflang, sitemaps, e-commerce and programmatic SEO, and regression monitoring; the GEO/AEO area specifically targets citations in AI answers — ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews, per the README. On the paid side, skills audit and operate connected Google, Meta, X, LinkedIn, Reddit, and TikTok Ads accounts.

The design rule that separates it from a prompt pack: read-only review comes before mutation, and paid-media changes stay explicit. Live analysis runs through one OAuth-connected NotFair MCP server rather than a pile of per-platform integrations.

Installation

In Claude Code, add the marketplace and install:

/plugin marketplace add nowork-studio/notfair-plugin
/plugin install notfair@nowork-studio

The README documents the same plugin for Cursor (marketplace listing or a local clone into ~/.cursor/plugins/local/notfair), Kiro (Powers panel), Gemini CLI (gemini extensions install https://github.com/nowork-studio/notfair-plugin), and Codex. Live account skills need one more step: complete the OAuth flow for the NotFair MCP connection, and each platform — Search Console, GA4, the ad accounts, WordPress, GoHighLevel — becomes available after you connect it in the NotFair workspace the flow selects.

Real Workflow: Diagnose a Traffic Drop With Live Data

Ask in plain language, the way the README's own example does: "Audit my site and tell me why organic traffic fell." That routes into /notfair:seo-analysis, which audits the full site with Search Console and crawl data and prioritizes the highest-impact fixes.

Then go narrower. /notfair:search-console analyzes live queries and pages and inspects specific URLs; /notfair:google-analytics compares GA4 periods for acquisition, engagement, and conversions. If the drop traces to a page, /notfair:seo-page runs a deep audit of that URL for intent, content, and on-page issues; if it traces to content, /notfair:content-planner turns the Search Console opportunities into a dated editorial calendar.

For ad spend, /notfair:paid-ads-review builds comparable weekly or monthly scorecards and checks tracking health before /notfair:paid-ads-optimize proposes what the README calls narrow, reversible changes — which you approve before anything executes.

Tips

• Slash commands are optional: plain sentences like "Find pages that could earn citations in AI answers" route to the right skill through the repository's AGENTS.md intent map.
• Skills reference platforms through placeholders such as ~~google-ads that resolve to whatever compatible tool the current session exposes, so workflows are not coupled to one MCP namespace.
• Two ad platforms are the exception to live operations: the README states Amazon and ChatGPT Ads remain planning or export-review workflows unless your session exposes a verified connector.
• Beyond the skills, an optional local app (npx notfair@latest) turns a measurable marketing outcome into a recurring agent loop and stores its state locally.

When Not to Use This

Live account analysis depends on routing data through the hosted NotFair MCP connection; if your security posture forbids that, you are left with the skills that work entirely from a repository, URL, or supplied export. The operators for WordPress and GoHighLevel make only explicitly requested changes, so bulk sweeps are out of scope by design. And this is a marketing toolkit — codebase work needs a different set of skills entirely.

See the leaderboard for more skills.