Support
A thousand technical marketers actively building AI workflows are worth more to a martech tool than a hundred thousand generic devs. Marketing Skills is the library they install into Claude Code, Cursor, and Codex — and your presence lives inside the skills their agents run. Placement in the workflow itself, not a banner beside it.
Founding partner pricing
Partners
The tools that fund the library. Each ships a clearly disclosed, verified integration — funding the work, never the recommendations.
Server-side conversion tracking
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.
The mission
Democratize access to the expertise and tooling that help businesses grow.
The skills put expert marketing playbooks inside every agent — free and open source. Partners put the tooling right beside them. Sponsorship is what keeps both within reach of any business trying to grow.
Your integration surfaces exactly when a user is doing the job your tool exists for — someone running the cold-outbound skill hits your tool at the implementation step, a cold-outbound buyer mid-task. That's intent-based placement, not impressions.
Sponsorships that depend on humans visiting a website are losing reach to AI assistants. Here, the library file is the distribution surface — it's installed into the agent, so your presence travels with the workflow wherever it runs.
Strict editorial rules — no paid influence over core skills, disclosed partner integrations — are what keep this library trusted and installed. A placement is only worth buying inside something people trust.
Sponsors give money and get visibility — frictionless, via GitHub Sponsors. Partners sign an agreement, collaborate on a disclosed skill, and get a badge — vetted, application-only. Founding rates hold for early partners and are grandfathered.
GitHub Sponsors
GitHub Sponsors
Invoiced via Stripe · 6-mo minimum
Application required. Annual prepay: 2 months free.
Invoiced via Stripe · 6-mo minimum
Application required. Annual prepay: 2 months free.
One Category Partner per category — that's the point. Claimed categories are off the market until the partnership ends.
House Tool: Truelist is built by the maintainer. Its category is reserved, not sold, and its skill carries stricter disclosure than any paying partner's. Category definitions are written into each agreement so exclusivity is unambiguous.
These are the essentials. The full rules and boundaries — the tool taxonomy, disclosure format, category exclusivity, and the partner lifecycle — live in the repo: tools/PARTNERS.md.
Sponsorship adds content — a verified partner integration — it never biases what existing skills say or recommend. Exclusivity applies to sponsorship slots, never to the agent's answers.
Every partner integration carries a ◆ marker in the tools registry and a disclosure header at the top of its guide. Registry files get forked and re-indexed across the ecosystem — the disclosure goes wherever the file goes.
A partner lives in the tools registry next to the non-partner tools for the same job — additive and marked, never removing or demoting another tool.
They surface only when a skill routes to the registry for implementation — never in place of a recommendation.
Partners draft collaboratively; accuracy edits happen whenever they're needed. It's in the agreement.
Partner tiers are application-only. The badge is worth something precisely because money alone can't buy it.
What sponsorship funds: maintaining the existing skills, building new ones, and keeping the core library free and open source under MIT. Sponsors and partners fund the work — they don't buy the recommendations. Core skills stay free, stay open, and stay editorially independent, whoever is paying.
Thanks to our supporters
No — ever. Sponsorship adds content (a clearly disclosed partner integration in the tools registry), it never biases existing skills. A partner is listed alongside the neutral options for the same job, never instead of them — being a partner never removes or demotes another tool. Exclusivity applies to sponsorship slots, never to what the agent recommends. If a core skill points to your competitor because that's the right answer, money doesn't change it.
Disclosure travels with the file, not just the site. Every partner integration carries a ◆ marker in the tools registry and a disclosure header at the top of its guide: “Verified partner integration — [Tool] sponsors Marketing Skills; this is disclosed and does not change what any skill recommends.” The registry files get scraped, forked, and re-indexed across the ecosystem — file-level disclosure survives all of that.
It means no competing tool in your category gets a verified-partner integration or a partner slot while your agreement is active. It does not mean core skills only recommend you, and it doesn't restrict what any skill says. Categories have tight written definitions in the partner agreement so there's no ambiguity about who counts as a competitor — and multi-category tools claim one category, with exclusivity binding only in the category they claim.
It's collaborative: you draft with us, and Corey holds final editorial control — including the ability to update the integration for accuracy at any time. A partner integration surfaces only when a skill routes to the tools registry for implementation — it never hijacks generic queries or changes a recommendation.
Partner tiers carry a 6-month minimum. If a partnership lapses, there's a 30-day notice period where the integration is flagged as unmaintained before removal — we don't silently break anyone's installs. Renewal is an explicit conversation, not an automatic charge.
Truelist is built by Corey, the repo's maintainer. It holds the email-verification category as a House Tool — that slot is not for sale, and Truelist's integration carries stricter disclosure than paying partners (its guide notes the repo author owns the tool). We'd rather over-disclose the self-dealing than pretend it isn't there.
No. Partner tiers are application-only — vetted, then paid. And to be precise about what the badge means: paid, disclosed, vetted-for-fit partnership. It is not a claim that yours is the best tool in the category, and it never changes what any skill recommends. That precision is exactly what keeps the badge worth carrying.
For Skill Partner and Category Partner. Just want to sponsor? Skip the form — GitHub Sponsors takes two minutes.
