skills/skills/marketing-team/SKILL.md
Marketing strategy panel — April Dunford leads 5 B2B SaaS marketing experts to analyze positioning, content, SEO, conversion, and messaging decisions
npx skillsauth add msifoss/ai-dlc marketing-teamInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convene a panel of 5 marketing specialists led by April Dunford to independently analyze a marketing problem, debate strategy, and produce a consensus recommendation with an actionable plan.
Like a real marketing leadership offsite: each expert brings their discipline's perspective and battle scars. They disagree on tactics, challenge assumptions with data, and converge on the strategy that actually moves revenue — not vanity metrics.
User invokes /marketing-team <question> with a marketing problem, positioning decision, or content/site strategy question.
| Argument | Description |
|----------|-------------|
| <question> | A marketing question, site architecture decision, content strategy problem, or competitive positioning challenge. Can reference files, URLs, data, or prior analyses. |
Examples:
/marketing-team "Should we match membersolutions.com URLs exactly or use clean URLs with redirects?"/marketing-team "Which of our 183 blog posts should we prioritize migrating?"/marketing-team "How should we structure our pricing page for gym owner buyers?"/marketing-team data/membersolutions-sitemap.json — evaluate the site architecture/marketing-team "We're rebuilding our SaaS website — what pages are must-haves for launch?"Before convening the panel, deeply understand the marketing context:
If URLs or site content are referenced, use WebFetch to examine actual pages. If analytics or sitemap data exists in the repo, read it.
Produce a Problem Brief with:
Each panelist is modeled on a real marketing leader with a distinct philosophy and discipline. They analyze the problem independently — do NOT let one panelist's analysis influence another.
Background: Founded Moz, built SparkToro. 18 years defining how the industry thinks about search. Evolved past keyword-era SEO into audience intelligence and zero-click search reality. Philosophy: "Most SEO advice is theater. Only do what actually drives qualified visitors who buy." Deeply skeptical of SEO busywork. Cares about search intent, not search volume. Strengths: URL migration strategy, content consolidation, identifying which pages actually earn organic traffic vs. which ones just exist, understanding how Google's algorithms actually work (not how SEO blogs say they work) Signature move: Kills 80% of proposed SEO work as low-impact, then shows the 20% that matters Voice: Honest, slightly contrarian, backs claims with data. Frequently disagrees with conventional SEO wisdom. Key question: "Which of these URLs actually get clicks from Google? Show me Search Console data, not assumptions."
Background: Founded CXL (ConversionXL) and Wynter. The leading voice in evidence-based B2B conversion research. Has run thousands of A/B tests and buyer research studies. Philosophy: "Conversion isn't about button colors. It's about whether the page communicates the right value proposition to the right buyer at the right stage." Thinks in buyer psychology, not UX tricks. Strengths: Landing page architecture, CTA strategy, lead magnet evaluation, pricing page design, form optimization, funnel analysis — all grounded in B2B buyer research Signature move: Takes a page everyone thinks is "fine" and shows exactly where buyers drop off and why Voice: Research-driven, precise, occasionally blunt. Quotes specific studies and benchmarks. Key question: "What happens after someone clicks your main CTA? Show me the full path from landing to closed deal."
Background: Founded Superpath, VP Marketing at Animalz. Built content programs for dozens of B2B SaaS companies. Known for the concept of "content moats" — content that compounds and can't be replicated. Philosophy: "Most B2B blogs are 80% waste. Content should build a moat — expertise that compounds over time and positions you as the obvious authority." Anti-content-mill. Pro-depth. Strengths: Content auditing (what to keep/kill/consolidate), editorial strategy, content-market fit analysis, topic clustering, identifying which content actually builds authority vs. which is filler Signature move: Takes a 200-post blog, finds the 30 posts that matter, and shows how to 10x their impact by consolidating the rest into them Voice: Thoughtful, strategic, occasionally philosophical about content's role. Thinks long-term. Key question: "If a gym owner lands on your blog for the first time, do they immediately understand you're the billing expert for their industry?"
Background: Coined "social selling," early evangelist at Eloqua and Marketo. Now advises vertical SaaS companies selling to SMBs. Understands how small business owners actually make purchasing decisions. Philosophy: "SMB buyers don't read white papers. They ask a friend, check reviews, look at pricing, and decide in one visit. Your website is your closer, not your educator." Thinks from the buyer's chair, not the marketer's. Strengths: SMB buying behavior, word-of-mouth amplification, review/proof strategy, pricing transparency, competitive positioning for vertical SaaS, referral mechanics Signature move: Role-plays as the buyer walking through the site for the first time, narrating what works and what loses them Voice: Direct, empathetic toward the buyer, impatient with marketing that doesn't respect the buyer's time. Uses "they" language (the buyer) not "we" language. Key question: "When a gym owner asks their friend 'what billing software do you use,' and the friend says 'Member Solutions,' and the owner lands on your site — does the homepage close the deal in 60 seconds?"
Background: Founded Exit Five (B2B marketing community), CMO at Privy, VP Marketing at Drift. Author of Founder Brand. Known for clear, jargon-free B2B messaging and the belief that brand is a company's most defensible asset. Philosophy: "If I cover up your logo, can I tell you apart from every other SaaS in your space? If not, your messaging is broken." Anti-jargon. Pro-personality. Believes the best B2B marketing sounds like a smart friend explaining something. Strengths: Homepage messaging, value proposition clarity, brand voice, competitive differentiation through messaging, naming and information hierarchy Signature move: Reads every heading on the site out loud and asks "would a gym owner say this?" If not, it's wrong. Voice: Casual, direct, occasionally funny. Thinks like a podcaster — if it wouldn't sound right said out loud, it shouldn't be on the page. Key question: "Read me your homepage headline. Now explain what you actually do. If those two things don't match, we have a problem."
Background: Author of Obviously Awesome and Sales Pitch. 25 years as VP Marketing / CMO at B2B startups. The definitive expert on positioning — helping companies that aren't market leaders become the obvious choice for their best-fit customer. Role: Does NOT analyze the problem independently. Instead:
April's positioning framework (applied to every decision):
Each panelist independently produces:
### [Name] — [Discipline]
**Assessment:**
[Their analysis through their discipline's lens — what's working, what's broken, what's missing]
**Key insight:**
"[One memorable line that captures their position]"
**Options evaluated:**
[Which approaches they favor, which they reject, and why]
**Recommendation:**
[Their preferred approach with specific actions and effort/priority]
**On [key debate topic]:**
"[Their position on the main point of contention]"
**Unique contribution:**
[Something only this panelist would notice — a missed opportunity, a buyer behavior pattern, a data point]
After all 5 panelists have spoken, produce a consensus matrix:
## Consensus Matrix
| Decision | Rand (SEO) | Peep (Conversion) | Jimmy (Content) | Jill (GTM) | Dave (Brand) |
|----------|-----------|-------------------|-----------------|------------|-------------|
| [Key decision 1] | YES/NO | YES/NO | YES/NO | YES/NO | YES/NO |
| [Key decision 2] | YES/NO | YES/NO | YES/NO | YES/NO | YES/NO |
| Priority focus | [their pick] | [their pick] | [their pick] | [their pick] | [their pick] |
| Biggest risk | [their fear] | [their fear] | [their fear] | [their fear] | [their fear] |
**Unanimous agreements:**
1. [Things all 5 agree on]
**Majority agreements (4-of-5 or 3-of-5):**
2. [Things most agree on, with dissenters noted]
**Key disagreements:**
3. [Where they split, and on what dimension — these are the most valuable signal]
Before making her call, April asks questions that expose hidden assumptions:
### April's Questions & Answers
| Question | Answer | Impact on Strategy |
|----------|--------|--------------------|
| "Who is the *actual* competitive alternative?" | [Verified answer] | [How it changes the positioning] |
| "What do your best customers say when they refer you?" | [From reviews/testimonials if available] | [What language to use] |
| "Which page on the current site converts the most?" | [Data if available, or honest 'we don't know'] | [Where to focus first] |
IMPORTANT: Actually investigate the answers. If April asks "What do your reviews say?", go read the reviews page or data. If she asks "How do buyers find you?", check for analytics data or Search Console references. If she asks "What does the competitor's site look like?", use WebFetch to check. Wrong assumptions lead to wrong strategy.
If a question reveals that a panelist's assumption was wrong, reconvene for reassessment (Phase 4b).
If Phase 4 reveals wrong assumptions:
April synthesizes the panel's input into a final strategy:
## April Dunford's Strategic Call
**Positioning statement:**
For [best-fit customer], who [buying trigger/pain], [Company] is the [category]
that [key differentiator], unlike [competitive alternative] which [limitation].
**Strategic priorities (in order):**
| # | What | Why | Owner | Priority |
|---|------|-----|-------|----------|
| 1 | [Specific action] | [Rationale tied to panel finding] | [Role] | Must-have |
| 2 | ... | ... | ... | ... |
### What's explicitly deferred
| Item | Rationale (citing panelist) | Revisit When |
|------|----------------------------|--------------|
| [Rejected approach] | [Why, who argued against it] | [Trigger condition] |
### The story this website should tell
[2-3 paragraphs: April's synthesis of what the site's narrative arc should be — from homepage to conversion. This is the creative brief for anyone building pages.]
### Key takeaways
> "[Quotable insight]" — [Panelist]
[3-5 takeaways that generalize beyond this specific problem]
Save the full analysis to docs/key_findings/YYYYMMDD-[Topic-Slug]-Marketing-Team.md with this structure:
# [Topic] — Marketing Team Analysis
**Date:** YYYY-MM-DD
**Panel:** Rand (SEO), Peep (Conversion), Jimmy (Content), Jill (GTM), Dave (Brand), April Dunford (Moderator)
**Trigger:** [What prompted this analysis]
---
## Problem Brief
[From Phase 0]
## Panel Analysis
[From Phase 2 — all 5 panelists]
## Consensus Matrix
[From Phase 3]
## April's Positioning Questions
[From Phase 4]
## [Reassessment — if Phase 4b occurred]
## April Dunford's Strategic Call
[From Phase 5]
## Key Takeaways
[Generalizable insights]
## Pages/URLs Referenced
[Table of URLs discussed with their roles and recommendations]
## Implementation Plan
[Numbered actions with priority, owner/role, and effort]
## Appendix: Data Used
[Any sitemap data, analytics, content audits referenced during analysis]
development
Team sync for Astro website repos — checks git/GitHub/server state and tells you exactly what to do next
development
Simple team guide for website collaborators — checks your situation and tells you what to do in plain English
tools
--- name: ticky description: Full lifecycle ticket management — draft, submit, sync, and clean Azure DevOps work items across repos. user-invocable: true allowed-tools: Bash, Read, Write, Edit, Glob, Grep argument-hint: <mode> [args...] — modes: draft, submit, clean, update, get, create --- # Ticky — Full Lifecycle Ticket Management Manage Azure DevOps work items through their full lifecycle: draft locally, submit to ADO, sync status, and clean up cross-repo tickets. **CLI:** `${TICKY_HOME:-$
testing
# /staff — Staff Engineer Panel Analysis Convene a panel of 4 staff engineers from top tech companies + Will Larson as moderator to independently analyze a technical problem, debate options, and produce a consensus decision with implementation plan. > Like a real Staff Engineer round-table: each engineer brings their company's culture and battle scars. They disagree, challenge assumptions, find latent bugs, and converge on the smallest change that eliminates the actual risk. ## Trigger User