---
title: "shadowfax"
description: "Founder-side GTM pack: find where demand already talks, pick one bet, draft the reach. Research and drafts only."
canonical: https://agentpluginsdirectory.com/plugins/shadowfax
last-updated: 2026-10-08
---

# shadowfax
Founder-side GTM pack: find where demand already talks, pick one bet, draft the reach. Research and drafts only.
- Slug: shadowfax
- Publisher: Sabique Islam
- Repository: https://github.com/sabique-islam/shadowfax
- Manifest: plugin.json
- Version: 0.3.0
- License: MIT
- Category (editorial): research
- Skills: 40 (activation, aeo, analytics, beyond-wrapper, buyer-gap, campaign-review, competitive, content-audit, content, customer-support, distribution, experimentation, find-communities, find-complaints, first-users, github, growth-loops, homepage, icp, inbound, iteration, launches, market-research, onboarding, outreach, positioning, posts, pricing, prospecting, review, roadmap, sales, setup-shadowfax, shadowfax, talk-to-users, trends, value-prop, video-ideas, write, youtube)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-22
- Repository last pushed: 2026-08-27
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/shadowfax
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What shadowfax does, in the publisher's words

Shadowfax is an agent plugin for Cursor, Claude Code, and other coding agents. It keeps a short notes file in your project (what the product does, who you've talked to, what's been tried), researches where people already complain about your problem, and drafts the next step, cold email, launch post, support reply, pricing call prep, SEO fix.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/sabique-islam/shadowfax/HEAD/README.md

## Skills

- activation: Diagnoses time-to-first-value and the weekend test for dev tools. Use when people sign up or star then vanish, docs assume expertise, or traffic is planned before first-run works.
- aeo: Splits answer-engine visibility into crawl, cite, and click, and maps citation exports back to post slugs. Use when the founder asks about AEO, AI Overviews, ChatGPT/Claude citations, or whether LLMs quote the blog. Does not invent citation counts.
- analytics: Inspects acquisition, activation, and retention to name where the funnel is broken. Use when the founder pastes metrics, PostHog, or "people signed up but nobody stayed." Does not generate more top-of-funnel to paper over activation.
- beyond-wrapper: Positions AI products against the wrapper accusation when the model is a commodity. Use when everyone claims AI, differentiation is unclear, or prospects say it is just ChatGPT with a UI.
- buyer-gap: Separates the developer adopter from the budget holder and drafts middle-out motion for getting paid. Use when devs love the free tier, stars grow, and no line item gets approved.
- campaign-review: Reviews a specific campaign: what was sent, what happened, and whether the failure was message, audience, channel, or product. Use after a launch, outreach batch, or ad. Allowed to say it failed.
- competitive: Records competitors' positioning, launches, pricing, channels, and messaging as dated facts. Use when the founder asks who else is in the space or how a rival talks. Does not write our positioning.
- content-audit: Ranks existing blog posts by search opportunity (recover, CTR gap, rank-to-page-one), flags hygiene, and drafts surgical edits. Use when the founder pastes GSC, empty SEO fields, a blog audit, or "ranking but no clicks." Does not publish. Does not write a new post.
- content: Drafts long-form from product work, PRs, user language, or Search Console near-misses, then gates the draft (strategy, structure, code provenance, cannibalization). Use when the channel bet is content-shaped or the founder asks for an article, changelog essay, Show HN writeup, or a new SEO post. Do…
- customer-support: Drafts support replies, ticket responses, and FAQ entries from product truth and evidence. Use when handling customer emails, in-app tickets, refund requests, or repetitive support questions. Does not send.
- distribution: Chooses the single distribution path for this cycle and justifies it from where the ICP already is. Use when deciding cold outreach vs GitHub vs HN vs Reddit vs X vs community vs partner vs SEO vs launch. Does not write the assets.
- experimentation: Defines one distribution experiment with hypothesis, sample, signal, timebox, and kill. Use when proposing or tightening a GTM test. Does not run a content calendar or invent success.
- find-communities
- find-complaints
- first-users
- github
- growth-loops
- homepage
- icp
- inbound
- iteration
- launches
- market-research
- onboarding
- outreach
- positioning
- posts
- pricing
- prospecting
- review
- roadmap
- sales
- setup-shadowfax
- shadowfax
- talk-to-users
- trends
- value-prop
- video-ideas
- write
- youtube

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.