Dev Marketing Prospector
Produce standardized dev-GTM prospect tables that rank SaaS companies in an exact vertical by funding stage, headcount caps, and sourced filters.
Overview
dev-marketing-prospector is an agent skill most often used in Idea (also validate scope, grow distribution) that formats dev-GTM company landscape tables with funding-stage badges and filter tags.
Install
npx skills add https://github.com/infrasity-labs/dev-gtm-claude-skills --skill dev-marketing-prospectorWhat is this skill?
- 7 funding-stage badge colour mappings (Bootstrapped through Series C+)
- Fixed table sort: earliest funding stage first, then alphabetical within stage
- Header bar rules: company count plus headcount and funding cap status
- Standard filter tags including SaaS/product-led, exact vertical, and all-data-sourced
- Column width spec for min-width 1320px horizontally scrollable prospect tables
- Table min-width 1320px layout spec
Adoption & trust: 1 installs on skills.sh; 24 GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You collected dev/SaaS prospects in a vertical but every table uses different colours, sort rules, and cap labels so you cannot compare landscapes or hand results to outreach.
Who is it for?
Solo builders mapping a devtools or PLG SaaS niche who need publication-ready landscape tables with funding and headcount constraints.
Skip if: Consumer B2C brand research unrelated to SaaS/product-led positioning, or teams that only need a single CRM export with no landscape framing.
When should I use this skill?
When the user asks for a dev/SaaS company landscape or prospect table in an exact vertical with funding and headcount filters.
What do I get? / Deliverables
You get a scrollable, consistently sorted prospect table with documented filters and header counts ready for positioning decisions or list building.
- Formatted prospect landscape table
- Header bar with company count and cap status
- Standard filter tag row
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Landscape and competitor mapping starts in Idea before you commit positioning, even though the same tables support later outreach. The skill encodes competitor and market landscape tables with funding badges and vertical filters—not product build or SEO copy.
Where it fits
Map every Series A devtool in your exact vertical before picking a wedge feature.
Check whether headcount-under-50 players already cover your planned ICP before building.
Refresh a sourced landscape table for a launch-week comparison blog or newsletter issue.
How it compares
Use for structured GTM prospect tables instead of ad-hoc competitor bullet lists from generic web research skills.
Common Questions / FAQ
Who is dev-marketing-prospector for?
Indie founders and dev-marketing leads who research SaaS landscapes and want agent output that matches a fixed funding-badge and filter-tag standard.
When should I use dev-marketing-prospector?
During Idea competitor mapping, Validate scope checks against real funded players, and Grow distribution when refreshing outbound target lists for the same vertical.
Is dev-marketing-prospector safe to install?
Check the Security Audits panel on this page; treat any skill that formats external company data as requiring your own verification of sources and privacy policy.
SKILL.md
READMESKILL.md - Dev Marketing Prospector
# Output Format Reference ## Badge Colours by Funding Stage | Stage | Background | Text colour | |---|---|---| | Bootstrapped / Breakeven | `#F1EFE8` | `#5F5E5A` | | Beta / Pre-revenue | `#FAEEDA` | `#854F0B` | | Pre-seed | `#FAEEDA` | `#854F0B` | | Seed | `#EAF3DE` | `#3B6D11` | | Series A | `#E6F1FB` | `#185FA5` | | Series B | `#EEEDFE` | `#3C3489` | | Series C+ | `#FBEAF0` | `#993556` | --- ## Table Sort Order Always sort rows by funding stage, earliest to latest: Bootstrap → Pre-seed/Beta → Seed → Series A → Series B → Series C+ Within the same funding stage, sort alphabetically by company name. --- ## Header Bar Content The table header bar must always show: - Left: vertical name + "— Exact Vertical" or "— Full Landscape" depending on whether a funding cap is applied - Right: count of companies + cap status (e.g. "8 companies · ≤50 headcount · Pre-seed → Series A" or "11 companies · No funding cap · No headcount cap") --- ## Filter Tags Always show filter tags below the header bar. Standard tags: - The vertical name (exact wording the user gave) - Headcount filter (e.g. "Headcount < 50") or "No headcount cap" - Funding range (e.g. "Pre-seed → Series A") or "No funding cap" - "SaaS / Product-led" (always present) - "Exact vertical only" (always present) - "All data sourced" (always present — signals the sourcing standard) --- ## Column Widths (min-width 1320px table, horizontally scrollable) | Column | Width | |---|---| | Company (name + badge + headcount) | 115px | | URL | 75px | | LinkedIn | 80px | | Headcount | 58px | | Signal + Why Dev Marketing | 195px | | Signal Sources | 130px | | Geography | 80px | | Pain Point | 195px | | Pain Point Sources | 145px | Total: ~1073px minimum. Set min-width: 1073px on the table and wrap in a horizontally scrollable <div class="wrap">. --- ## Company Cell Content Each company cell must contain, in order: 1. Company name — `font-weight: 500`, `font-size: 12.5px` 2. Funding badge — colour per stage table above 3. Sub-line: `Founded YYYY` in muted 10px text 4. Optional: one-line phase descriptor of what the company specifically does in the vertical (e.g. "Durable AI workflow orchestration") --- ## Signal Cell Content 2–4 sentences. Include: - The specific trigger event (round, launch, partnership, award) with amount, date, and lead investor where applicable - A direct connection to why developer marketing is relevant for this company right now — do not leave this implicit --- ## Signal Sources Cell Content A compact numbered list. Each entry is a clickable link: ```html <ul class="src-list"> <li> <a href="https://..." target="_blank"> <span class="ref-num">S1</span> Source label — what data point it proves </a> </li> </ul> ``` Format for the ref-num span: - `background: var(--color-background-secondary)` - `border: 0.5px solid var(--color-border-secondary)` - `border-radius: 3px` - `font-size: 9px` - `padding: 0 3px` - `color: var(--color-text-secondary)` Keep source labels to ~6 words. The label must describe what the source proves, not just the source name. Examples: - "PitchBook — funding & headcount" ✓ - "Sacra — 32k downloads, 35x YoY" ✓ - "PitchBook" ✗ (too vague) --- ## Pain Point Cell Content 2–4 sentences. Must: - Reference specific numbers and competitor context - State the consequence clearly — what happens if they don't fix the gap - Never be generic ("they need more awareness") If a claim in the pain point is self-reported by the company (not independently verified), add this warning badge directly in the cell: ```html <span class="warn">⚠ [Stat] is self-reported by [Company] — not independently verified</span> ``` Warning badge CSS: - `background: #FAEEDA` - `color: #633806` - `font-size: 9px` - `padding: 1px 4px` - `border-radius: 3px` - `display: inline-block` - `margin-top: 2px` --- ## Pain Point Sources Cell Content Same format as Signal Sources but using P1, P2... reference numbers. For infe