{ "title": "Developer Marketing field guide — skills", "updated": "2026-07-26", "count": 13, "skills": [ { "id": "devmarketing-skills-the-whole-stack-on-one-shelf", "title": "devmarketing-skills: the whole stack on one shelf", "name": "devmarketing-skills", "author": "Jonathan Heimer", "repo": "jonathimer/devmarketing-skills", "summary": "Thirty-four skills covering audience context, content, distribution, developer experience, growth and retention — every one reads a shared developer-audience file first.", "job": "foundation", "agents": [ "claude-code", "cursor", "windsurf", "codex" ], "install": "npx skills add jonathimer/devmarketing-skills", "license": "MIT", "caveat": "Prescriptive playbooks, not sourced research — the outputs are drafts, and the claims inside them are yours to check before they ship.", "note": "The closest thing to this guide in installable form, and grouped the way the\nwork actually divides: audience context, content and community, distribution and\ndiscovery, developer experience, growth, lifecycle. The design decision worth\nnoticing is `developer-audience-context` — you state your persona, their\ntechnical level, their pain points and where they hang out once, and every other\nskill reads it first, which is what stops the outputs drifting into generic SaaS\nvoice. Install that one even if you install nothing else; the folder list\n(`hacker-news-strategy`, `docs-as-marketing`, `free-tier-strategy`,\n`developer-signup-flow`) reads like a table of contents for the sections here.", "section": "00-start-here", "section_url": "https://developer-marketing.vercel.app/guide/00-start-here/", "tags": [ "positioning", "content", "distribution", "activation", "devrel" ], "source": { "label": "jonathimer/devmarketing-skills", "url": "https://github.com/jonathimer/devmarketing-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "marketingskills-state-your-positioning-once", "title": "marketingskills: state your positioning once, inherit it everywhere", "name": "product-marketing", "author": "Corey Haines", "repo": "coreyhaines31/marketingskills", "summary": "The general-marketing shelf — 60 skills across CRO, copywriting, SEO, pricing and lifecycle — wired so each one reads your product-marketing context file before it writes.", "job": "positioning", "agents": [ "claude-code", "cursor", "windsurf", "codex" ], "install": "npx skills add coreyhaines31/marketingskills", "license": "MIT", "caveat": "Written for marketers at large, so it will hand you funnel advice a developer audience punishes. Take the structure; keep the technical judgment yours.", "note": "The most-used shelf of the lot — 41.8k stars as of July 2026 — and the reason it\nearns a place on a developer-marketing page is structural rather than\neditorial. Every skill checks `product-marketing` first: one file at\n`.agents/product-marketing.md` holding your product, audience and positioning,\nso the claim is stated once and inherited by the landing page, the pricing page\nand the launch post instead of being re-improvised in each. That is the same\ndiscipline positioning demands of a human team, enforced by the tooling. The\nindividual skills are generic B2B by default; the context file is where you make\nthem survive contact with an engineer.", "section": "01-positioning-for-developers", "section_url": "https://developer-marketing.vercel.app/guide/01-positioning-for-developers/", "tags": [ "positioning", "content", "cro", "seo", "pricing" ], "source": { "label": "coreyhaines31/marketingskills", "url": "https://github.com/coreyhaines31/marketingskills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "diataxis-docs-framework-a-house-style-you-can-adopt", "title": "diataxis-docs-framework: a house style you can adopt instead of argue", "name": "diataxis-docs-framework", "author": "Anivar Aravind", "repo": "anivar/developer-docs-framework", "summary": "Diátaxis expanded to fourteen content types, 27 rules, and six pluggable style guides — Google, Microsoft, Stripe, Canonical, Good Docs, or minimal.", "job": "docs", "agents": [ "claude-code", "cursor", "windsurf", "codex" ], "install": "git clone https://github.com/anivar/developer-docs-framework", "license": "MIT", "caveat": "Ships as reference material with no one-line installer — clone it and copy the folder into .claude/skills/. The rules synthesise published methodologies; they are not measured against your readers.", "note": "Where an auditor scores what you have, this decides what to write. Diátaxis'\nfour modes — tutorial, how-to, reference, explanation — expand into the fourteen\ntypes a developer product actually ships (quickstart, integration guide,\nmigration guide, troubleshooting, SDK reference, config reference, runbook,\nglossary), each with its own guidance and anti-patterns. The pluggable style\nguides are the pragmatic part: a team picks Google or Stripe or minimal and\ninherits a settled answer on voice, person and tense, which is an argument you\notherwise re-run in every review.", "section": "02-docs-as-front-door", "section_url": "https://developer-marketing.vercel.app/guide/02-docs-as-front-door/", "tags": [ "docs", "content", "writing" ], "source": { "label": "anivar/developer-docs-framework", "url": "https://github.com/anivar/developer-docs-framework" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "docs-auditor-make-our-docs-are-fine-falsifiable", "title": "docs-auditor: make “our docs are fine” falsifiable", "name": "docs-auditor", "author": "Infrasity Labs", "repo": "Infrasity-Labs/dev-gtm-claude-skills", "summary": "Thirty-three checks across AI discoverability, structure, content quality, SEO and internal linking, returned as a 0–100 score with prioritised fixes.", "job": "docs", "agents": [ "claude-code", "claude-ai", "codex" ], "install": "npx skills add Infrasity-Labs/dev-gtm-claude-skills", "license": "MIT", "caveat": "Structural checks cannot tell you whether the quickstart runs. Pair the score with a real time-to-first-call test on a clean machine.", "note": "Docs are the highest-leverage surface you own and nobody scores their own. A\nthirty-three-check pass with a number at the end is worth having mostly because\nit converts \"our docs are fine\" into a claim someone can disagree with before a\nlaunch, and because the AI-discoverability half of the checklist is work most\ndocs teams have not yet been asked to do. The same repo carries\n`api-docs-quality-report` for per-endpoint scoring and the linking audits\n(`orphan-pages-internal-linking-opportunities`, `no-outlinks-audit`) that catch\nthe pages nothing points at — a common quiet failure in docs that grew by\naccretion.", "section": "02-docs-as-front-door", "section_url": "https://developer-marketing.vercel.app/guide/02-docs-as-front-door/", "tags": [ "docs", "seo", "geo", "metrics" ], "source": { "label": "dev-gtm-claude-skills: docs-auditor", "url": "https://github.com/Infrasity-Labs/dev-gtm-claude-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "readme-skill-write-and-review-the-repo-front-door", "title": "readme-skill: write and review the repo front door", "name": "readme", "author": "Alberto Grande", "repo": "albertogrande/readme-skill", "summary": "Generates or audits a README against a cited standard, scored out of 100 across identity, trust, onboarding, structure, craft, and agent-readability.", "job": "readme", "agents": [ "claude-code" ], "install": "/plugin marketplace add albertogrande/readme-skill\n/plugin install readme-skill@readme-skill", "license": "MIT", "caveat": "One artifact only — it grades the README, not the docs site behind it, and the voice is yours to supply via a style profile.", "disclosure": "Published by this site's author.", "note": "For most developer products the README *is* the landing page: it is where a link\nfrom Hacker News lands, what a model retrieves when someone asks what your thing\ndoes, and the page read before anyone reaches the docs site. This is the only\nskill on the shelf that treats it as a scored artifact — every rule traces to a\nsource (the canonical guides, twenty top-tier READMEs, GitHub's own docs, and\n2025–2026 research on how agents read repos), and `review` returns a rubric with\nconcrete replacement text for the worst offender instead of vague prose. Reach\nfor it before a launch, and again the moment an install command changes.", "section": "02-docs-as-front-door", "section_url": "https://developer-marketing.vercel.app/guide/02-docs-as-front-door/", "tags": [ "docs", "readme", "github", "positioning" ], "source": { "label": "albertogrande/readme-skill", "url": "https://github.com/albertogrande/readme-skill" }, "sources": [ { "label": "The rule set — anatomy.md", "url": "https://github.com/albertogrande/readme-skill/blob/main/skills/readme/references/anatomy.md" } ], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "developer-listening-hear-the-rooms-you-are-not-in", "title": "developer-listening: hear the rooms you are not in", "name": "developer-listening", "author": "Jonathan Heimer", "repo": "jonathimer/devmarketing-skills", "summary": "A repeatable sweep of developer conversation across Reddit, Hacker News, Discord and issue trackers, turned into notes a DevRel team can act on.", "job": "research", "agents": [ "claude-code", "cursor", "windsurf", "codex" ], "install": "npx skills add jonathimer/devmarketing-skills", "license": "MIT", "caveat": "Public conversation only — the sharpest signal about your own product still arrives in the support queue and the issue tracker.", "note": "DevRel's real input is what developers say when you are not in the room, and the\nreason most teams do it badly is that it is unglamorous, cross-platform, and\nnever finished. Handing the sweep to an agent makes the cadence survivable: the\nsame loop this paper's scout desk runs on the industry, pointed at your category\ninstead. Its siblings in the repo — `reddit-engagement`, `hacker-news-strategy`\n— cover what to do once you have heard something, including the part where\nposting in the wrong register gets you flagged.", "section": "03-devrel-and-community", "section_url": "https://developer-marketing.vercel.app/guide/03-devrel-and-community/", "tags": [ "devrel", "community", "research", "listening" ], "source": { "label": "devmarketing-skills: developer-listening", "url": "https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-listening" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "mcp-builder-your-tool-descriptions-are-now-the-docs", "title": "mcp-builder: your tool descriptions are now the docs", "name": "mcp-builder", "author": "Anthropic", "repo": "anthropics/skills", "summary": "Anthropic's own four-phase guide to building an MCP server — research, implement, review, then generate ten evaluations that test whether a model can actually use it.", "job": "product-surface", "agents": [ "claude-code", "claude-ai" ], "install": "/plugin marketplace add anthropics/skills\n/plugin install example-skills@anthropic-agent-skills", "license": "Apache-2.0", "caveat": "An engineering skill, engineering-owned in most teams. Bring it to whoever ships the server rather than running it alone.", "note": "For a growing share of your users the tool description *is* the documentation:\nthey never read the reference, because an agent chose your tool on the strength\nof one sentence and a JSON schema. That makes naming, annotations\n(`readOnlyHint`, `destructiveHint`, `idempotentHint`) and error copy a\nfirst-touch surface, and it is on a marketing shelf because nobody else in the\ncompany is going to own how it reads. The phase most worth stealing is the last\none: ten independent, verifiable evaluation questions that measure whether a\nmodel can complete real tasks against your server — a time-to-first-call test\nfor the agent era.", "section": "04-developer-experience-and-activation", "section_url": "https://developer-marketing.vercel.app/guide/04-developer-experience-and-activation/", "tags": [ "dx", "mcp", "agents", "activation" ], "source": { "label": "anthropics/skills: mcp-builder", "url": "https://github.com/anthropics/skills/tree/main/skills/mcp-builder" }, "sources": [ { "label": "SKILL.md — the four phases and the evaluation format", "url": "https://github.com/anthropics/skills/blob/main/skills/mcp-builder/SKILL.md" } ], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "sdk-docs-auditor-grade-the-gap-where-activation-dies", "title": "sdk-docs-auditor: grade the gap where activation dies", "name": "sdk-docs-auditor", "author": "Infrasity Labs", "repo": "Infrasity-Labs/dev-gtm-claude-skills", "summary": "Scores SDK docs across the six sections integration actually fails in — installation, quick start, error handling, troubleshooting, examples, best practices — as an HTML report.", "job": "dx", "agents": [ "claude-code", "claude-ai", "codex" ], "install": "npx skills add Infrasity-Labs/dev-gtm-claude-skills", "license": "MIT", "caveat": "It audits the docs for the SDK, not the SDK. A clean report on a hostile API is still a hostile API.", "note": "Activation rarely dies at install; it dies in the hour after, when the first call\nreturns an error nobody documented. The six sections this grades map almost\nexactly onto that hour, and the two teams usually miss — error handling and\ntroubleshooting — are the two nobody is measured on. Run it on your own SDK docs\nand on the competitor a prospect is comparing you against; the delta is a more\npersuasive internal argument than a satisfaction survey.", "section": "04-developer-experience-and-activation", "section_url": "https://developer-marketing.vercel.app/guide/04-developer-experience-and-activation/", "tags": [ "dx", "activation", "docs", "sdk" ], "source": { "label": "dev-gtm-claude-skills: sdk-docs-auditor", "url": "https://github.com/Infrasity-Labs/dev-gtm-claude-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "skill-creator-package-what-you-know-as-something-installable", "title": "skill-creator: package what you know as something installable", "name": "skill-creator", "author": "Anthropic", "repo": "anthropics/skills", "summary": "Scaffolds and validates an Agent Skill — the packaging format that puts your conventions, gotchas and idiomatic examples inside the agent your users already work in.", "job": "content", "agents": [ "claude-code", "claude-ai" ], "install": "/plugin marketplace add anthropics/skills\n/plugin install example-skills@anthropic-agent-skills", "license": "Apache-2.0", "caveat": "Ship knowledge that is genuinely yours. A skill that reads like a brochure gets uninstalled faster than a bad README gets closed.", "note": "A skill is a content surface that did not exist two years ago: your migration\ngotchas, your idiomatic error handling, your \"do not do it that way\" — installed\ninto the tool a developer is already in, invoked without them ever visiting your\nsite. This is the tool that builds and validates one, and the discipline it\nenforces is the discipline good docs need anyway: a description tight enough to\ntrigger on the right task, progressive disclosure so the body stays small, no\ndead weight. The shelves catalogued on this page are themselves the evidence\nthat the format travels — thirty-four skills, sixty skills, installed by\nstrangers with one command.", "section": "05-content-that-earns-trust", "section_url": "https://developer-marketing.vercel.app/guide/05-content-that-earns-trust/", "tags": [ "content", "docs", "agents", "distribution" ], "source": { "label": "anthropics/skills: skill-creator", "url": "https://github.com/anthropics/skills/tree/main/skills/skill-creator" }, "sources": [ { "label": "The Agent Skills specification", "url": "https://github.com/anthropics/skills/tree/main/spec" } ], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "geo-skills-twelve-rules-for-being-cited-not-crawled", "title": "geo-skills: twelve rules for being cited, not just crawled", "name": "geo-skills", "author": "luka2chat", "repo": "luka2chat/geo-skills", "summary": "The knowledge layer for generative-engine optimisation — content patterns, structured data, crawler config, llms.txt, E-E-A-T and the monitoring to see if any of it moved.", "job": "seo-geo", "agents": [ "any" ], "install": "npx skills add luka2chat/geo-skills", "license": "MIT", "caveat": "No citations behind the rules — it descends from a curated awesome-list. A well-organised checklist, not evidence.", "note": "Audit tools tell you what is missing; this changes how you brief the work in the\nfirst place. Twelve rules across four groups — content and strategy, technical\nimplementation, authority and trust, platforms and analytics — each with\ntemplates and config you can lift. It is on the shelf because the rules are\norganised the way a marketer thinks rather than the way a crawler works, and\nbecause it ships in the format 37-plus agents can read, which is itself the\nargument its own category is making.", "section": "06-channels-and-distribution", "section_url": "https://developer-marketing.vercel.app/guide/06-channels-and-distribution/", "tags": [ "geo", "seo", "distribution", "content" ], "source": { "label": "luka2chat/geo-skills", "url": "https://github.com/luka2chat/geo-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "gtm-engineer-skills-from-audit-to-diff", "title": "gtm-engineer-skills: from audit to diff", "name": "improve-aeo-geo", "author": "onvoyage-ai", "repo": "onvoyage-ai/gtm-engineer-skills", "summary": "Twelve skills that research, plan and then patch — AEO/GEO auditing with framework-specific fixes, shipped with worked plans for a Next.js blog and a WordPress site.", "job": "seo-geo", "agents": [ "claude-code" ], "install": "git clone https://github.com/onvoyage-ai/gtm-engineer-skills.git\nmkdir -p ~/.claude/skills\nln -s \"$PWD/gtm-engineer-skills/audit-website-aeo\" ~/.claude/skills/audit-website-aeo\nln -s \"$PWD/gtm-engineer-skills/improve-aeo-geo\" ~/.claude/skills/improve-aeo-geo", "license": "MIT", "caveat": "Manual clone-and-symlink per skill, and a marketing agent editing your app needs the same review as any other contributor.", "note": "The third GEO entry here, and the one that goes past reporting: alongside brand\nand keyword research it carries `improve-aeo-geo`, which proposes\nframework-specific changes to the site itself. Pick between the three by what you\nare short of. Knowledge you lack: read the rules. A number you lack: run the\n`llms.txt` probe. A diff you lack, on a site you own and can review: this one.\nThe marketing-engineer role it assumes — someone comfortable opening a pull\nrequest against the marketing site — is the role this whole shelf quietly\nrequires.", "section": "06-channels-and-distribution", "section_url": "https://developer-marketing.vercel.app/guide/06-channels-and-distribution/", "tags": [ "geo", "seo", "distribution", "tooling" ], "source": { "label": "onvoyage-ai/gtm-engineer-skills", "url": "https://github.com/onvoyage-ai/gtm-engineer-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "llms-txt-checker-can-the-answer-engines-read-you-at-all", "title": "llms-txt-checker: can the answer engines read you at all", "name": "llms-txt-checker", "author": "Infrasity Labs", "repo": "Infrasity-Labs/dev-gtm-claude-skills", "summary": "Probes robots.txt, llms.txt and llms-full.txt, scores AI-readiness against a structured checklist, and needs no API key.", "job": "seo-geo", "agents": [ "claude-code", "claude-ai", "codex" ], "install": "npx skills add Infrasity-Labs/dev-gtm-claude-skills", "license": "MIT", "caveat": "Presence, not persuasion — every file can pass while the content behind them earns no citation.", "note": "The cheapest check on this page: minutes, no credentials, and it answers a\nquestion most devtool teams have not formally asked — whether the systems now\nfielding \"what should I use for X\" can reach and parse us at all. Treat the\nresult as a floor rather than a strategy. A pass means you are legible; being\nchosen is a content problem, and blocking the crawlers you did not mean to block\nis a robots.txt problem you will be glad you found before the next quarter's\ntraffic review.", "section": "06-channels-and-distribution", "section_url": "https://developer-marketing.vercel.app/guide/06-channels-and-distribution/", "tags": [ "geo", "distribution", "docs", "agents" ], "source": { "label": "dev-gtm-claude-skills: llms-txt-checker", "url": "https://github.com/Infrasity-Labs/dev-gtm-claude-skills" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" }, { "id": "changelog-generator-the-most-read-page-nobody-owns", "title": "changelog-generator: the most-read page nobody owns", "name": "changelog-generator", "author": "Composio", "repo": "ComposioHQ/awesome-claude-skills", "summary": "Reads git history, groups changes into added, improved, fixed and breaking, drops internal noise, and returns release notes a human can edit in ten minutes.", "job": "launch", "agents": [ "claude-code" ], "install": "git clone https://github.com/ComposioHQ/awesome-claude-skills.git\nmkdir -p ~/.claude/skills\ncp -r awesome-claude-skills/changelog-generator ~/.claude/skills/", "license": "Apache-2.0 (per-skill may differ)", "caveat": "Commits are the wrong source for why a change matters. It drafts the what; the why, the migration note and the breaking-change warning are yours.", "note": "For most developer products the changelog is read more often than the blog and\nowned by nobody, because translating forty commits into user-facing language is a\nchore that loses to whatever shipped that week. Handing the first draft to an\nagent is the cheapest way to restore the cadence — and cadence is the point, as\nthe operators who turned releases into a recurring weekly beat keep\ndemonstrating. Keep the human edit: the categories come from the commits, but\n\"you must change your webhook handler before August\" never does.", "section": "07-launches", "section_url": "https://developer-marketing.vercel.app/guide/07-launches/", "tags": [ "launches", "changelog", "releases", "docs" ], "source": { "label": "awesome-claude-skills: changelog-generator", "url": "https://github.com/ComposioHQ/awesome-claude-skills/tree/master/changelog-generator" }, "sources": [], "added": "2026-07-26", "verified": "2026-07-26" } ] }