arkaos 4.26.0 → 4.27.0

package/config/evals/marketing.yaml

@@ -26,3 +26,3765 @@
     - Meta title/description dentro dos limites de caracteres
   rubric: Rejeitar keyword stuffing ou outline sem lógica de funil.
   tags: [seo, content]
+
+# --- BEGIN imported (marketing-skills, MIT) — regenerated by scripts/tools/evals_import.py ---
+- id: marketing-ab-test-01
+  department: marketing
+  prompt: I want to A/B test our homepage headline. We currently say 'The All-in-One Project
+    Management Tool' and want to test something benefit-focused. We get about 15,000 visitors/month
+    and our current signup rate is 3.2%.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Uses the hypothesis framework with observation, belief, outcome, and metric
+  - Identifies as A/B test type
+  - Addresses sample size calculation based on traffic and baseline rate
+  - Defines primary metric (signup rate)
+  - Defines secondary and guardrail metrics
+  - Warns about the peeking problem
+  - Provides structured test plan output
+  rubric: 'Should check for product-marketing.md first. Should build a proper hypothesis using
+    the framework: ''Because [observation], we believe [change] will cause [outcome], which
+    we''ll measure by [metric].'' Should identify this as an A/B test (two variants). Should
+    calculate or reference sample size needs based on 15,000 monthly visitors and 3.2% baseline.
+    Should define primary metric (signup rate), secondary metrics, and guardrail metrics.
+    Should warn about the peeking problem and recommend a fixed test duration. Should provide
+    the test plan in the structured output format.'
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-02
+  department: marketing
+  prompt: we want to test like 4 different CTA button colors on our pricing page. is that
+    a good idea?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Identifies as A/B/n test (multiple variants)
+  - Cautions about increased traffic needs for 4 variants
+  - References sample size requirements
+  - Questions whether button color alone is high-impact
+  - Suggests alternative higher-impact elements to test
+  - Provides hypothesis framework
+  rubric: Should trigger on casual phrasing. Should identify this as an A/B/n test (multiple
+    variants). Should caution that testing 4 variants requires significantly more traffic
+    than a simple A/B test. Should reference the sample size quick reference showing traffic
+    multipliers for multiple variants. Should question whether button color alone is likely
+    to produce meaningful lift vs testing CTA copy, placement, or surrounding context. Should
+    recommend either reducing to 2 variants or ensuring sufficient traffic. Should still provide
+    hypothesis framework and test setup if proceeding.
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-03
+  department: marketing
+  prompt: Our test has been running for 3 days and Variant B is winning with 95% confidence.
+    Should we call it?
+  expected_properties:
+  - Addresses the peeking problem directly
+  - Explains why early significance is misleading
+  - Recommends running for full pre-calculated duration
+  - Mentions day-of-week effects or audience mix shifts
+  - Explains false positive rate inflation from peeking
+  - Mentions sequential testing as alternative approach
+  rubric: Should immediately address the peeking problem. Should explain that checking results
+    early inflates false positive rates. Should recommend running for the full pre-calculated
+    duration regardless of early results. Should explain why early significance can be misleading
+    (regression to the mean, day-of-week effects, audience mix shifts). Should provide guidance
+    on when it IS appropriate to stop early (sequential testing methods). Should recommend
+    the pre-test commitment to duration.
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-04
+  department: marketing
+  prompt: Help me set up a multivariate test on our landing page. I want to test the headline,
+    hero image, and CTA button simultaneously.
+  expected_properties:
+  - Identifies as multivariate test (MVT)
+  - Explains MVT tests combinations of elements
+  - Addresses dramatically higher traffic requirements
+  - Calculates number of combinations
+  - Suggests sequential A/B tests as alternative if traffic insufficient
+  - Builds hypotheses for each element
+  - Provides structured test plan
+  rubric: 'Should identify this as a Multivariate Test (MVT). Should explain that MVT tests
+    combinations of elements and requires much more traffic than A/B tests. Should calculate
+    or reference traffic needs (combinations multiply: e.g., 2 headlines × 2 images × 2 CTAs
+    = 8 combinations). Should recommend MVT only if traffic supports it, otherwise suggest
+    sequential A/B tests. Should build hypotheses for each element being tested. Should define
+    interaction effects to watch for. Should provide structured test plan.'
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-05
+  department: marketing
+  prompt: What metrics should I track for an A/B test on our trial signup page? We're testing
+    a longer form (adds company size and role fields) against the current short form.
+  expected_properties:
+  - Applies three-tier metric framework (primary, secondary, guardrail)
+  - Identifies form completion rate as primary metric
+  - Identifies lead quality as secondary metric
+  - Defines guardrail metrics to protect against negative outcomes
+  - Explains quantity vs quality tradeoff
+  - Notes need for longer observation window for downstream metrics
+  rubric: 'Should apply the metrics selection framework with three tiers: primary, secondary,
+    and guardrail metrics. Primary: form completion rate (the direct conversion metric). Secondary:
+    lead quality metrics (SQL conversion rate, activation rate post-signup). Guardrail: overall
+    signup volume (ensure longer form doesn''t tank total signups below acceptable threshold).
+    Should explain the tradeoff between conversion quantity and lead quality. Should note
+    that this test needs longer observation window to measure downstream metrics.'
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-06
+  department: marketing
+  prompt: Can you help me write copy for our new landing page? We want to test it against
+    the current version.
+  expected_properties:
+  - Recognizes this as primarily a copywriting task
+  - References or defers to copywriting skill
+  - Does not attempt to write full page copy using test setup patterns
+  - May offer to help with test hypothesis and setup
+  rubric: Should recognize this is primarily a copywriting task, not a test setup task. Should
+    defer to or cross-reference the copywriting skill for writing the actual copy. May help
+    frame the test hypothesis and setup, but should make clear that copywriting is the right
+    skill for creating the page copy itself.
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ab-test-07
+  department: marketing
+  prompt: 'We ran an A/B test on our pricing page for 4 weeks. Control: 2.1% conversion. Variant:
+    2.4% conversion. 12,000 visitors per variant. Is this statistically significant? Should
+    we ship it?'
+  expected_properties:
+  - Evaluates against statistical significance criteria
+  - Addresses whether sample size is sufficient for this effect size
+  - References 95% confidence threshold
+  - Distinguishes statistical significance from practical significance
+  - Provides clear recommendation on shipping
+  - Suggests segment analysis or follow-up if borderline
+  rubric: Should evaluate the results against statistical significance criteria. Should calculate
+    or estimate whether the sample size is sufficient to detect a 0.3 percentage point lift
+    from a 2.1% baseline (this is a ~14% relative lift). Should reference the 95% confidence
+    threshold. Should discuss practical significance vs statistical significance. Should recommend
+    whether to ship, continue testing, or iterate. Should consider segment analysis if results
+    are borderline.
+  tags:
+  - ab-test
+  - imported
+- id: marketing-ad-creative-01
+  department: marketing
+  prompt: 'Generate ad creative for our Meta (Facebook/Instagram) campaign. We sell an AI
+    writing assistant for content marketers. Main value prop: write blog posts 5x faster.
+    Target audience: content marketing managers at B2B SaaS companies. Budget: $5k/month.'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Uses angle-based generation approach
+  - Identifies multiple angles (3-5)
+  - Respects Meta character limits (125/40/30)
+  - Generates multiple variations per angle
+  - Suggests image or visual direction
+  - Includes hook, body, and CTA for each
+  - Recommends which angles to test first
+  rubric: 'Should check for product-marketing.md first. Should generate creative following
+    the angle-based approach: identify 3-5 angles (speed, quality, ROI, pain of blank page,
+    competitive edge). For each angle, should generate primary text (≤125 chars), headline
+    (≤40 chars), and description (≤30 chars) respecting Meta character limits. Should provide
+    multiple variations per angle. Should suggest image/visual direction for each. Should
+    organize output with angle name, hook, body, CTA for each variation. Should recommend
+    which angles to test first.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-02
+  department: marketing
+  prompt: I need Google Ads copy for our CRM product. We're targeting the keyword 'best CRM
+    for small business'. Need responsive search ads.
+  expected_properties:
+  - Respects Google RSA character limits (30 char headlines, 90 char descriptions)
+  - Generates 10-15 headline variations
+  - Generates 4+ description variations
+  - Includes target keyword in headlines
+  - Notes pinning should be used sparingly per skill guidance
+  - Suggests ad extensions
+  - Uses angle-based variation approach
+  rubric: 'Should generate Google RSA creative respecting character limits: headlines (≤30
+    chars each, need 10-15 variations) and descriptions (≤90 chars each, need 4+ variations).
+    Should note that pinning should be used sparingly as it reduces optimization. Should include
+    the target keyword in headlines. Should provide multiple angle-based variations. Should
+    suggest ad extensions (sitelinks, callouts, structured snippets). Should follow Google
+    Ads best practices for RSA.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-03
+  department: marketing
+  prompt: 'Here''s our ad performance data: Ad A (pain point angle) - CTR 2.1%, CPC $3.20,
+    Conv rate 4.5%. Ad B (social proof angle) - CTR 1.4%, CPC $4.10, Conv rate 6.2%. Ad C
+    (feature angle) - CTR 0.8%, CPC $5.50, Conv rate 2.1%. Help me iterate on these.'
+  expected_properties:
+  - Activates iteration mode based on performance data
+  - Analyzes CTR, CPC, and conversion rate for each ad
+  - Identifies winning angles from the data
+  - Recommends pausing or reworking underperforming creative
+  - Generates new variations combining winning elements
+  - Provides specific iterations on top performers
+  rubric: 'Should activate the iteration-from-performance mode (not generate-from-scratch).
+    Should analyze the data: Ad A has best CTR, Ad B has best conversion rate (highest efficiency
+    despite lower CTR), Ad C is underperforming on all metrics. Should recommend doubling
+    down on the pain point angle (high CTR) and social proof angle (high conversion), while
+    pausing or reworking the feature angle. Should generate new variations that combine winning
+    elements (pain point hook + social proof). Should suggest specific iterations on Ad A
+    and Ad B.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-04
+  department: marketing
+  prompt: we need linkedin ads for our enterprise security product. audience is CISOs and
+    IT directors.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Respects LinkedIn character limits (150/70/100)
+  - Adapts tone for enterprise security audience
+  - Uses risk-reduction and compliance language
+  - Provides multiple angles relevant to security buyers
+  - Suggests LinkedIn ad format recommendations
+  rubric: 'Should trigger on casual phrasing. Should generate LinkedIn ad creative respecting
+    character limits: introductory text (≤150 chars), headline (≤70 chars), description (≤100
+    chars). Should adapt tone and messaging for enterprise security audience (CISOs, IT directors)
+    — more formal, compliance-focused, risk-reduction language. Should provide multiple angles
+    relevant to security buyers (risk reduction, compliance, incident response time, cost
+    of breaches). Should suggest ad format recommendations for LinkedIn (sponsored content,
+    message ads, etc.).'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-05
+  department: marketing
+  prompt: I need to generate a big batch of ad variations for a multi-platform campaign launching
+    next week. We're a meal delivery service targeting busy professionals. Need ads for Google,
+    Meta, and TikTok.
+  expected_properties:
+  - Activates batch generation workflow
+  - Generates for all three platforms
+  - Respects each platform's character limits
+  - Identifies angles that work across platforms
+  - Notes TikTok needs video concepts
+  - Organizes output by platform
+  - Generates multiple variations per angle per platform
+  rubric: 'Should activate the batch generation workflow. Should generate creative for all
+    three platforms respecting each platform''s character limits: Google RSA (30/90), Meta
+    (125/40/30), TikTok (80 chars recommended, 100 max). Should identify 3-5 angles that work
+    across platforms (convenience, health, time savings, variety, cost vs eating out). Should
+    generate variations per angle per platform. Should note platform-specific creative considerations
+    (TikTok needs video concepts, not just text). Should organize output clearly by platform.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-06
+  department: marketing
+  prompt: Help me plan our overall paid advertising strategy. We have a $20k monthly budget
+    and want to figure out which platforms to use and how to allocate spend.
+  expected_properties:
+  - Recognizes this as paid ads strategy, not creative generation
+  - References or defers to ads skill
+  - Does not attempt full campaign strategy using creative generation patterns
+  rubric: Should recognize this is a paid advertising strategy task, not ad creative generation.
+    Should defer to or cross-reference the ads skill, which handles campaign strategy, platform
+    selection, and budget allocation. May briefly mention creative considerations but should
+    make clear that ads is the right skill for strategy.
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-07
+  department: marketing
+  prompt: I want to make one of those iMessage-style video ads for Meta — the ones where a
+    fake text conversation reveals the product and a promo code. We sell a sleep tracking
+    ring. Our promo code is RESTED.
+  expected_properties:
+  - Loads or applies the imessage-video-ads reference
+  - Selects a concept angle before writing the script
+  - Script is 8-14 bubbles in authentic texting voice
+  - Brand name appears only after the peer asks about it
+  - Promo code RESTED appears in a bubble and on the end card
+  - Applies grounding rules — no fabricated claims, not framed as a real testimonial
+  - Mentions at least one production route and key craft rules (SFX, silent typing indicator,
+    9:16)
+  rubric: 'Should load references/imessage-video-ads.md. Should start by picking a concept
+    angle from the six-angle catalog (result-as-screenshot, setup flex, cancellation moment,
+    feature-as-punchline, friend-asks-friend inverse, receipt-as-hook) before writing bubbles
+    — likely result-as-screenshot (a sleep score) for this product. Should draft an 8-14 bubble
+    script in real texting voice where the brand appears only after the peer asks, with the
+    RESTED code delivered conversationally inside a bubble and repeated on a static end card.
+    Should apply grounding rules: any sleep-improvement claim in the thread must trace to
+    a real customer result or product fact, and the thread must not be framed as a real testimonial.
+    Should present production route options (off-the-shelf skill, Playwright+ffmpeg pipeline,
+    or Remotion) rather than assuming one, and mention key craft rules (the recognizable send/receive
+    SFX, silent typing indicators, 9:16 1080x1920).'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-08
+  department: marketing
+  prompt: We sell a menopause supplement. I saw those ads where someone asks ChatGPT a health
+    question and the answer recommends the product — make one of those for us. Also curious
+    about the Apple Notes version.
+  expected_properties:
+  - Applies the iOS-native reveal surfaces section of the imessage-video-ads reference
+  - Flags health-claim/substantiation risk for the fabricated ChatGPT answer before or while
+    drafting
+  - Does not present the ChatGPT exchange as a real unprompted output endorsing the product
+  - Recommends legal review or a compliant reframe for health advice in the AI answer
+  - 'Apple Notes guidance: title-as-hook, first-person confession, product as an understated
+    list item, keyboard-taps-only audio'
+  - Grounds claims and realizations in documented facts/reviews (Grounded Inputs)
+  - Gives surface-selection reasoning (ChatGPT vs Notes) instead of treating formats as interchangeable
+  rubric: 'Should load references/imessage-video-ads.md and apply the Other iOS-Native Reveal
+    Surfaces section. Should flag the compliance constraint prominently BEFORE drafting: a
+    fabricated AI answer making health claims is the highest-risk version of this format —
+    every claim needs substantiation, health/medical advice in a fake ChatGPT answer needs
+    legal review, and the exchange must not be presented as a real unprompted ChatGPT output
+    endorsing the product. May propose a compliant angle (mechanism education grounded in
+    documented facts) or steer to the Apple Notes confession format as the lower-risk fit
+    for a transformation story. For the Notes version: title-as-hook, first-person list with
+    the product as the least enthusiastic line, keyboard-taps-only audio, grounding realizations
+    in real reviews. Should apply surface-selection guidance rather than treating the three
+    formats as interchangeable.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-09
+  department: marketing
+  prompt: Our Meta account is stuck — we've tested 30 ads over two months and nothing beats
+    the control. I have our reviews exported and access to our ad account data. Build me a
+    creative plan for next month.
+  expected_properties:
+  - Applies the creative strategy loop (Mode 4) instead of only generating ad copy
+  - Diagnoses exploration state and recommends a wide, net-new-heavy mix with minimal iterations
+  - Redefines wins per-metric for a stuck account
+  - Synthesizes all three signal sources or explicitly requests the missing one
+  - Concepts are evidence-ranked with cited sources (no invented insights)
+  - Monthly slate is capacity-checked and production-tiered, favoring low-fidelity tests
+  - Includes a month-end retro plan that feeds the next slate
+  rubric: 'Should apply Mode 4 / references/creative-roadmap.md rather than jumping straight
+    to generating ads. Should identify the account as exploration state (nothing working)
+    and shape the plan accordingly: mostly net-new concepts across different segments/angles,
+    minimal iterations, per-metric win redefinition (a hold-rate lift or CPC drop counts as
+    a hit worth pulling on). Should synthesize the three signals (account performance from
+    the ad data, customer language from the reviews, external organic — asking for or mining
+    niche organic content) into concepts ranked by evidence tier, each with a cited source.
+    Should produce a capacity-checked monthly slate with production tiers (favoring T1/T2
+    low-fidelity tests per the fidelity ladder) and flag the common exploration-state root
+    causes to check (boring creative, overcomplicated message, unclear UVP, punishing CPMs).
+    Should end with the retro plan for judging the slate at month end. Should not invent customer
+    language or claims — insights must trace to the provided reviews/data.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-10
+  department: marketing
+  prompt: We generated four ad concepts for a client (an organic skincare brand) and need
+    to send them something they can actually look at and approve — with the Instagram preview,
+    the carousel frames, and the different headline options they can compare. Can you put
+    that together?
+  expected_properties:
+  - Produces a creative review page from the HTML template, not plain markdown
+  - Populates the DATA object (concept tabs, in-feed preview, frame storyboard, headline variations,
+    copy, destination)
+  - Labels storyboard frames by narrative job rather than by pictured content
+  - Includes a required grounding/disclosure line per concept; labels illustrative proof as
+    illustrative
+  - Does not present invented stats or stock imagery as the brand's real assets
+  - Uses placeholders for unrendered frames and keeps image paths relative
+  - Explains how to deliver the page (open locally / host / hand off the file)
+  rubric: Should recognize this as a creative review page request and apply references/creative-review-page.md
+    + the assets/creative-review-template.html template rather than producing plain markdown.
+    Should copy the template into the output folder and populate its DATA object with the
+    four concepts as tabs, each with an in-feed Instagram preview, a labeled frame-by-frame
+    storyboard (frames labeled by narrative job — Hook / Problem / Proof / Ask — not by pictured
+    content), selectable headline variations, primary text, and destination/CTA. Should curate
+    to a reviewable number of concepts (2-4) rather than dumping everything. Should include
+    a required grounding disclosure per concept stating what is real (product photography,
+    any claims/results) and label illustrative proof as illustrative — never present invented
+    stats or stock imagery as the brand's own. Should use styled placeholders for frames not
+    yet rendered to image, and keep image paths relative. Should explain how to deliver it
+    (open locally, host on a static host, or hand off the file).
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-ad-creative-11
+  department: marketing
+  prompt: I want to make one of those AirDrop-style video ads — where a phone gets an incoming
+    AirDrop and you tap accept. We sell a limited-run sneaker drop.
+  expected_properties:
+  - Applies the AirDrop iOS-native-reveal surface, not a from-scratch format
+  - Builds around the incoming-AirDrop-card + accept-tap-as-reveal interaction (receiver POV)
+  - Preview thumbnail is treated as the hook that must earn the accept
+  - Casts a relatable human sender name, not the brand, on the incoming card
+  - Uses the AirDrop swoosh sound + Apple trade-dress note, not iMessage tritones
+  - Applies the family grounding/disclosure rules (dramatized share, substantiated claims,
+    not a real endorsement)
+  rubric: 'Should apply the AirDrop surface in references/imessage-video-ads.md (the iOS-native
+    reveal family), not treat it as a novel format. Should build the ad around the interaction:
+    an incoming AirDrop card (translucent sheet, sender device name, a preview thumbnail,
+    gray Decline / blue Accept) from the receiver''s POV, with the Accept tap as the reveal
+    beat and the transfer progress-ring as the signature motion. Should make the preview thumbnail
+    earn the tap (the sneaker money-shot / the drop), cast a relatable human sender name rather
+    than the brand, use the AirDrop swoosh sound (not iMessage tritones) with the Apple trade-dress
+    note, and keep it short. Should apply the family grounding/disclosure rules (a dramatization
+    of a share, not a real endorsement; claims substantiated). May note receiver-POV-by-default
+    vs sender-POV-as-flex.'
+  tags:
+  - ad-creative
+  - imported
+- id: marketing-paid-campaign-01
+  department: marketing
+  prompt: Help me plan a paid advertising strategy. We're a B2B SaaS tool for HR teams, selling
+    at $99/month per seat. We have $15k/month to spend on ads and want to generate demo requests.
+    Where should we advertise?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies platform selection guide
+  - Recommends platforms appropriate for B2B HR audience
+  - Recommends campaign structure with naming conventions
+  - Defines audience targeting per platform
+  - Sets budget allocation across platforms
+  - Defines success metrics
+  - Recommends starting structure and scaling plan
+  rubric: Should check for product-marketing.md first. Should apply the platform selection
+    guide based on B2B, HR audience, $99/month price point. Should recommend LinkedIn (B2B
+    targeting by job title/industry), Google Ads (search intent for HR software keywords),
+    and potentially Meta (retargeting). Should recommend campaign structure with naming conventions.
+    Should define audience targeting strategy for each platform. Should set budget allocation
+    across platforms. Should define success metrics and attribution approach. Should recommend
+    starting structure and scaling plan.
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-paid-campaign-02
+  department: marketing
+  prompt: Our Google Ads CPC is $12 and our cost per lead is $180. Is that good? We're getting
+    about 80 leads/month from a $15k budget.
+  expected_properties:
+  - Evaluates metrics in context
+  - Compares CPL against LTV considerations
+  - Applies campaign optimization framework
+  - Recommends specific optimization levers
+  - Asks about downstream conversion rates
+  - Provides industry context for benchmarking
+  rubric: 'Should evaluate the metrics in context. Should assess: $12 CPC for B2B (reasonable
+    depending on industry), $180 CPL (depends on LTV — need to compare against customer lifetime
+    value), 80 leads/month from $15k (math checks out). Should apply the campaign optimization
+    framework: check quality score, search term relevance, landing page conversion rate, negative
+    keywords. Should recommend specific optimization levers to reduce CPC and CPL. Should
+    frame performance against industry benchmarks if applicable. Should ask about downstream
+    conversion rates (lead → demo → customer).'
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-paid-campaign-03
+  department: marketing
+  prompt: we want to run retargeting ads for people who visited our site but didn't convert.
+    how should we set this up?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies funnel-based retargeting approach
+  - Recommends audience segments by intent level
+  - Recommends different messaging per segment
+  - Addresses frequency capping
+  - Recommends retargeting platforms
+  - Includes audience duration windows
+  rubric: 'Should trigger on casual phrasing. Should apply the retargeting strategies section,
+    specifically the funnel-based approach. Should recommend audience segments: all visitors
+    (broad), pricing page visitors (high intent), blog readers (lower intent), and cart/signup
+    abandoners (highest intent). Should recommend different messaging and offers for each
+    segment. Should address frequency capping to avoid ad fatigue. Should recommend retargeting
+    platforms (Meta, Google Display, LinkedIn). Should include duration windows for each audience.'
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-paid-campaign-04
+  department: marketing
+  prompt: Should we advertise on TikTok? We sell accounting software to small businesses.
+    Our current ads are on Google and Meta.
+  expected_properties:
+  - Applies platform selection guide for TikTok
+  - Evaluates fit for accounting + small business audience
+  - Provides honest assessment of likely weaker fit
+  - Discusses when TikTok can work for B2B
+  - Suggests small test budget if proceeding
+  - Compares to their existing Google/Meta performance
+  rubric: 'Should apply the platform selection guide for TikTok specifically. Should evaluate
+    TikTok fit for accounting software + small business audience: likely a weaker fit than
+    Google/Meta for this category (lower purchase intent, younger skewing audience, less B2B
+    targeting). Should discuss when TikTok CAN work for B2B (brand awareness, creative content,
+    younger business owners). Should provide an honest recommendation with caveats. Should
+    suggest a small test budget approach if they want to try.'
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-paid-campaign-05
+  department: marketing
+  prompt: How do we structure our Google Ads campaigns? We have 50+ keywords we want to target
+    for our CRM product.
+  expected_properties:
+  - Applies campaign structure framework
+  - Organizes campaigns by theme/intent
+  - Recommends tight ad group structure
+  - Defines naming conventions
+  - Recommends match types strategy
+  - Includes negative keyword lists
+  - Provides sample campaign structure
+  rubric: Should apply the campaign structure and naming conventions framework. Should recommend
+    organizing campaigns by theme/intent (brand, competitor, product features, pain points).
+    Should recommend ad group structure (tightly themed, 5-15 keywords per group). Should
+    define naming conventions for campaigns and ad groups. Should recommend match types strategy.
+    Should include negative keyword lists. Should provide a sample campaign structure.
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-paid-campaign-06
+  department: marketing
+  prompt: Can you write some ad copy for our Facebook ads? We need headlines and descriptions
+    for 5 different angles.
+  expected_properties:
+  - Recognizes this as ad creative generation
+  - References or defers to ad-creative skill
+  - Does not attempt bulk ad copy generation using campaign strategy patterns
+  rubric: Should recognize this is an ad creative generation task, not campaign strategy.
+    Should defer to or cross-reference the ad-creative skill, which handles platform-specific
+    ad copy generation with character limits, angle-based variation, and batch generation.
+    May provide brief ad copy framework guidance but should make clear that ad-creative is
+    the right skill for generating ad copy at scale.
+  tags:
+  - paid-campaign
+  - imported
+- id: marketing-ai-seo-01
+  department: marketing
+  prompt: How do I make sure our SaaS product shows up in AI search results? We're a project
+    management tool and we keep getting left out of ChatGPT and Perplexity recommendations
+    when people ask about project management software.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies three pillars framework (Structure, Authority, Presence)
+  - Runs AI Visibility Audit across platforms
+  - Checks content extractability
+  - References Princeton GEO research findings
+  - Checks AI bot access in robots.txt
+  - Provides prioritized action plan
+  rubric: 'Should check for product-marketing.md first. Should apply the three pillars framework:
+    Structure (make content extractable), Authority (make content citable), Presence (be where
+    AI looks). Should run through the AI Visibility Audit checklist across platforms (Google
+    AI Overviews, ChatGPT, Perplexity, etc.). Should check content extractability (clear definitions,
+    structured comparisons, statistics). Should reference Princeton GEO research findings
+    (citations improve visibility +40%, statistics +37%). Should check AI bot access in robots.txt.
+    Should provide a prioritized action plan.'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-02
+  department: marketing
+  prompt: Should we block AI crawlers like GPTBot and PerplexityBot in our robots.txt? We're
+    worried about content theft.
+  expected_properties:
+  - Addresses the blocking tradeoff directly
+  - Explains impact on AI visibility vs content protection
+  - Lists specific AI bot user agents
+  - Provides recommended robots.txt configuration
+  - Gives nuanced recommendation based on business goals
+  - Explains what each bot does
+  rubric: 'Should address the AI bot access question directly. Should explain the tradeoff:
+    blocking AI bots prevents training on your content but also prevents AI platforms from
+    citing and recommending you. Should reference the specific bots and their purposes (GPTBot,
+    Google-Extended, PerplexityBot, ClaudeBot, etc.). Should provide the recommended robots.txt
+    configuration. Should explain that blocking may hurt AI visibility more than it protects
+    content. Should provide a nuanced recommendation based on business goals.'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-03
+  department: marketing
+  prompt: What kind of content gets cited most by AI systems? We want to create content specifically
+    optimized for AI search.
+  expected_properties:
+  - References specific content types with citation rates
+  - Mentions comparisons as highest-cited format
+  - Explains why these formats work for AI
+  - Provides specific content creation recommendations
+  - References Princeton GEO research
+  - Mentions structured data, statistics, and clear definitions
+  rubric: 'Should reference the content types that get cited most, including comparisons (~33%
+    of AI citations), definitive guides (~15%), and other high-citation content types. Should
+    explain why these formats work (they provide the structured, extractable, authoritative
+    information AI systems need). Should provide specific recommendations for creating AI-optimized
+    content: clear definitions, structured data, original statistics, comparison tables, expert
+    quotes. Should reference the Princeton GEO research on what increases citation probability.'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-04
+  department: marketing
+  prompt: we noticed our competitors are showing up in google AI overviews but we're not.
+    what do we need to change?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Focuses on Google AI Overviews specifically
+  - Explains how AI Overviews selects sources
+  - Checks Structure pillar (extractability, headings, answer-first)
+  - Checks Authority signals
+  - Recommends specific content structure changes
+  - Suggests monitoring approach
+  rubric: 'Should trigger on casual phrasing. Should focus specifically on Google AI Overviews
+    visibility. Should explain how AI Overviews selects sources (authoritative, well-structured,
+    directly answers queries). Should run through the Structure pillar checklist: content
+    extractability, heading hierarchy, answer-first format, structured data. Should check
+    Authority signals: domain authority, citations, E-E-A-T. Should recommend specific content
+    structure changes. Should suggest monitoring approach.'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-05
+  department: marketing
+  prompt: Can you audit our website for AI search readiness? We want to know how visible we
+    are across ChatGPT, Perplexity, Google AI Overviews, and other AI platforms.
+  expected_properties:
+  - Runs full AI Visibility Audit
+  - Checks multiple AI platforms
+  - Evaluates all three pillars (Structure, Authority, Presence)
+  - Checks content extractability
+  - Checks AI bot access
+  - Provides findings organized by pillar
+  - Provides prioritized action plan
+  rubric: 'Should run the full AI Visibility Audit. Should check each platform in the landscape
+    (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot). Should evaluate all
+    three pillars: Structure (content extractability, JSON-LD, clear definitions), Authority
+    (citations, backlinks, E-E-A-T signals), Presence (AI bot access, platform-specific factors).
+    Should provide findings organized by pillar. Should provide a prioritized action plan
+    with specific fixes.'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-06
+  department: marketing
+  prompt: Our organic search traffic has dropped 30% this quarter. Can you do a full SEO audit
+    to figure out what's going on?
+  expected_properties:
+  - Recognizes this as a traditional SEO audit request
+  - References or defers to seo-audit skill
+  - Does not attempt a full traditional SEO audit using AI SEO patterns
+  - May mention AI search as one factor to consider
+  rubric: Should recognize this is a traditional SEO audit request, not specifically an AI
+    SEO task. Should defer to or cross-reference the seo-audit skill, which handles comprehensive
+    traditional SEO audits including crawlability, technical foundations, on-page optimization,
+    and content quality. May mention AI search as one factor to investigate but should make
+    clear that seo-audit is the primary skill for this task.
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-ai-seo-07
+  department: marketing
+  prompt: 'We''re a seed-stage data-quality startup (barely anyone knows us yet). Plan: publish
+    20 ''best data quality tools'' style listicles ranking ourselves #1 so ChatGPT and AI
+    Overviews recommend us. Good idea?'
+  expected_properties:
+  - Does not endorse 20 self-ranked listicles as a path to AI recommendations for a low-authority
+    brand
+  - Distinguishes citations from recommendations with the different governing criteria
+  - References the visibility ladder (retrieved/cited/mentioned/recommended)
+  - Warns the guides may surface competitors in AI answers (vote-for-competitors mechanism)
+  - Recommends offsite consensus building (reviews, communities, analysts, or PR) as the recommendation
+    lever
+  - Does not tell the user to stop publishing buyer's guides entirely — reframes expectations
+    toward citation and category framing
+  - 'Mentions the attribution blind spot and at least two of: prompt tracking, self-reported
+    attribution, call recordings'
+  rubric: 'Should apply references/citations-vs-recommendations.md rather than endorsing the
+    plan as-is. Should explain the citation vs. recommendation distinction — self-promotional
+    listicles from low-authority brands often earn citations while the AI answer recommends
+    the competitors named in the guide instead (cites the study directionally: ~69% of self-promotional
+    listicle citations — 224 of 323 — excluded the publisher from recommendations). Should
+    present the visibility ladder (retrieved → cited → mentioned → recommended) and explain
+    recommendation is governed by offsite consensus (reviews, forums, analysts, press). Should
+    NOT say ''don''t publish guides'' — should reframe: publish a small number of genuinely
+    useful guides for category framing, and rebalance investment toward reviews/communities/earned
+    media. Should mention the attribution blind spot (AI-influenced visits mostly appear as
+    branded search/direct; only a small share is visible AI traffic) and the measurement triad
+    (prompt tracking, self-reported attribution, call recordings).'
+  tags:
+  - ai-seo
+  - imported
+- id: marketing-analytics-report-01
+  department: marketing
+  prompt: Help me set up analytics tracking for our B2B SaaS product. We use GA4 and GTM.
+    We need to track signups, feature usage, and upgrade events.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies 'track for decisions' principle
+  - Uses object_action naming convention
+  - Defines essential SaaS events (signup, feature usage, upgrade)
+  - Provides GA4 implementation details
+  - Includes GTM data layer examples
+  - Output follows tracking plan format
+  rubric: 'Should check for product-marketing.md first. Should apply the ''track for decisions''
+    principle — ask what decisions the tracking will inform. Should use the event naming convention
+    (object_action, lowercase with underscores). Should define essential events for SaaS:
+    signup_completed, trial_started, feature_used, plan_upgraded, etc. Should provide GA4
+    implementation details with proper event parameters. Should include GTM data layer push
+    examples. Should organize output as a tracking plan with event name, trigger, parameters,
+    and purpose for each event.'
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-analytics-report-02
+  department: marketing
+  prompt: What UTM parameters should we use? We run ads on Google, Meta, and LinkedIn, plus
+    send a weekly newsletter and post on LinkedIn organically.
+  expected_properties:
+  - Applies UTM parameter strategy
+  - Defines source, medium, and campaign conventions
+  - Provides specific UTM examples for each channel
+  - Uses consistent naming conventions (lowercase)
+  - Warns about common UTM mistakes
+  - Recommends tracking documentation
+  rubric: 'Should apply the UTM parameter strategy framework. Should define consistent UTM
+    conventions: source (google, meta, linkedin, newsletter), medium (cpc, paid-social, email,
+    organic-social), campaign (naming convention with date or identifier). Should provide
+    specific UTM examples for each channel mentioned. Should warn about common UTM mistakes
+    (inconsistent casing, redundant parameters, missing medium). Should recommend a UTM tracking
+    spreadsheet or naming convention document.'
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-analytics-report-03
+  department: marketing
+  prompt: our tracking seems broken — we're seeing duplicate events and our conversion numbers
+    in GA4 don't match what our database shows. help?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies debugging and validation framework
+  - Checks for duplicate tag firing
+  - Provides specific debugging tools (GA4 DebugView, GTM Preview)
+  - Addresses GA4 vs database discrepancy
+  - Lists common causes of data mismatches
+  - Provides systematic troubleshooting steps
+  rubric: 'Should trigger on casual phrasing. Should apply the debugging and validation framework.
+    Should systematically check for common issues: duplicate GTM tags firing, missing event
+    deduplication, incorrect trigger conditions, cross-domain tracking issues, consent mode
+    filtering. Should provide specific debugging steps: use GA4 DebugView, GTM Preview mode,
+    browser developer tools. Should address the GA4 vs database discrepancy (common causes:
+    consent mode, ad blockers, client-side vs server-side tracking, session timeout differences).'
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-analytics-report-04
+  department: marketing
+  prompt: We're launching an e-commerce store and need to set up tracking from scratch. What
+    events do we absolutely need?
+  expected_properties:
+  - References essential events for e-commerce site type
+  - Defines full e-commerce event taxonomy
+  - Includes enhanced e-commerce parameters
+  - Follows object_action naming convention
+  - Organizes by priority (must-have vs nice-to-have)
+  - Provides tracking plan format output
+  rubric: 'Should reference the essential events by site type, specifically e-commerce. Should
+    define the e-commerce event taxonomy: product_viewed, product_added_to_cart, cart_viewed,
+    checkout_started, checkout_step_completed, purchase_completed, product_removed_from_cart.
+    Should include enhanced e-commerce parameters (item_id, item_name, price, quantity, etc.).
+    Should follow object_action naming convention. Should organize as a tracking plan with
+    priorities (must-have vs nice-to-have).'
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-analytics-report-05
+  department: marketing
+  prompt: We need to make sure our tracking is GDPR compliant. We have European users and
+    we're using GA4, Hotjar, and Facebook Pixel.
+  expected_properties:
+  - Applies privacy and compliance framework
+  - Addresses GDPR requirements specifically
+  - Recommends consent management platform
+  - Covers GA4 consent mode configuration
+  - Addresses conditional loading for each tool
+  - Provides consent hierarchy
+  - Mentions data retention settings
+  rubric: 'Should apply the privacy and compliance framework. Should address GDPR requirements
+    for each tool: consent before tracking, consent management platform (CMP) setup, GA4 consent
+    mode configuration, conditional loading of Hotjar and Facebook Pixel. Should recommend
+    a consent hierarchy (necessary, analytics, marketing). Should provide GTM implementation
+    for consent-based tag firing. Should mention data retention settings in GA4. Should address
+    cookie banner requirements.'
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-analytics-report-06
+  department: marketing
+  prompt: Help me set up tracking for our A/B test. We want to measure which version of our
+    pricing page converts better.
+  expected_properties:
+  - Recognizes overlap with A/B test setup
+  - References or defers to ab-testing skill
+  - May help with tracking implementation specifics
+  - Does not attempt to design the full experiment
+  rubric: Should recognize this overlaps with A/B test setup, not just analytics tracking.
+    Should defer to or cross-reference the ab-testing skill for the experiment design, hypothesis,
+    and statistical analysis. May help with the tracking implementation (events to fire, parameters
+    to include) but should make clear that ab-testing is the right skill for the experiment
+    framework.
+  tags:
+  - analytics-report
+  - imported
+- id: marketing-aso-01
+  department: marketing
+  prompt: 'Here''s our app on the App Store: https://apps.apple.com/us/app/example/id123456789.
+    Can you audit our listing and tell me what to fix?'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies as Apple App Store URL
+  - Classifies brand maturity tier
+  - Scores all 6 dimensions with weights
+  - Provides scorecard with grade
+  - Lists top 3 quick wins
+  - Recommendations include character counts
+  - Recommendations are specific (X to Y format)
+  rubric: Should check for product-marketing.md first. Should detect this is an Apple App
+    Store URL and run the full ASO audit workflow. Should fetch the listing and extract Apple-specific
+    fields (title 30 chars, subtitle 30 chars, description, promotional text 170 chars, category,
+    screenshots, video, ratings). Should classify the app's brand maturity tier (Dominant/Established/Challenger)
+    before scoring. Should score all 6 dimensions (Title & Subtitle 20%, Description 15%,
+    Visual Assets 25%, Ratings & Reviews 20%, Metadata & Freshness 10%, Conversion Signals
+    10%) with weighted total out of 100 and a grade. Should output a scorecard, top 3 quick
+    wins, detailed findings, keyword suggestions, visual recommendations, and prioritized
+    action plan with specific 'change X from Y to Z' recommendations including character counts.
+  tags:
+  - aso
+  - imported
+- id: marketing-aso-02
+  department: marketing
+  prompt: We're a small fintech startup with about 5,000 downloads. Our Play Store listing
+    has a 2.8 rating and we haven't updated the description in 8 months. Help us figure out
+    what to fix first.
+  expected_properties:
+  - Identifies as Google Play app
+  - Classifies as Challenger tier
+  - Flags rating below 4.0
+  - Flags stale update (>3 months)
+  - Notes Google Play indexes full description
+  - Mentions feature graphic requirement
+  - Recommends keyword strategy in description
+  - Prioritizes rating improvement
+  rubric: 'Should recognize this as a Challenger-tier Google Play app. Should immediately
+    flag the always-flag issues: rating below 4.0 (critical), last update >3 months ago. Should
+    apply strict Challenger scoring against textbook best practices. Should focus on Google
+    Play-specific guidance: full description is indexed for search (target 2-3% keyword density),
+    no hidden keyword field, feature graphic required (1024x500), max 8 screenshots, Android
+    Vitals affect ranking. Should prioritize fixing the rating issue (response strategy, in-app
+    review prompts) and refreshing the description with keyword strategy. Should recommend
+    updating the listing soon to break the >3 month stale signal.'
+  tags:
+  - aso
+  - imported
+- id: marketing-aso-03
+  department: marketing
+  prompt: Instagram's App Store listing has just 'Instagram' as the title and barely any keywords.
+    Should they fix that?
+  expected_properties:
+  - Classifies Instagram as Dominant tier
+  - Explains brand-only titles are valid for Dominant
+  - Does NOT flag the title as a problem
+  - Contrasts Dominant vs Challenger treatment
+  - Cites the 'mistake vs deliberate choice' principle
+  rubric: 'Should classify Instagram as a Dominant-tier app and apply tier-adjusted scoring.
+    Should explain that brand-only titles are valid for Dominant apps (score 8+ if brand IS
+    the keyword) because users search by brand name, not generic keywords. Should NOT flag
+    this as a missed opportunity. Should explain the key principle: ''Is this a mistake or
+    a deliberate choice by a team that has data I don''t?'' Should note that other dimensions
+    (screenshots, description, what''s new) are also evaluated against tier — lifestyle/brand
+    photography and brief release notes are acceptable for Dominant apps. Should contrast
+    with what would be a problem for a Challenger app.'
+  tags:
+  - aso
+  - imported
+- id: marketing-aso-04
+  department: marketing
+  prompt: 'Compare our app https://apps.apple.com/us/app/ourapp/id111 against these two competitors:
+    https://apps.apple.com/us/app/competitor1/id222 and https://apps.apple.com/us/app/competitor2/id333'
+  expected_properties:
+  - Scores all 3 apps with same framework
+  - Builds comparison table
+  - Identifies where user's app is weaker
+  - Identifies keyword gaps vs competitors
+  - Produces competitor-informed action list
+  rubric: Should run Phase 3 competitor comparison. Should fetch and score all three apps
+    with the same 6-dimension framework. Should build a side-by-side comparison table highlighting
+    where the user's app is weaker or stronger across each dimension. Should identify keyword
+    gaps — terms competitors target that the user's app doesn't. Should produce a prioritized
+    list of competitor-informed changes. Should call out platform-specific considerations
+    consistently across all three apps.
+  tags:
+  - aso
+  - imported
+- id: marketing-aso-05
+  department: marketing
+  prompt: We only have 3 screenshots and no preview video. Does this really matter that much?
+  expected_properties:
+  - Notes Visual Assets is 25% of score
+  - Cites first 3 screenshots are most important
+  - Mentions screenshot caption indexing (Apple, 2025)
+  - Cites video conversion lift benchmark
+  - Notes Google Play video has lower ROI
+  - Recommends specific screenshot count and video specs
+  - Flags <5 screenshots as always-flag issue
+  rubric: 'Should explain that screenshot count and video presence are heavily weighted in
+    the Visual Assets dimension (25% of total score). Should cite specific data: Apple allows
+    up to 10 screenshots per device with the first 3 visible in search, and 90% of users never
+    scroll past the 3rd. Should note Apple screenshot captions are indexed for search since
+    June 2025. Should cite the conversion benchmark: app preview video delivers +20-40% conversion
+    lift on iOS (note Google Play video has lower ROI — only ~6% tap play). Should recommend
+    adding 5-8 screenshots minimum with caption text, and a 15-30s preview video. Should flag
+    fewer than 5 screenshots as an always-flag issue across all tiers.'
+  tags:
+  - aso
+  - imported
+- id: marketing-aso-06
+  department: marketing
+  prompt: Should I run a Custom Product Page experiment on iOS for our paid search campaigns?
+  expected_properties:
+  - Identifies Custom Product Pages as iOS-specific
+  - Cites +5.9% conversion lift benchmark
+  - Explains CPP can match traffic source intent
+  - Cross-references ab-testing or ads skill
+  - Notes Google Play equivalents
+  rubric: 'Should reference Apple-specific facts: Custom Product Pages (CPP) — up to 70 —
+    appear in organic search since July 2025 with +5.9% average conversion lift. Should explain
+    CPPs let you test variants of screenshots, video, and promotional text against specific
+    traffic sources (e.g., paid search keywords). Should recommend matching CPP variants to
+    the keyword intent for the campaign. Should cross-reference the ab-testing skill for proper
+    experiment design and the ads skill for the campaign side. Should note this is an iOS-only
+    feature (Google Play has Store Listing Experiments and Custom Store Listings as equivalents).'
+  tags:
+  - aso
+  - imported
+- id: marketing-co-marketing-01
+  department: marketing
+  prompt: We make a project management tool for design agencies. Who should we look for as
+    co-marketing partners?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies same persona / different problem characteristic
+  - Suggests specific partner categories in workflow
+  - Mentions Crossbeam or account overlap data
+  - Lists multiple sources to find partners
+  - Applies scoring criteria
+  rubric: 'Should check for product-marketing.md first. Should apply the Partner Identification
+    Framework with audience overlap analysis. Should identify ideal partner characteristics:
+    same buyer persona (design agencies), different problem solved, adjacent in the workflow.
+    Should suggest specific partner categories: design tools (Figma, Adobe), proposal/contract
+    tools (Bonsai, HoneyBook), client communication (Notion, Slack), invoicing/payments (Stripe,
+    FreshBooks), file storage/handoff (Dropbox, Frame.io). Should recommend audience scoring
+    criteria. Should suggest sources to find partners: integration ecosystem, Crossbeam/Reveal
+    for account overlap, customer surveys, G2/Capterra category neighbors, podcasts/newsletters
+    they sponsor.'
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-co-marketing-02
+  department: marketing
+  prompt: We're partnering with a competitor — wait, not a competitor, a complementary CRM
+    company. Help us brainstorm 5 campaign ideas we could run together.
+  expected_properties:
+  - Applies brainstorming framework
+  - Proposes campaigns across multiple types (content, events, integration, community)
+  - Suggests specific actionable ideas
+  - Mentions integration or 'better together' angle
+  - Uses brainstorming prompts
+  rubric: 'Should apply the brainstorming framework: shared audience moments, combined value
+    propositions, unique assets each brings. Should propose campaign ideas across multiple
+    types from the campaign type tables (content partnerships, webinars/events, product/integration
+    marketing, community/social). Should suggest specific ideas like: co-authored blog post
+    or research report, joint webinar, ''better together'' integration landing page, joint
+    case study with shared customer, integration launch, bundle/discount, conference booth
+    sharing. Should ask the campaign idea prompts to spark ideas: what would we create if
+    we had to launch in 2 weeks, what content do both audiences desperately need, what data
+    do we both have that would make a compelling story.'
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-co-marketing-03
+  department: marketing
+  prompt: Draft a cold outreach email to a potential co-marketing partner. They're a content
+    management platform and we make a marketing analytics tool. Both serve B2B marketing teams.
+  expected_properties:
+  - Includes subject with both company names
+  - Specific observation about audience overlap
+  - Includes one concrete campaign idea
+  - Includes clear ask for a call
+  - Keeps it short and personal
+  - Mentions what to prepare for the call
+  rubric: 'Should use the cold outreach template structure. Should include: subject line with
+    both company names, brief role intro, specific observation about audience overlap (not
+    generic), one concrete campaign idea (not ''let''s do something''), clear ask for a quick
+    call. Should keep it short and personal. Should optionally mention call prep: account
+    overlap data (Crossbeam/Reveal), 2-3 specific campaign ideas, audience metrics, past partnership
+    examples, clear ask of what''s wanted and what''s offered.'
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-co-marketing-04
+  department: marketing
+  prompt: We've identified 5 potential partners but only have time for one campaign this quarter.
+    How should we pick?
+  expected_properties:
+  - Applies partner scoring criteria
+  - Includes all 6 scoring dimensions
+  - Weights by goal
+  - Considers ease of execution / partnership history
+  - Recommends starting with low-effort format
+  rubric: 'Should apply the partner scoring criteria: audience fit, audience size, brand alignment,
+    engagement quality, reciprocity potential, ease of execution. Should recommend scoring
+    each partner 1-5 across these criteria. Should weight by current goal (e.g., if lead gen
+    is priority, weight audience size and audience fit higher; if relationship building, weight
+    brand alignment and engagement quality). Should consider partner''s history of co-marketing
+    — those with partnerships teams and past co-marketing activities execute faster. Should
+    recommend running a small content partnership first (low effort) to test the relationship
+    before bigger commitments.'
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-co-marketing-05
+  department: marketing
+  prompt: Our partnership webinar with another SaaS company got 200 signups. How do we split
+    the leads?
+  expected_properties:
+  - Explains lead split options
+  - Recommends documenting in agreement
+  - Lists agreement components
+  - Mentions measuring lead quality not just volume
+  - Recommends post-campaign debrief
+  rubric: 'Should address the lead handling question from the Structuring the Partnership
+    section. Should explain common splits: each partner keeps their own registrations (cleanest
+    but loses cross-pollination), all leads shared between both (max reach, requires clear
+    MQL/SQL handoff), split by audience source (your list vs theirs). Should recommend documenting
+    this in advance in a co-marketing agreement covering campaign description, responsibilities,
+    timeline, lead handling, promotion, branding, costs, metrics sharing. Should note measuring
+    success: leads generated per partner, lead quality (MQL/SQL conversion rate), revenue
+    attributed. Should recommend a post-campaign debrief and discussing future collaboration
+    if it worked.'
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-co-marketing-06
+  department: marketing
+  prompt: Our customer success team wants us to launch a referral program. Can you help us
+    design one?
+  expected_properties:
+  - Recognizes this is customer referral, not co-marketing
+  - Defers to referrals skill
+  - Distinguishes co-marketing from referral programs
+  - Does not attempt full co-marketing strategy
+  rubric: Should recognize this is about customer referrals, not co-marketing between companies.
+    Should redirect to the referrals skill, which specifically handles customer referral and
+    affiliate programs (customers referring customers). Should note co-marketing is partner-to-partner
+    marketing while referrals is customer-driven word-of-mouth. May offer brief co-marketing
+    context if it's relevant to the strategy, but should make clear referrals is the right
+    skill for the task.
+  tags:
+  - co-marketing
+  - imported
+- id: marketing-cold-email-01
+  department: marketing
+  prompt: 'Write a cold email to VP of Marketing at mid-size B2B SaaS companies. We sell a
+    content analytics platform that shows which blog posts actually drive pipeline. Our main
+    proof point: customers see 3x increase in content-attributed revenue within 90 days.'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Writes like a peer, not a vendor
+  - Uses a structure framework from the skill
+  - Subject line is short, lowercase, internal-looking
+  - Every sentence earns its place (concise)
+  - Personalization connects to prospect's problem
+  - Uses proof point as social proof
+  - CTA is low-friction
+  - Provides 2-3 variations
+  rubric: Should check for product-marketing.md first. Should write like a peer, not a vendor.
+    Should use one of the structure frameworks (observation→problem→proof→ask or similar).
+    Subject line should be 2-4 words, lowercase, internal-looking. Every sentence should earn
+    its place. Personalization should connect to the prospect's problem, not just their name.
+    Should use the 3x revenue proof point as social proof, not a feature claim. CTA should
+    be low-friction (not 'book a demo'). Should provide 2-3 variations. Should include a quality
+    check against the guidelines.
+  tags:
+  - cold-email
+  - imported
+- id: marketing-cold-email-02
+  department: marketing
+  prompt: Help me write a cold email to CTOs at enterprise companies. I sell cybersecurity
+    training. My current email has a 2% open rate and 0% reply rate.
+  expected_properties:
+  - Diagnoses problems from the performance data
+  - Identifies subject line as likely open rate issue
+  - Applies voice calibration for CTO audience
+  - Subject line is short, lowercase, internal-looking
+  - Adapts tone for enterprise audience
+  - Uses structure framework from the skill
+  - Explains why each element works
+  rubric: Should diagnose the current email's likely problems based on 2% open rate (subject
+    line issue) and 0% reply rate (body/relevance issue). Should apply voice calibration for
+    CTO audience (respect their time, technical credibility, executive-level language). Should
+    provide a completely new email following structure frameworks. Subject line should be
+    2-4 words, look internal. Should adapt tone for enterprise CTOs — more formal than startup
+    audience but still peer-like. Should provide the email plus analysis of why each element
+    works.
+  tags:
+  - cold-email
+  - imported
+- id: marketing-cold-email-03
+  department: marketing
+  prompt: write me a follow-up sequence. prospect didn't reply to my first email about our
+    HR software. how many should I send and how far apart?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Recommends 3-5 follow-up emails
+  - Each follow-up adds something new
+  - Does not use 'just bumping' or 'checking in' language
+  - Provides timing between emails
+  - Provides actual copy for each follow-up
+  - Includes a breakup email
+  - Follow-ups get progressively shorter
+  rubric: 'Should trigger on casual phrasing. Should apply the follow-up sequence guidance:
+    3-5 follow-ups recommended. Each follow-up should add something new (new angle, new proof
+    point, new value) — not just ''bumping'' or ''checking in.'' Should provide timing recommendations
+    between emails. Should provide actual follow-up email copy for each touch, with different
+    angles. Should include a breakup email at the end. Should note that each follow-up should
+    be shorter than the previous.'
+  tags:
+  - cold-email
+  - imported
+- id: marketing-cold-email-04
+  department: marketing
+  prompt: 'Review this cold email and tell me what''s wrong: ''Dear Sir/Madam, I hope this
+    email finds you well. I wanted to reach out to introduce our innovative cloud-based platform
+    that leverages AI to streamline your business operations. We have helped over 500 companies
+    transform their workflows. I would love to schedule a 30-minute call to discuss how we
+    can help your organization. Best regards, John'''
+  expected_properties:
+  - Identifies lack of personalization
+  - Identifies filler phrases
+  - Identifies jargon and buzzwords
+  - Identifies vendor language vs peer language
+  - Identifies CTA as too high-friction
+  - Notes email is sender-focused not prospect-focused
+  - Provides a rewritten version
+  - Rewrite follows cold email principles
+  rubric: 'Should apply the quality check framework. Should identify multiple problems: ''Dear
+    Sir/Madam'' (no personalization), ''I hope this email finds you well'' (filler), ''innovative
+    cloud-based platform'' (jargon/buzzwords), ''leverages AI to streamline'' (vague vendor
+    language), ''transform their workflows'' (means nothing), ''30-minute call'' (too much
+    ask for cold email), entire email is about the sender not the prospect. Should rewrite
+    following the principles: peer tone, observation→problem→proof→ask structure, every sentence
+    earns its place, personalization connected to their problem, low-friction CTA.'
+  tags:
+  - cold-email
+  - imported
+- id: marketing-cold-email-05
+  department: marketing
+  prompt: What are the best subject lines for cold emails? I want to maximize open rates.
+  expected_properties:
+  - Applies subject line guidelines (2-4 words, lowercase, internal-looking)
+  - Provides specific examples
+  - Explains why the format works
+  - Warns against common bad subject line patterns
+  - Notes distinction between open rate and reply rate
+  rubric: 'Should apply the subject line guidelines: short (2-4 words), lowercase or sentence
+    case, internal-looking (should look like it came from a colleague, not a vendor). Should
+    provide examples following these principles. Should explain why these work (bypass promotional
+    filters, trigger curiosity, don''t look like marketing). Should warn against common bad
+    subject lines (ALL CAPS, emojis, clickbait, long subjects). Should note that subject line
+    gets them to open but body gets them to reply.'
+  tags:
+  - cold-email
+  - imported
+- id: marketing-cold-email-06
+  department: marketing
+  prompt: Can you help me set up an automated email drip campaign for leads who download our
+    whitepaper?
+  expected_properties:
+  - Recognizes this as lifecycle/nurture email, not cold outreach
+  - References or defers to emails skill
+  - Explains the distinction between cold email and lifecycle email
+  - Does not attempt to design a nurture sequence using cold email patterns
+  rubric: Should recognize this is a lifecycle/nurture email sequence, not cold outreach.
+    Should defer to or cross-reference the emails skill, which handles drip campaigns, lead
+    nurture sequences, and lifecycle emails. Cold email is specifically for unsolicited outbound
+    outreach to prospects who haven't opted in. Should make this distinction clear.
+  tags:
+  - cold-email
+  - imported
+- id: marketing-competitor-profile-01
+  department: marketing
+  prompt: 'Profile these three competitors for us: https://competitor1.com, https://competitor2.com,
+    https://competitor3.com. We need this for sales enablement and to find positioning gaps.'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Runs all three phases (scraping, SEO data, synthesis)
+  - Saves raw data to competitor-profiles/raw/ with date subfolder
+  - Produces individual profile per competitor
+  - Produces _summary.md after individual profiles
+  - Uses consistent metrics across competitors
+  - Parallelizes scraping when possible
+  rubric: 'Should check for product-marketing.md first. Should run the full research process:
+    Phase 1 site scraping (Firecrawl map + scrape of homepage, pricing, features, about, customers,
+    integrations, changelog), Phase 2 SEO and market data (DataForSEO for backlinks, ranked
+    keywords, traffic, competitors), Phase 3 synthesis. Should save raw data to competitor-profiles/raw/<slug>/<YYYY-MM-DD>/
+    with scrapes/, seo/, reviews/ subfolders before synthesizing. Should produce one markdown
+    file per competitor following the profile template (At a Glance, Positioning & Messaging,
+    Product & Features, Pricing, Customers & Social Proof, SEO & Content Strategy, Strengths
+    & Weaknesses, Competitive Implications). Should produce a _summary.md after individual
+    profiles with comparison table, positioning map, key takeaways, gaps and opportunities.
+    Should parallelize scraping when handling multiple competitors and use consistent metrics
+    across all three for comparability.'
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-profile-02
+  department: marketing
+  prompt: We have 12 competitors. Profile all of them.
+  expected_properties:
+  - Recommends prioritization over profiling all 12
+  - Suggests top 5 based on relevance
+  - Defaults to quick scan for large list
+  - Explains quick scan vs deep profile difference
+  - Asks user to prioritize
+  rubric: 'Should recommend prioritizing rather than profiling all 12. Should suggest profiling
+    the top 5 first based on domain overlap or market similarity (handling-multiple-competitors
+    guidance). Should default to quick scan mode for a list this size, not deep profile. Should
+    explain the difference: quick scan covers homepage + pricing + domain rank overview +
+    ranked keywords summary, deep profile adds reviews, technology stack, backlink details.
+    Should offer deep profile only if user requests or for 3 or fewer competitors. Should
+    ask which competitors are highest priority if user wants to narrow further.'
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-profile-03
+  department: marketing
+  prompt: I have an existing profile of Notion from 4 months ago. Should I update it or start
+    fresh?
+  expected_properties:
+  - Recommends updating over starting fresh
+  - Lists what to re-pull (pricing, SEO, changelog)
+  - Mentions adding Change Log section
+  - Says to save raw data to new date folder
+  - Says never overwrite prior date's data
+  rubric: 'Should explain profile updating process from the Updating Profiles section. Should
+    recommend updating rather than starting fresh — preserves history and enables diffing.
+    Should explain what to re-pull: pricing page first (most volatile), SEO metrics (traffic
+    and rankings shift monthly), changelog scan for product changes. Should update the Generated
+    date. Should add a Change Log section at the bottom noting what changed since last profile.
+    Should also save the new raw data to a new <YYYY-MM-DD> folder rather than overwriting
+    prior data — supports diffing over time.'
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-profile-04
+  department: marketing
+  prompt: What pages should I scrape for a competitor profile?
+  expected_properties:
+  - Lists all key page types in priority order
+  - Specifies what to extract from each page type
+  - Includes changelog as product direction signal
+  - Mentions optional review scraping
+  - References Firecrawl Map then Scrape workflow
+  rubric: 'Should list the prioritized page types from Phase 1: homepage, pricing page, features/product
+    pages, about/company page, blog (top-level for content strategy signals), customers/case
+    studies page, integrations page, changelog/what''s new (if exists). Should explain what
+    to extract from each: homepage (headline, value prop, primary CTA, social proof, target
+    audience signals), pricing (tiers, prices, feature breakdown, billing options, free tier/trial
+    details), features (categories, key capabilities, how they describe each feature), about
+    (founding story, team size, funding, mission, HQ), customers (named customers, logos,
+    industries, case study themes), integrations (count, key integrations, categories), changelog
+    (release velocity, recent focus areas, product direction signals). Should mention optional
+    review scraping (G2, Capterra, Product Hunt, TrustRadius).'
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-profile-05
+  department: marketing
+  prompt: I want a profile but I don't care about SEO data — just pricing, positioning, and
+    customer logos. Can you skip the DataForSEO calls?
+  expected_properties:
+  - Skips Phase 2 (DataForSEO) as requested
+  - Runs Phase 1 and Phase 3
+  - Explains what's missing without SEO data
+  - Flags SEO section as skipped, not blank
+  - Still saves raw data
+  rubric: Should accept the scoped request and skip Phase 2. Should run Phase 1 (Firecrawl
+    scraping of homepage, pricing, customers pages) and Phase 3 synthesis only. Should explain
+    that without SEO data, the profile won't include Domain Rank, organic traffic estimates,
+    ranked keywords, referring domains, or top organic pages — but the positioning, pricing,
+    and customer sections will be complete. Should produce an abbreviated profile flagging
+    the SEO section as 'not collected per user request' rather than leaving placeholders.
+    Should still save raw scrapes to disk for reuse.
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-profile-06
+  department: marketing
+  prompt: Should I trust the customer logo wall on the competitor's homepage as evidence of
+    who their customers are?
+  expected_properties:
+  - Treats logos as positioning claim, not customer breakdown
+  - Recommends cross-referencing case studies and reviews
+  - Mentions checking traffic/backlink profile against claim scale
+  - Distinguishes verifiable named customers from claims
+  - Notes including date pulled
+  rubric: 'Should apply the ''Facts Over Opinions'' and ''Honest Assessment'' principles.
+    Should explain that customer logos are a positioning claim, not necessarily an accurate
+    customer breakdown — companies often show their best-known logos regardless of share of
+    revenue. Should recommend cross-referencing: check case studies for actual usage details,
+    search for press releases naming customers, look at customer reviews on G2/Capterra/TrustRadius
+    for company name signals, check their LinkedIn for posts about customers. Should note:
+    if they claim ''10,000 customers'' but have weak traffic/backlink profile, the claim should
+    be flagged in the profile. Should distinguish between named customers (verifiable claims)
+    and ''industries served'' (positioning statement). Always include the date the data was
+    pulled.'
+  tags:
+  - competitor-profile
+  - imported
+- id: marketing-competitor-analysis-01
+  department: marketing
+  prompt: Create a 'Best Asana Alternatives' page for our project management tool. We compete
+    mainly on price (we're $8/user vs their $24/user) and simplicity (they've become bloated).
+    Target audience is small teams (5-20 people).
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies as plural alternatives format
+  - Includes TL;DR comparison section
+  - Includes feature comparison table
+  - Includes pricing comparison
+  - Includes 'who it's best for' per alternative
+  - Positions user's product prominently with differentiators
+  - Addresses SEO for target keyword
+  rubric: 'Should check for product-marketing.md first. Should identify this as the plural
+    alternatives format ([Competitor] Alternatives). Should include the essential sections:
+    TL;DR comparison, brief paragraphs on each alternative (including the user''s product
+    positioned first or prominently), feature comparison table, pricing comparison, who each
+    alternative is best for. Should use the modular content architecture approach. Should
+    address SEO considerations for the target keyword ''Asana alternatives.'' Should position
+    the user''s product with the stated differentiators (price, simplicity).'
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-competitor-analysis-02
+  department: marketing
+  prompt: Write a 'HubSpot vs Salesforce' comparison page. We're HubSpot and want to show
+    why we're the better choice for SMBs.
+  expected_properties:
+  - Identifies as 'you vs competitor' format
+  - Includes structured comparison sections
+  - Includes feature-by-feature comparison
+  - Includes pricing comparison
+  - Includes TL;DR at the top
+  - Factually accurate about competitor
+  - Strategically positions user's product for SMBs
+  - Includes migration path or switching section
+  rubric: 'Should identify this as the ''you vs competitor'' format. Should include structured
+    comparison sections: overview of both, feature-by-feature comparison, pricing comparison,
+    pros/cons of each, who each is best for, and migration path. Should be factually accurate
+    about the competitor while strategically positioning the user''s product. Should include
+    a TL;DR at the top. Should address the SMB angle throughout. Should use the centralized
+    competitor data architecture pattern.'
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-competitor-analysis-03
+  department: marketing
+  prompt: we need a page targeting 'mailchimp alternative' (singular). we're an email marketing
+    platform focused on e-commerce brands.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Identifies as singular alternative format
+  - Focuses on user's product as THE alternative
+  - Includes why people switch from Mailchimp
+  - Highlights e-commerce-specific advantages
+  - Includes feature and pricing comparison
+  - Includes migration guide
+  - Optimizes for singular keyword
+  rubric: 'Should trigger on casual phrasing. Should identify this as the singular alternative
+    format ([Competitor] Alternative — positioning your product as THE alternative). Should
+    focus the entire page on why the user''s product is the best Mailchimp alternative for
+    e-commerce. Should include: why people switch from Mailchimp, what the user''s product
+    does better (e-commerce specific features), feature comparison, pricing comparison, migration
+    guide, customer testimonials. Should optimize for the singular keyword ''Mailchimp alternative.'''
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-competitor-analysis-04
+  department: marketing
+  prompt: Can you create a comparison page for 'Notion vs Coda'? We're a third-party review
+    site, not affiliated with either product.
+  expected_properties:
+  - Identifies as 'competitor vs competitor' format
+  - Maintains objectivity (third-party perspective)
+  - Includes balanced feature comparison
+  - Includes pricing comparison
+  - Includes use case recommendations
+  - Addresses SEO considerations
+  - Suggests monetization approach
+  rubric: 'Should identify this as the ''competitor vs competitor'' format (third-party perspective).
+    Should maintain objectivity since the user isn''t either product. Should include balanced
+    comparison: overview of both, feature comparison, pricing, pros/cons, use case recommendations.
+    Should use the essential page sections from the skill. Should suggest how to monetize
+    the page (affiliate links, CTA to the user''s own product if relevant). Should address
+    SEO for the ''Notion vs Coda'' keyword.'
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-competitor-analysis-05
+  department: marketing
+  prompt: We want to build a whole competitor comparison hub. We have 5 main competitors and
+    want to create alternative pages for each, plus head-to-head comparisons. How should we
+    structure this?
+  expected_properties:
+  - Applies centralized competitor data architecture
+  - Recommends hub structure with multiple page types
+  - Suggests individual and roundup alternative pages
+  - Addresses internal linking between comparison pages
+  - Recommends research process for competitive data
+  - Addresses URL structure
+  rubric: 'Should apply the centralized competitor data architecture. Should recommend a hub
+    structure with: individual alternative pages for each competitor (5 singular pages), a
+    ''best alternatives'' roundup page, head-to-head comparison pages for key matchups. Should
+    address internal linking strategy between these pages. Should recommend the research process
+    for gathering competitive data. Should address URL structure and site architecture for
+    the hub.'
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-competitor-analysis-06
+  department: marketing
+  prompt: I need to create a battle card for our sales team comparing us to Zendesk. It should
+    help reps handle competitive objections during sales calls.
+  expected_properties:
+  - Recognizes this as internal sales enablement material
+  - References or defers to sales-enablement skill
+  - Does not attempt to create internal battle card using public comparison page patterns
+  rubric: Should recognize this as internal sales enablement material, not a public comparison
+    page. Should defer to or cross-reference the sales-enablement skill, which handles battle
+    cards, objection handling docs, and internal competitive collateral. May provide some
+    competitive positioning advice but should make clear that sales-enablement is the right
+    skill for internal sales materials.
+  tags:
+  - competitor-analysis
+  - imported
+- id: marketing-content-strategy-01
+  department: marketing
+  prompt: Help me build a content strategy for our B2B SaaS product. We sell expense management
+    software to finance teams at companies with 50-500 employees. We currently have no blog
+    and want to start from scratch.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Establishes 3-5 content pillars
+  - Maps content by buyer stage (awareness through implementation)
+  - Includes keyword research by buyer stage
+  - Recommends mix of searchable and shareable content
+  - Uses prioritization scoring framework
+  - Provides publishing cadence or calendar
+  - Recommends appropriate starting content types
+  rubric: Should check for product-marketing.md first. Should establish content pillars (3-5
+    core topic areas). Should map content types by buyer stage (awareness → consideration
+    → decision → implementation). Should identify keyword research opportunities by buyer
+    stage. Should recommend a mix of searchable (SEO-driven) and shareable (thought leadership,
+    data) content. Should use the prioritization scoring framework (customer impact 40%, content-market
+    fit 30%, search potential 20%, resources 10%). Should provide an initial content calendar
+    or publishing cadence. Should recommend content types appropriate for starting from scratch.
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-content-strategy-02
+  department: marketing
+  prompt: We have 200+ blog posts but traffic has been flat for a year. Our content feels
+    random — no clear strategy. How do we fix this?
+  expected_properties:
+  - Diagnoses the 'random content' problem
+  - Recommends content audit for existing posts
+  - Introduces content pillars and topical clustering
+  - Identifies hub-and-spoke opportunities
+  - Recommends update, consolidate, or retire decisions
+  - Uses prioritization framework
+  - Addresses topical authority building
+  rubric: Should diagnose the 'random content' problem. Should recommend a content audit process
+    to evaluate existing posts. Should introduce content pillars and topical clustering to
+    organize the existing library. Should identify hub-and-spoke opportunities from existing
+    content. Should recommend which posts to update, consolidate, or retire. Should use the
+    prioritization framework to plan next steps. Should address topical authority building
+    through clusters.
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-content-strategy-03
+  department: marketing
+  prompt: what kind of content should we be creating? we're a developer tool (API testing
+    platform) and our audience is backend developers and QA engineers
+  expected_properties:
+  - Triggers on casual phrasing
+  - Recommends content types for developer audience
+  - Emphasizes technical depth and practical value
+  - Notes developers prefer substance over marketing
+  - Suggests content pillars for developer tool
+  - Uses ideation sources framework
+  - Mentions developer community channels
+  rubric: 'Should trigger on casual phrasing. Should recommend content types appropriate for
+    a developer audience: technical tutorials, documentation-style guides, use-case content,
+    template/example libraries, data-driven benchmarks. Should note that developer audiences
+    prefer depth, accuracy, and practical value over marketing fluff. Should suggest content
+    pillars aligned with developer interests. Should use the ideation sources framework (keyword
+    data, community forums like Stack Overflow/Reddit, competitor gaps).'
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-content-strategy-04
+  department: marketing
+  prompt: How should we prioritize which content to create first? We have a list of 50 blog
+    post ideas but limited resources — one content marketer writing 2 posts per week.
+  expected_properties:
+  - Applies prioritization scoring framework with weights
+  - Explains each scoring dimension
+  - Recommends focusing on high-impact, lower-effort first
+  - Considers buyer stage distribution
+  - Provides practical workflow for limited resources
+  rubric: 'Should apply the prioritization scoring framework: customer impact (40%), content-market
+    fit (30%), search potential (20%), resources required (10%). Should help score or rank
+    the content ideas using this framework. Should recommend focusing on high-impact, lower-effort
+    content first. Should consider the buyer stage distribution (don''t write only top-of-funnel).
+    Should provide a practical workflow for the single content marketer to use going forward.'
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-content-strategy-05
+  department: marketing
+  prompt: We want to build topical authority in 'employee engagement.' What does a content
+    cluster look like for this topic?
+  expected_properties:
+  - Applies hub-and-spoke content cluster model
+  - Designs a pillar page for the core topic
+  - Identifies 8-15 supporting spoke articles
+  - Maps internal linking between hub and spokes
+  - Addresses keyword research for the cluster
+  - Recommends content types for each piece
+  rubric: Should apply the hub-and-spoke content cluster model. Should design a pillar page
+    for 'employee engagement' (comprehensive, 3000+ word guide). Should identify 8-15 supporting
+    spoke articles targeting long-tail keywords related to employee engagement. Should map
+    the internal linking structure between hub and spokes. Should address keyword research
+    for the cluster. Should recommend content types for each piece (guide, how-to, template,
+    data-driven, etc.).
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-content-strategy-06
+  department: marketing
+  prompt: Can you write a blog post about remote work best practices for our HR software blog?
+  expected_properties:
+  - Recognizes this as content creation, not strategy
+  - References or defers to copywriting skill
+  - Does not attempt to write the full blog post
+  - May provide strategic context for the piece
+  rubric: Should recognize this is a copywriting/content creation task, not a content strategy
+    task. Should defer to or cross-reference the copywriting skill for writing individual
+    pieces of content. May provide strategic context (where this fits in the content strategy,
+    keyword targeting, audience) but should make clear that copywriting is the right skill
+    for writing the actual content.
+  tags:
+  - content-strategy
+  - imported
+- id: marketing-human-writing-01
+  department: marketing
+  prompt: 'Edit this homepage copy for us: ''Welcome to CloudSync! We are very excited to
+    offer you an innovative, cutting-edge platform that seamlessly integrates with your existing
+    tools. Our powerful solution helps businesses of all sizes optimize their workflows and
+    drive meaningful results. Get started today and experience the difference!'''
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies Seven Sweeps Framework
+  - Identifies vague language (Clarity sweep)
+  - Flags weak opening and company-focused language (Voice & Tone sweep)
+  - Questions missing value proposition (So What sweep)
+  - Notes missing proof points (Prove It sweep)
+  - Flags generic terms (Specificity sweep)
+  - Provides a rewritten version
+  rubric: 'Should check for product-marketing.md first. Should apply the Seven Sweeps Framework
+    systematically. Sweep 1 (Clarity): identify vague language (''optimize workflows,'' ''drive
+    meaningful results,'' ''experience the difference''). Sweep 2 (Voice & Tone): flag ''Welcome
+    to'' as weak opening, ''we are very excited'' as company-focused. Sweep 3 (So What): question
+    what specific value is being offered. Sweep 4 (Prove It): note no proof points, stats,
+    or evidence. Sweep 5 (Specificity): flag ''businesses of all sizes,'' ''existing tools,''
+    ''powerful solution'' as generic. Sweep 6 (Heightened Emotion): assess emotional impact.
+    Sweep 7 (Zero Risk): check for trust signals. Should provide a rewritten version addressing
+    all issues.'
+  tags:
+  - human-writing
+  - imported
+- id: marketing-human-writing-02
+  department: marketing
+  prompt: 'Quick edit on this CTA section: ''Ready to take your business to the next level?
+    Our team of dedicated professionals is standing by to help you achieve your goals. Click
+    here to learn more about how we can help you succeed.'''
+  expected_properties:
+  - Identifies clichés and filler phrases
+  - Flags 'click here' and 'learn more' as weak
+  - Applies word-level and sentence-level checks
+  - Rewrites with specific value and strong CTA
+  - Uses active voice in rewrite
+  - Keeps response concise for a quick edit
+  rubric: 'Should apply the quick-pass editing checks. Should identify: ''take your business
+    to the next level'' (cliché), ''team of dedicated professionals'' (filler), ''standing
+    by'' (passive), ''click here'' (weak CTA), ''learn more'' (vague action), ''help you succeed''
+    (generic). Should apply word-level, sentence-level, and paragraph-level checks. Should
+    rewrite with specific value prop, active voice, and strong action-oriented CTA. Should
+    be concise since this was requested as a ''quick edit.'''
+  tags:
+  - human-writing
+  - imported
+- id: marketing-human-writing-03
+  department: marketing
+  prompt: 'edit this product description, it feels too long and wordy: ''Our comprehensive
+    project management solution provides teams with a robust set of tools that enable them
+    to efficiently plan, execute, and monitor their projects from start to finish. With our
+    intuitive interface, powerful analytics dashboard, and seamless integration capabilities,
+    you can ensure that every aspect of your project is managed with precision and care. Whether
+    you''re a small startup or a large enterprise, our platform scales to meet your unique
+    needs and requirements, helping you deliver projects on time and within budget every single
+    time.'''
+  expected_properties:
+  - Triggers on casual phrasing
+  - Identifies redundancy in the copy
+  - Identifies filler words and hedge phrases
+  - Identifies generic claims
+  - Cuts copy significantly (50%+ reduction)
+  - Provides tighter rewrite with specific language
+  rubric: 'Should trigger on casual phrasing. Should apply the Clarity and Specificity sweeps
+    primarily. Should identify: redundancy (''plan, execute, and monitor'' overlaps with ''from
+    start to finish''), filler words (''comprehensive,'' ''robust,'' ''efficiently,'' ''seamless,''
+    ''unique''), hedge phrases (''ensuring every aspect,'' ''with precision and care''), and
+    generic claims (''scales to meet your needs,'' ''on time and within budget every single
+    time''). Should cut the copy significantly (probably by 50%+). Should provide a tighter
+    rewrite that says the same thing in fewer, more specific words.'
+  tags:
+  - human-writing
+  - imported
+- id: marketing-human-writing-04
+  department: marketing
+  prompt: 'Review this testimonial section and improve it: ''CloudSync is great! It really
+    helped our company. The team was very responsive and the product works well. We would
+    recommend it to anyone looking for a solution. - John S., CEO'''
+  expected_properties:
+  - Applies Prove It and Specificity sweeps
+  - Identifies testimonial as too vague
+  - Recommends specific results and context
+  - Suggests questions to get better testimonial
+  - Does not fabricate specific numbers
+  - Provides template for strong testimonial
+  rubric: Should apply the Prove It and Specificity sweeps. Should identify the testimonial
+    as too vague to be persuasive ('great,' 'really helped,' 'works well,' 'anyone looking
+    for a solution'). Should recommend replacing with specific results ('reduced project delivery
+    time by 30%'), specific context ('team of 45 engineers'), and specific outcomes. Should
+    suggest questions to ask the customer for a better testimonial. Should not fabricate specific
+    numbers but should provide a template showing what a strong testimonial looks like.
+  tags:
+  - human-writing
+  - imported
+- id: marketing-human-writing-05
+  department: marketing
+  prompt: 'I need you to apply the ''So What'' and ''Zero Risk'' sweeps to this pricing page
+    copy: ''Our Pro plan includes unlimited projects, advanced reporting, priority support,
+    and custom integrations. Starting at $99/month.'''
+  expected_properties:
+  - Applies So What sweep to each feature
+  - Translates features to customer benefits
+  - Applies Zero Risk sweep
+  - Identifies missing trust signals
+  - Suggests guarantee, trial, or cancel-anytime language
+  - Provides rewritten copy addressing both sweeps
+  rubric: 'Should apply specifically the So What and Zero Risk sweeps as requested. So What:
+    for each feature, ask ''so what does this mean for the customer?'' — unlimited projects
+    (what does that enable?), advanced reporting (what decisions can they make?), priority
+    support (what does that mean in practice? response time?), custom integrations (which
+    ones? what workflow does it enable?). Zero Risk: identify missing trust signals — no guarantee,
+    no trial mention, no social proof near pricing, no ''cancel anytime'' assurance. Should
+    provide rewritten copy addressing both sweeps.'
+  tags:
+  - human-writing
+  - imported
+- id: marketing-human-writing-06
+  department: marketing
+  prompt: Write fresh homepage copy for our new product. We're launching a CRM for real estate
+    agents.
+  expected_properties:
+  - Recognizes this as writing new copy, not editing existing copy
+  - References or defers to copywriting skill
+  - Explains that copy-editing is for improving existing copy
+  - Does not attempt to write full page copy from scratch
+  rubric: Should recognize this is a copywriting-from-scratch task, not copy editing. Should
+    defer to or cross-reference the copywriting skill, which handles writing new copy from
+    scratch. Copy-editing is specifically for improving existing copy. Should make this distinction
+    clear.
+  tags:
+  - human-writing
+  - imported
+- id: marketing-customer-research-01
+  department: marketing
+  prompt: I have 20 customer interview transcripts. Help me analyze them.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks about the goal before diving in (improve messaging, build personas, find gaps, etc.)
+  - Mentions extracting jobs to be done, pain points, and desired outcomes
+  - Suggests organizing quotes by theme
+  - References frequency and intensity scoring
+  - Asks which deliverable is needed
+  rubric: 'Should check for product-marketing.md first. Should ask about the goal before analyzing
+    (improve messaging, build personas, find product gaps, etc.). Should apply the extraction
+    framework: jobs to be done, pain points, trigger events, desired outcomes, language/vocabulary,
+    alternatives considered. Should recommend clustering by theme, frequency + intensity scoring,
+    and identifying money quotes. Should ask which deliverable is needed.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-02
+  department: marketing
+  prompt: I want to do ICP research but I don't have any customer interviews yet.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recommends digital watering hole research as an alternative
+  - Mentions Reddit, G2, or review sites as starting points
+  - Asks what product or category to research
+  - Offers to help extract insights from online sources
+  rubric: Should check for product-marketing.md first. Should recommend digital watering hole
+    research as a starting point. Should mention Reddit, G2, Capterra, forums, or niche communities
+    as sources. Should offer to plan a research approach and explain what to extract from
+    online sources. Should note this is Mode 2 and ask what product/category to research.
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-03
+  department: marketing
+  prompt: Mine Reddit and G2 to understand what people hate about project management software.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies relevant subreddits or search strategies for project management
+  - Suggests reading 3-star and 1-star G2 reviews
+  - Recommends competitor 4-star reviews for buried complaints
+  - Plans to extract verbatim quotes and pain themes
+  - 'Mentions what to look for: complaints, workarounds, switching triggers'
+  rubric: Should check for product-marketing.md first. Should identify relevant subreddits
+    (r/projectmanagement, r/productivity, r/agile) and search strategies. Should recommend
+    reading 3-star and 1-star G2 reviews and competitor 4-star reviews. Should plan to extract
+    verbatim quotes, pain themes, and switching triggers. Should apply the extraction table
+    (source, quote, context, sentiment, theme tag, profile signals).
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-04
+  department: marketing
+  prompt: Build me a customer persona for a marketing manager at a B2B SaaS company.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks if there is existing research to build from before inventing details
+  - Warns against creating personas without data
+  - Includes jobs to be done, pains, triggers, and desired outcomes in persona structure
+  - Mentions the need to capture actual customer vocabulary
+  - Notes minimum data threshold (5-10 data points)
+  rubric: 'Should check for product-marketing.md first. Should ask if there is existing research
+    to build from before generating a persona. Should warn against inventing details without
+    data. Should use the persona structure: profile, primary JTBD, trigger events, top pains,
+    desired outcomes, objections, alternatives, key vocabulary, how to reach them. Should
+    note that personas should be built from at least 5-10 data points.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-05
+  department: marketing
+  prompt: I have 6 months of customer support tickets. What insights can I pull from them?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recommends categorizing tickets before analyzing (bugs vs confusion vs feature requests)
+  - Warns against treating all tickets as equal signal
+  - Mentions extracting recurring language and patterns
+  - Asks about the goal — product improvement, messaging, or something else
+  rubric: Should check for product-marketing.md first. Should recommend categorizing tickets
+    before analyzing (bugs vs. confusion vs. feature requests vs. expectation mismatches).
+    Should warn against treating all tickets as equal signal. Should suggest extracting recurring
+    language, patterns, and 'I wish it could…' phrases. Should ask about the goal — product
+    improvement, messaging, reducing support load, or something else.
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-06
+  department: marketing
+  prompt: What are customers saying about my competitors on review sites?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recommends reading competitor 4-star reviews specifically for buried complaints
+  - Mentions G2 or Capterra as sources
+  - 'Describes what to extract: what they love, what frustrates them, unmet needs'
+  - Frames as competitive intelligence input
+  rubric: 'Should check for product-marketing.md first. Should ask which competitors to research.
+    Should recommend G2 and Capterra as primary sources. Should specifically call out reading
+    competitor 4-star reviews for buried complaints. Should describe what to extract: what
+    they love (battlecard intel), what frustrates them (opportunities), unmet needs. Should
+    use the review mining template.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-07
+  department: marketing
+  prompt: Help me do voice of customer research for a new SaaS in the HR space.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks about target ICP segment within HR
+  - Suggests relevant digital watering holes (subreddits, G2 categories, communities)
+  - Plans to extract verbatim language for copy use
+  - Mentions organizing findings into a VOC quote bank
+  rubric: 'Should check for product-marketing.md first. Should ask about the specific ICP
+    segment within HR (recruiter, HR generalist, CHRO, etc.). Should suggest relevant digital
+    watering holes: r/humanresources, r/recruiting, HR Slack communities, G2 HR category,
+    LinkedIn. Should plan to extract verbatim language for copy use. Should offer to produce
+    a VOC quote bank as a deliverable.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-08
+  department: marketing
+  prompt: I want to understand why customers churn. I have exit survey results.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recommends segmenting churn reasons before analyzing
+  - Warns against averaging across different churn causes
+  - Suggests pairing open-ended responses with quantitative data
+  - Asks if win/loss interview data is also available
+  rubric: Should check for product-marketing.md first. Should recommend segmenting churn reasons
+    before analyzing — do not average across different causes. Should suggest pairing open-ended
+    responses with quantitative data. Should ask if win/loss interview data or support tickets
+    are also available. Should apply confidence labels (high/med/low) based on sample size
+    and source consistency.
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-09
+  department: marketing
+  prompt: Find the digital watering holes where DevOps engineers talk shop.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Mentions specific relevant communities (r/devops, Hacker News, LinkedIn, Discord)
+  - Suggests what to search for in those communities
+  - Describes what signal to extract from each source type
+  rubric: 'Should check for product-marketing.md first. Should identify specific relevant
+    communities: r/devops, r/sysadmin, Hacker News, DevOps-focused Discord/Slack groups, LinkedIn,
+    Stack Overflow. Should suggest what to search for in those communities. Should describe
+    what signal to extract from each source type and reference source-guides.md for detailed
+    playbooks.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-10
+  department: marketing
+  prompt: Turn my customer research into messaging I can use on my homepage.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Extracts the VOC language and themes first before jumping to copy
+  - Identifies the highest-signal quotes for messaging
+  - References the copywriting skill for the actual copy writing step
+  rubric: Should check for product-marketing.md first. Should extract VOC language and top
+    themes before moving to copy. Should identify the highest-signal quotes and language patterns.
+    Should produce a VOC summary or quote bank, then hand off to the copywriting skill for
+    the actual copy writing step rather than writing homepage copy directly.
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-11
+  department: marketing
+  prompt: I run a mobile fitness app and want to understand why users drop off after week
+    2.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recognizes this as a B2C research scenario
+  - Suggests app store reviews as a primary source
+  - Mentions Reddit or community sources relevant to fitness/consumer apps
+  - Frames around understanding drop-off triggers and desired outcomes
+  rubric: 'Should check for product-marketing.md first. Should recognize this as a B2C research
+    scenario. Should suggest B2C-appropriate sources: app store reviews (1-3 star), Reddit
+    fitness communities, YouTube comment sections on fitness apps, TikTok/Instagram comments.
+    Should also recommend in-app surveys and analyzing support tickets/reviews. Should frame
+    around activation and habit formation research.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-customer-research-12
+  department: marketing
+  prompt: I have no existing research and don't know who my best customers are yet.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Recognizes this as a zero-research bootstrap scenario
+  - Recommends forming hypotheses before gathering data
+  - Suggests a minimum viable research plan (interviews + online sources)
+  - Warns against building personas without any data
+  rubric: 'Should check for product-marketing.md first. Should treat this as a bootstrap research
+    scenario. Should recommend starting with hypothesis formation before gathering data. Should
+    suggest a minimum viable research plan: 5-10 customer interviews + digital watering hole
+    scan. Should provide interview recruiting tips and what questions to ask. Should warn
+    against building personas before collecting any data.'
+  tags:
+  - customer-research
+  - imported
+- id: marketing-directory-submit-01
+  department: marketing
+  prompt: We're launching our AI SaaS in 3 weeks. Help me plan all the directories we should
+    submit to.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Runs Phase 0 readiness assessment
+  - Recommends tier mix appropriate to AI SaaS
+  - Maps 3-week PH timeline to calendar dates
+  - Names Product Hunt as anchor
+  - Recommends 10-in-30 reviews protocol
+  - Sets day-30 and day-90 KPI targets
+  - References directory-list.md or positioning-variations.md
+  rubric: 'Should check for product-marketing.md first. Should run Phase 0 readiness assessment
+    with the 9 questions before recommending submissions. Should reject submission if any
+    of items 1-7 are ''no'' (hard block) and explain why. Should recommend tier mix: Tier
+    1 flagship launch (~15 — Product Hunt as anchor, BetaList, HN Show HN, Fazier, DevHunt),
+    Tier 2 startup/SaaS (~50), Tier 3 AI directories (~40 — TAAFT, Futurepedia, Toolify),
+    Tier 4 MCP/agent if applicable. Should map the 3-week Product Hunt prep timeline to calendar
+    dates. Should warn against submitting before destination pages exist. Should reference
+    references/directory-list.md and references/positioning-variations.md. Should recommend
+    the 10-in-30 reviews protocol for G2/Capterra. Should set day-30 and day-90 targets from
+    the KPI table.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-directory-submit-02
+  department: marketing
+  prompt: Can I just copy-paste the same description into every directory?
+  expected_properties:
+  - Refuses the request
+  - Cites Rule 3 (positioning varies by directory type)
+  - Notes AI engines penalize duplicate content
+  - Lists different framing per surface type
+  - Specifies variant lengths (tagline, short, long)
+  - References positioning-variations.md
+  rubric: 'Should refuse and explain Rule 3: positioning varies by directory type. Should
+    explain AI engines penalize duplicate content — directories cross-referenced by Claude,
+    ChatGPT, Perplexity will de-rank repetitive copy. Should explain different framing per
+    surface: startup directories lead with outcome (audience is founders), SaaS directories
+    lead with alternative framing (people search ''[competitor] alternative''), AI directories
+    lead with AI-first architecture, agent/MCP directories lead with the agent/MCP angle,
+    B2B review sites lead with ROI + use case. Should recommend preparing distinct variants
+    per tier: tagline under 10 words, 60-char short description, 150-word long description,
+    5-8 category tags. Should reference references/positioning-variations.md.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-directory-submit-03
+  department: marketing
+  prompt: Should we pay for one of those directory submission services that submits to 200
+    directories for $99?
+  expected_properties:
+  - Refuses the service
+  - Cites 'don't pay for submission services' rule
+  - Warns about low-DR spam directories
+  - Warns about Google spam penalty risk
+  - Recommends manual submission to quality directories
+  rubric: 'Should say no, citing ''What NOT to Do'' rule 1: don''t pay for directory submission
+    services. Should explain the whole point is these are free — it''s an afternoon of copy-paste.
+    Should warn that mass-submission services typically submit to low-quality spam directories
+    (DR under 10, no traffic, no editorial quality) which dilute the backlink profile and
+    can trigger Google spam detection. Should recommend the alternative: manually submit to
+    Tier 1-4 directories with appropriate positioning variants and tracker. Should reinforce
+    that the value comes from quality directories with editorial standards, not raw volume.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-directory-submit-04
+  department: marketing
+  prompt: Walk me through how to launch on Product Hunt next month. We've never done it before.
+  expected_properties:
+  - Maps 3-week timeline with specific day markers
+  - Notes 12:01 AM Pacific Time launch
+  - Restricts to Tue/Wed/Thu
+  - Emphasizes first 2 hours / 50+ supporters
+  - Warns never ask for upvotes
+  - Recommends asking for feedback
+  - Warns against DMing strangers
+  - Includes post-launch recap and cross-posting
+  rubric: 'Should apply the Product Hunt Deep Dive playbook. Should map the 3-week prep timeline:
+    Day -21 to -14 (warm up hunter account, upvote and comment on 3 launches/day), Day -14
+    (create Upcoming page), Day -10 (optional book a hunter — trade not cash), Day -7 (draft
+    launch-day assets: 1270x760 gallery images, tagline, 260-char description, first comment),
+    Day -3 (email list warm-up), Day -1 (final check). Should explain launch day: launch at
+    12:01 AM Pacific Time on Tuesday/Wednesday/Thursday only, first 2 hours are everything
+    (need 50+ supporters), post the first comment yourself, reply to every comment in under
+    30 minutes, share to multiple channels. Should warn never ask for upvotes — ask for feedback.
+    Should warn don''t DM strangers — community flags this. Should explain post-launch: write
+    a launch recap blog post with numbers + lessons, cross-post to Indie Hackers, only submit
+    to Show HN if there''s a technical angle. Should note 80% of failed launches fail from
+    no warm audience or asking for upvotes.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-directory-submit-05
+  department: marketing
+  prompt: We want to list on G2 but we only have 4 customers right now. Worth doing?
+  expected_properties:
+  - Explains 10-review threshold for Grid
+  - Recommends NOT submitting yet OR claim + plan review drive
+  - Lays out 10-in-30 protocol
+  - Notes incentive ($25 gift card) is allowed
+  - Mentions Users Love Us badge requirements
+  - Warns against paying for G2 plan in year one
+  - Mentions Summer/Fall report cutoffs
+  rubric: 'Should explain G2 and Capterra listings are worthless without reviews — 10 reviews
+    is the magic threshold for Grid appearance. Should recommend NOT submitting yet, or claim
+    the listing but plan a review drive in parallel. Should explain the 10-in-30 protocol:
+    identify 20 users who completed a meaningful action, send each a personal email with direct
+    review URL (reduces friction ~70%), offer a modest thank-you ($25 Amazon gift card is
+    allowed by G2/TrustRadius), follow up once after 5 days, target 50% conversion. Should
+    note the Users Love Us badge is free (20 reviews at 4.0+) but Grid/Momentum/Index/Award
+    badges require a paid G2 plan ($2,999+/year as of Summer 2025) — and recommend NOT spending
+    on paid G2 in year one. Should mention G2 Summer report cutoff ~April 28 and Fall ~July
+    28. Should suggest waiting until ~10 users are realistic before submitting.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-directory-submit-06
+  department: marketing
+  prompt: We submitted to 50 directories last week. Now what?
+  expected_properties:
+  - Warns against over-indexing on launch spike
+  - Recommends verifying dofollow status of backlinks
+  - Pivots to destination pages strategy
+  - Mentions GEO tactics
+  - Includes ongoing community distribution
+  - Recommends tracking weekly KPIs
+  - Says investigate before submitting more
+  rubric: 'Should warn against treating submissions as the strategy. Should reference ''What
+    NOT to Do'' rule 11: don''t over-index on launch spike. Flywheel is templates + alternatives
+    + reviews + ongoing content. Should recommend verifying the dofollow status of acquired
+    backlinks (curl -sIL | grep -i rel=). Should pivot to ongoing distribution: destination
+    pages strategy (alternative pages converting 5-15%, use-case/ICP pages, template gallery
+    if applicable, ''best of'' listicles you write yourself, integration pages), GEO tactics
+    for AI citation (single H1, FAQ schema, comparison tables, get cited on Reddit/HN, claim
+    Crunchbase/LinkedIn/Wikidata), community presence (Reddit 90/10 rule, LinkedIn 3-5 posts/week,
+    Twitter build-in-public, Indie Hackers, Dev.to/Hashnode). Should remind to track weekly
+    KPIs (DR, referring domains, indexed pages, organic clicks, signups from directory referrals)
+    and investigate if numbers aren''t moving rather than submitting more.'
+  tags:
+  - directory-submit
+  - imported
+- id: marketing-email-sequence-01
+  department: marketing
+  prompt: Create a welcome email sequence for new users who sign up for our project management
+    tool's free trial. The trial is 14 days. We want to get them to their aha moment (creating
+    their first project and inviting a team member).
+  expected_properties:
+  - Checks for product-marketing.md
+  - Creates 5-7 email welcome sequence
+  - Follows one email one job principle
+  - Maps emails to trial timeline (14 days)
+  - Includes timing between emails
+  - Each email has hook, context, value, CTA
+  - Includes subject lines for each email
+  - Aligns with stated aha moment
+  - Output follows structured per-email format
+  rubric: 'Should check for product-marketing.md first. Should create a welcome sequence (5-7
+    emails) following the core principles: one email one job, value before ask. Should map
+    each email to a specific goal in the 14-day trial journey. Should include timing/delays
+    between emails. Each email should follow the email copy structure: hook → context → value
+    → CTA → sign-off. Should include subject lines following the subject line strategy. Should
+    align sequence with the aha moment (first project + team invite). Output should follow
+    the structured format with sequence overview and per-email specs.'
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-email-sequence-02
+  department: marketing
+  prompt: We need a lead nurture sequence for people who download our 'State of DevOps 2024'
+    report. Goal is to get them to book a demo of our CI/CD platform.
+  expected_properties:
+  - Creates 6-8 email lead nurture sequence
+  - Follows value before ask principle
+  - Maps from awareness through consideration to decision
+  - Includes timing between emails
+  - Each email has clear subject line and single CTA
+  - Gradually increases commitment asks
+  - Connects to original download topic
+  rubric: Should create a lead nurture sequence (6-8 emails). Should follow value before ask
+    — first emails should provide related value, not immediately push for demo. Should map
+    the sequence from awareness (report download) through consideration (related content,
+    case studies) to decision (demo request). Should include timing between emails. Each email
+    should have clear subject line, hook, single CTA. Should gradually increase commitment
+    asks across the sequence.
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-email-sequence-03
+  department: marketing
+  prompt: our email open rates have tanked. used to be 35% now we're at 18%. what's going
+    on and how do we fix our subject lines?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Diagnoses potential causes beyond just subject lines
+  - Addresses sender reputation and deliverability
+  - Recommends list hygiene or re-engagement
+  - Applies subject line strategy with specific patterns
+  - Provides subject line formulas and examples
+  - Suggests testing framework
+  rubric: 'Should trigger on casual phrasing. Should diagnose potential causes of declining
+    open rates: sender reputation, list hygiene, subject line quality, sending frequency,
+    deliverability issues. Should apply the subject line strategy from the skill: test curiosity
+    vs benefit vs urgency patterns, personalization, optimal length. Should recommend a re-engagement
+    campaign to clean the list. Should provide specific subject line formulas and examples.
+    Should suggest testing framework for subject lines.'
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-email-sequence-04
+  department: marketing
+  prompt: Build a re-engagement sequence for subscribers who haven't opened any emails in
+    90 days. We have about 5,000 inactive subscribers.
+  expected_properties:
+  - Creates 3-4 email re-engagement sequence
+  - Acknowledges absence in first email
+  - Escalates through the sequence
+  - Includes 'last chance' final email
+  - Recommends sunset policy for non-responders
+  - Addresses deliverability impact of inactive subscribers
+  - Uses compelling subject lines
+  rubric: 'Should create a re-engagement sequence (3-4 emails). Should follow the re-engagement
+    pattern: first email acknowledges absence and offers value, middle emails escalate with
+    compelling reasons to re-engage, final email is a clear ''last chance'' before removal.
+    Should recommend aggressive subject lines to break through. Should include a sunset policy
+    (remove non-responders after sequence completes). Should address the impact on deliverability
+    of keeping inactive subscribers.'
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-email-sequence-05
+  department: marketing
+  prompt: What's the ideal timing for our onboarding email sequence? We send the first email
+    immediately after signup, but we're not sure about the rest.
+  expected_properties:
+  - Provides timing guidance for onboarding sequences
+  - Recommends immediate first email
+  - Discusses behavior-triggered vs time-based timing
+  - Provides typical timing patterns
+  - Notes timing depends on product and trial length
+  - Recommends behavior triggers with time-based fallbacks
+  rubric: 'Should provide timing guidance for onboarding sequences. Should reference the timing
+    and delays framework: immediate first email (welcome/confirmation), then suggest data-driven
+    timing based on user behavior triggers vs fixed time delays. Should recommend behavior-triggered
+    emails when possible (user completed action → next email) with time-based fallbacks. Should
+    provide typical timing patterns for SaaS onboarding (day 0, day 1, day 3, day 5, day 7,
+    etc.). Should note that optimal timing depends on product complexity and trial length.'
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-email-sequence-06
+  department: marketing
+  prompt: Help me optimize our post-signup onboarding experience. Users sign up but 60% never
+    complete setup.
+  expected_properties:
+  - Recognizes this as in-app onboarding optimization
+  - References or defers to onboarding skill
+  - Does not attempt full onboarding redesign using email patterns
+  - May offer email component support
+  rubric: Should recognize this is an in-app onboarding optimization task, not an email sequence
+    task. Should defer to or cross-reference the onboarding skill, which handles in-app onboarding
+    flows, checklists, and activation optimization. May offer to help with the email component
+    of onboarding but should make clear that onboarding is the primary skill for this task.
+  tags:
+  - email-sequence
+  - imported
+- id: marketing-free-tools-01
+  department: marketing
+  prompt: We want to build a free tool to drive leads for our SEO software. We're thinking
+    about an SEO audit tool or a keyword research tool. Which would be better and how should
+    we approach it?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies evaluation scorecard to compare options
+  - References tool types from the skill
+  - Recommends one option with clear rationale
+  - Discusses lead capture gating strategy
+  - Addresses MVP scope
+  - Provides implementation recommendations
+  rubric: Should check for product-marketing.md first. Should apply the evaluation scorecard
+    to compare both tool ideas across dimensions (audience alignment, lead quality, build
+    effort, SEO value, maintenance burden, competitive differentiation). Should reference
+    the tool types from the skill (analyzers, testers). Should recommend the stronger option
+    with rationale. Should discuss lead capture gating strategy (what's free vs what requires
+    email). Should address MVP scope — what's the minimum valuable version. Should provide
+    implementation recommendations.
+  tags:
+  - free-tools
+  - imported
+- id: marketing-free-tools-02
+  department: marketing
+  prompt: I want to build a free ROI calculator for our HR software. Users input their company
+    size and current processes, and it shows how much time and money they'd save.
+  expected_properties:
+  - Identifies as calculator tool type
+  - Applies ideation framework to validate
+  - Discusses lead capture gating strategy
+  - Addresses build vs buy decision
+  - Recommends MVP scope (inputs, outputs, formula)
+  - Discusses SEO considerations
+  - References evaluation scorecard
+  rubric: 'Should identify this as a calculator tool type. Should apply the ideation framework
+    to validate the concept. Should discuss lead capture strategy: should the basic result
+    be free and detailed report gated? Should address the build vs buy decision. Should recommend
+    MVP scope (what inputs, what outputs, what formula). Should discuss SEO considerations
+    for the tool page. Should reference the evaluation scorecard to score the idea.'
+  tags:
+  - free-tools
+  - imported
+- id: marketing-free-tools-03
+  department: marketing
+  prompt: give me some ideas for free tools we could build. we sell email marketing software
+    for e-commerce brands.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies ideation framework
+  - Generates ideas across multiple tool types
+  - Ideas are relevant to email marketing + e-commerce
+  - Provides 5-8 ideas
+  - Briefly evaluates each idea
+  - Recommends top 2-3 to pursue
+  rubric: 'Should trigger on casual phrasing. Should apply the ideation framework to generate
+    tool ideas relevant to email marketing + e-commerce. Should provide 5-8 ideas across different
+    tool types (calculators, generators, analyzers, testers). Examples: email subject line
+    tester, email deliverability checker, email ROI calculator, email template generator,
+    spam score checker. Should briefly score each against the evaluation dimensions. Should
+    recommend top 2-3 to pursue.'
+  tags:
+  - free-tools
+  - imported
+- id: marketing-free-tools-04
+  department: marketing
+  prompt: We built a free website speed test tool 6 months ago but it's barely getting any
+    traffic. What went wrong and how do we fix it?
+  expected_properties:
+  - Diagnoses potential traffic issues
+  - Investigates SEO strategy for the tool
+  - Assesses competitive landscape
+  - Questions unique value proposition
+  - Applies engineering as marketing principles
+  - Recommends recovery plan with specific actions
+  rubric: 'Should diagnose why the tool isn''t getting traffic. Should investigate: SEO strategy
+    for the tool page (target keywords, on-page optimization), distribution strategy (was
+    it launched and forgotten?), competitive landscape (are there dominant free tools already?),
+    tool quality and UX (does it provide unique value?). Should apply the engineering as marketing
+    principles. Should recommend a recovery plan: SEO improvements, content marketing around
+    the tool, product improvements for differentiation.'
+  tags:
+  - free-tools
+  - imported
+- id: marketing-free-tools-05
+  department: marketing
+  prompt: Should we gate our free tool behind an email capture or make it completely free?
+    We want leads but don't want to kill usage.
+  expected_properties:
+  - Applies lead capture gating strategy
+  - Presents gating spectrum (ungated to fully gated)
+  - Recommends partial gating approach
+  - Discusses tradeoffs of each approach
+  - Provides specific gating recommendations
+  - Addresses SEO impact of gating decisions
+  rubric: 'Should apply the lead capture gating strategy framework. Should present the spectrum:
+    fully ungated → partial gating (basic results free, detailed report gated) → fully gated.
+    Should recommend partial gating as the typical best approach — give enough value to demonstrate
+    the tool''s worth, gate the detailed/actionable output. Should discuss tradeoffs: ungated
+    = more SEO value and usage, gated = more leads but fewer users. Should provide specific
+    gating recommendations based on tool type.'
+  tags:
+  - free-tools
+  - imported
+- id: marketing-free-tools-06
+  department: marketing
+  prompt: How do I optimize the landing page for our free tool to get more signups? The tool
+    itself is great but nobody finds it.
+  expected_properties:
+  - Recognizes this as page CRO, not free tool strategy
+  - References or defers to cro skill
+  - May provide free-tool-specific context
+  - Does not attempt full page CRO using free tool strategy patterns
+  rubric: Should recognize this is a landing page conversion optimization task, not a free
+    tool strategy task. Should defer to or cross-reference the cro skill for optimizing the
+    tool's landing page conversion rate. May provide free-tool-specific context (gating strategy,
+    value demonstration) but should make clear that cro is the right skill for page conversion
+    optimization.
+  tags:
+  - free-tools
+  - imported
+- id: marketing-council-01
+  department: marketing
+  prompt: We're a B2B SaaS about to cut our price 40% to compete with a cheaper rival. Have
+    the council review this.
+  expected_properties:
+  - Includes the simulation disclaimer
+  - Seats 3-5 advisors appropriate to a pricing question
+  - Includes at least one genuine dissenter
+  - Each take applies that advisor's named frameworks to the user's specifics
+  - Includes a disagreement map with underlying trade-offs
+  - Ends with a chair's synthesis and skill handoffs
+  - No fabricated quotes
+  rubric: Should check for product-marketing.md, restate the question and stakes, and seat
+    3-5 advisors fitting an offer/pricing question (e.g., Hormozi, Halbert) plus at least
+    one designated dissenter (e.g., Sutherland on price-as-signal or Godin on race-to-the-bottom).
+    Should open with the simulation disclaimer. Each take should apply that advisor's documented
+    frameworks (value equation, starving crowd, costly signaling) to the specifics rather
+    than generic advice. Must include a disagreement map naming the underlying trade-offs
+    and a chair's synthesis with concrete next steps and skill handoffs (pricing, offers).
+  tags:
+  - council
+  - imported
+- id: marketing-council-02
+  department: marketing
+  prompt: 'What would David Ogilvy say about this headline: ''Revolutionize your workflow
+    with AI-powered synergy''?'
+  expected_properties:
+  - Runs quick-take mode with one advisor, not a full council
+  - Applies Ogilvy's documented headline doctrine specifically
+  - Uses only verifiable quotes, attributed
+  - Offers a concrete improvement direction
+  - Labels the take as simulation
+  rubric: 'Quick-take mode: one advisor, loading only the Ogilvy dossier. Should critique
+    through his documented doctrine — headlines carry 80% of the spend, promise a specific
+    benefit, avoid vague superlatives and jargon (''the consumer is not a moron''), demand
+    the Big Idea and factual specificity. Should not fabricate verbatim Ogilvy quotes beyond
+    documented ones, and should offer a rewrite direction consistent with his method. May
+    hand off to copywriting for execution.'
+  tags:
+  - council
+  - imported
+- id: marketing-council-03
+  department: marketing
+  prompt: Convene the full council and have them tell me my niche newsletter strategy is right.
+    I want validation that focusing on 500 superfans beats chasing reach.
+  expected_properties:
+  - Does not produce uniform agreement
+  - Sharp's reach/penetration counter-position is represented in substance
+  - Supportive takes (Godin/Handley) are grounded in their actual frameworks
+  - Disagreement map names the reach-vs-resonance trade-off and evidence to settle it
+  - Gently flags that seeking validation from the council is an anti-pattern
+  rubric: Should not simply validate. The council must include genuine dissent — Byron Sharp's
+    penetration/reach laws and double jeopardy directly challenge superfan-focus strategies,
+    and Vaynerchuk's interest-graph volume position also conflicts. Godin and Handley would
+    support the smallest-viable-audience direction. The disagreement map should name the real
+    trade-off (reach vs. resonance, and what evidence would settle it for this business).
+    Should push back on 'I want validation' framing — an agreeing council is an anti-pattern.
+    Full council is allowed since the user asked, but the output should stay structured.
+  tags:
+  - council
+  - imported
+- id: marketing-council-04
+  department: marketing
+  prompt: Add my old boss Maria to the council. She always said 'ship weekly or die' and hated
+    paid ads.
+  expected_properties:
+  - Creates the dossier at .agents/advisors/ (outside the skill folder)
+  - Follows the advisor-template structure
+  - Asks the user to supply positions rather than inventing them
+  - Does not fabricate views for a real private person
+  rubric: 'Should use the custom advisor flow: create a dossier from references/advisor-template.md
+    structure, saved to .agents/advisors/maria.md in the user''s project (not inside the skill).
+    Because Maria is a private person, the agent must interview the user for her positions
+    rather than inventing views — it can structure what the user supplied (''ship weekly'',
+    anti-paid-ads) but should ask for more before treating the dossier as complete (frameworks,
+    blind spots, voice). Must not fabricate positions beyond what the user provides.'
+  tags:
+  - council
+  - imported
+- id: marketing-council-05
+  department: marketing
+  prompt: Have the council debate whether we should rebrand. Also — what did Rory Sutherland
+    say about AI last month?
+  expected_properties:
+  - Does not fabricate a recent Sutherland statement
+  - Runs a live research pass (or declines to attribute) for the recency question
+  - Rebrand debate includes Sharp's distinctive-assets/memory-structures warning
+  - Output remains clearly labeled as simulation
+  rubric: 'The rebrand debate should proceed with an appropriate bench (e.g., Sharp on distinctive
+    assets and the danger of discarding memory structures, Godin, Dunford). For the Sutherland-on-AI
+    question: the dossier notes his AI takes evolve quickly and directs to the research pass
+    for current ones — ''last month'' is a recency question, so the agent must run a live
+    research pass (deep-research or web search) and answer with citations rather than answering
+    from the dossier alone or fabricating a recent statement. If research is unavailable,
+    it should say it cannot attribute a recent position without sources.'
+  tags:
+  - council
+  - imported
+- id: marketing-marketing-ideas-01
+  department: marketing
+  prompt: I need marketing ideas for my SaaS product. We're a bootstrapped team of 3, sell
+    a $49/month analytics tool for e-commerce, and have about 200 customers. Budget is tight
+    — maybe $500/month for marketing.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Filters ideas by low budget constraint
+  - Provides ideas from the 139 marketing ideas catalog
+  - Ideas are appropriate for bootstrapped SaaS stage
+  - Output follows structured format per idea
+  - Includes why it fits, how to start, expected outcome
+  - Prioritizes by likely impact
+  - Includes resources needed per idea
+  rubric: 'Should check for product-marketing.md first. Should filter ideas by low budget
+    and early-stage constraints. Should pull relevant ideas from the 139 marketing ideas organized
+    by category. Should provide ideas appropriate for bootstrapped SaaS: content marketing,
+    community building, SEO, partnerships, referral programs, social media, Product Hunt,
+    and others that don''t require large budgets. Output should follow the format: idea name,
+    why it fits, how to start, expected outcome, resources needed. Should prioritize by likely
+    impact given their stage.'
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-ideas-02
+  department: marketing
+  prompt: What's the fastest way to get more leads? We sell enterprise security software and
+    have a $10k/month marketing budget.
+  expected_properties:
+  - Applies 'leads fast' use case filter
+  - Recommends paid channels appropriate for enterprise
+  - Recommends outbound tactics
+  - Filters for enterprise-appropriate tactics
+  - Provides structured output per idea
+  - Notes that fast leads means paid or outbound
+  - Includes timeline expectations
+  rubric: Should apply the 'top ideas by use case' — specifically 'leads fast' recommendations.
+    Should recommend paid channels (Google Ads, LinkedIn Ads for enterprise), outbound (cold
+    email, LinkedIn outreach), and content-based lead magnets. Should filter for enterprise-appropriate
+    tactics. Should provide the structured output with why each idea fits, how to start, expected
+    timeline, and resources needed. Should note that 'fast leads' typically means paid or
+    outbound channels.
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-ideas-03
+  department: marketing
+  prompt: how do we grow without spending money on ads? we're a PLG (product-led growth) company
+    with a freemium model
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies PLG use case filter
+  - Recommends PLG-specific tactics
+  - Avoids ad-dependent ideas
+  - Includes virality and referral tactics
+  - Provides structured output with implementation guidance
+  rubric: 'Should trigger on casual phrasing. Should apply the ''PLG'' use case filter from
+    top ideas. Should recommend PLG-specific tactics: product virality features, referral
+    programs, community building, content marketing, SEO, free tools/calculators, open-source
+    contributions, social proof loops. Should avoid ad-dependent ideas given the constraint.
+    Should provide structured output with implementation guidance.'
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-ideas-04
+  department: marketing
+  prompt: We want to build authority and thought leadership in the HR tech space. We're a
+    newer company and nobody knows who we are yet.
+  expected_properties:
+  - Applies 'authority building' use case filter
+  - Recommends thought leadership tactics
+  - Includes original research and content
+  - Includes community and media appearances
+  - Notes authority building is longer-term
+  - Provides structured output with timelines
+  rubric: 'Should apply the ''authority building'' use case filter. Should recommend thought
+    leadership tactics: original research/surveys, guest posting, podcast appearances, speaking
+    engagements, LinkedIn content, industry report publishing, expert roundups. Should note
+    that authority building is a longer-term play. Should provide structured output with how
+    to start each idea, expected outcomes, and timeline.'
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-ideas-05
+  department: marketing
+  prompt: Give me 20 marketing ideas. We sell project management software.
+  expected_properties:
+  - Provides approximately 20 ideas
+  - Ideas span multiple categories
+  - Organizes by category or effort/impact
+  - Provides brief implementation context per idea
+  - Output follows structured format
+  - Ideas are relevant to project management software
+  rubric: Should provide a curated list of ~20 ideas from the catalog. Should organize them
+    by category or by effort/impact. Should provide brief implementation context for each.
+    Should vary the ideas across categories (content, community, partnerships, product, paid,
+    etc.) for a well-rounded set. Output should follow the structured format with at least
+    idea name and brief description for each.
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-ideas-06
+  department: marketing
+  prompt: We want to set up a referral program. How should we structure it?
+  expected_properties:
+  - Recognizes this as a referral program design request
+  - References or defers to referrals skill
+  - Does not attempt detailed referral program design
+  - May briefly mention as a marketing idea
+  rubric: Should recognize this is specifically a referral program design request. Should
+    defer to or cross-reference the referrals skill, which provides detailed guidance on referral
+    loop design, incentive structures, implementation, and optimization. May briefly mention
+    referral programs as a marketing idea but should make clear that referrals is the right
+    skill for detailed program design.
+  tags:
+  - marketing-ideas
+  - imported
+- id: marketing-marketing-loops-01
+  department: marketing
+  prompt: I want to set up a recurring loop that watches our SEO and tells me what to do each
+    week. We're a B2B SaaS with a content-heavy site.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Selects appropriate SEO loop(s) from the catalog
+  - Presents the loop with the nine-part anatomy
+  - Includes state/idempotency (last-run marker or dedupe)
+  - Includes an explicit stop/bail-out condition
+  - Sets a weekly cadence and justifies it via the cadence rule
+  - References seo-audit or related skills for execution
+  rubric: 'Should check for product-marketing.md first. Should recognize this maps to SEO
+    loops in the catalog (keyword-gap, ranking-drop watch, content-decay) and propose the
+    closest match(es). Should present the loop using the nine-part anatomy: check cadence,
+    acts-when (action condition), purpose, skills used, loop body, self-check, state/idempotency,
+    stop/bail-out, and output. Should set a weekly cadence (matching how slowly rankings move)
+    and explain the cadence rule. Should include a stop/bail-out and note that most runs may
+    find no action. Should reference the seo-audit skill for execution.'
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-02
+  department: marketing
+  prompt: I want to automate my marketing so it basically runs itself. Where do I start?
+  expected_properties:
+  - Asks about the target outcome / funnel stage before recommending
+  - Avoids banned autopilot vocabulary
+  - Recommends starting with one loop, not many
+  - Frames loops as systems with checkpoints, not magic
+  - Emphasizes human checkpoints for spend/publish actions
+  - May suggest the weekly-marketing-review loop as a starting point
+  rubric: Should clarify the outcome to protect or grow before dumping loops (acquisition,
+    activation, retention, revenue, referral). Should push back gently on 'runs itself' framing
+    and avoid the banned vocabulary ('set it and forget it', 'fully autonomous'). Should recommend
+    starting with ONE loop and proving it earns its keep rather than building many at once.
+    Should describe loops as disciplined systems with checkpoints, not autopilot. Should likely
+    suggest the weekly-marketing-review loop as a good first heartbeat loop, and explain human
+    checkpoints for anything that spends or publishes.
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-03
+  department: marketing
+  prompt: Set up a newsjacking loop that finds trending stories and automatically posts our
+    take to X and pitches journalists.
+  expected_properties:
+  - Builds the newsjacking loop with the nine-part anatomy
+  - Includes an explicit veto list for sensitive story types
+  - Requires human approval before pitching or posting
+  - Does not enable fully autonomous posting
+  - Includes dedupe/state so stories aren't re-pitched
+  - References the public-relations skill
+  rubric: Should build the newsjacking loop but refuse to make it fully autonomous. Must include
+    the veto list (skip tragedies, deaths, disasters, active crises, politically/socially
+    charged stories unless the brand takes such stances, and legal/medical/financial-sensitive
+    topics) and require verified sources. Must require human approval before any pitch or
+    post rather than auto-posting. Should include state/idempotency (dedupe per story, one
+    angle per story) and note most days will correctly skip. Should reference the public-relations
+    skill.
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-04
+  department: marketing
+  prompt: How do I actually schedule these loops so they run on their own?
+  expected_properties:
+  - Explains scheduling is environment-dependent
+  - Covers Claude Code native options and plain cron
+  - Includes manual cadence as a valid option
+  - Gives cron vs dynamic-pacing default guidance
+  - Treats loopify as optional, not a required dependency
+  rubric: 'Should explain that the loop body is agent-agnostic but scheduling depends on the
+    environment. Should cover the options: Claude Code native primitives (/loop, ScheduleWakeup,
+    CronCreate), any-agent + cron (with an example cron expression), and manual cadence for
+    high-judgment loops. Should default to time-of-day cron for review-style loops and dynamic
+    pacing for monitor-until-threshold loops. Should treat a dedicated loop-mechanics skill
+    like loopify as an optional companion, not a hard dependency, and not assume it is installed.'
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-05
+  department: marketing
+  prompt: Can you make me a loop that continuously improves our brand positioning and comes
+    up with our big campaign ideas?
+  expected_properties:
+  - Identifies this as a 'when NOT to loop' case
+  - Explains loops optimize/maintain rather than set strategy or creative
+  - Redirects strategy/creative to the appropriate non-loop work
+  - Suggests adjacent operational loops that genuinely fit
+  - Does not force an ill-fitting positioning/campaign-ideation loop
+  rubric: 'Should push back: strategy, positioning, and creative direction are the ''when
+    NOT to loop'' cases. Loops maintain and optimize; they don''t set positioning or invent
+    campaigns. Should explain why (high-judgment, low-frequency, not signal-driven) and redirect:
+    those belong in strategy work, while loops can operationalize the executional follow-through
+    (e.g., competitor-watch to inform positioning, content-calendar refill, campaign-postmortem
+    to compound learnings). Should not fabricate a positioning loop as if it were a good fit.'
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-06
+  department: marketing
+  prompt: We keep losing customers to failed payments and expired cards. Set up something
+    to recover that revenue automatically.
+  expected_properties:
+  - Selects the failed-payment/dunning loop
+  - Triggers on failed payment or card expiration
+  - Includes a retry schedule with dunning stage state
+  - Has a stop condition so it does not loop forever
+  - Self-check separates involuntary failures from intentional cancels
+  - References revops and/or emails skills
+  rubric: Should select the failed-payment/dunning loop. Should trigger on payment failure
+    or upcoming card expiration, run a retry schedule with escalating update-card messaging,
+    and include state (track dunning stage per account, stop on recovery). Must include a
+    stop/bail-out so it doesn't loop forever (escalate/deactivate after final retry) and a
+    self-check to distinguish involuntary failures from intentional cancellations (don't dun
+    someone who chose to leave). Should reference revops and emails skills. May note this
+    is often the highest-ROI retention loop.
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-loops-07
+  department: marketing
+  prompt: I want a loop that keeps our A/B testing program running — generating hypotheses,
+    running tests, and analyzing results every week.
+  expected_properties:
+  - Recognizes overlap with the ab-testing skill
+  - Keeps the loop as a thin wrapper that defers to ab-testing
+  - Does not duplicate test design or statistical analysis in the loop
+  - Includes backlog prioritization (ICE) and hypothesis dedupe
+  - References the ab-testing skill as the owner of execution
+  rubric: Should recognize heavy overlap with the ab-testing skill and treat the experiment-backlog
+    loop as a thin wrapper only. The loop should maintain and re-rank the hypothesis backlog
+    and manage hand-off cadence, but defer test design, statistical analysis, and velocity
+    management to the ab-testing skill rather than duplicating them. Should include ICE prioritization
+    for the backlog and dedupe of incoming hypotheses, and avoid starting conflicting tests.
+  tags:
+  - marketing-loops
+  - imported
+- id: marketing-marketing-plan-01
+  department: marketing
+  prompt: I'm starting a fractional CMO engagement with a Series A B2B SaaS doing $2M ARR,
+    12-person team with 1 marketer, $20K/month marketing budget. They want a marketing plan
+    we can share with the team and the board. Build it.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks for client name or uses a slug
+  - Walks through INIT phase with structured intake
+  - Produces 13-section plan structured by AARRR
+  - Section 3 scores against the embedded 17-section rubric
+  - Section 9 (90-day roadmap) has owner-assigned moves, not just actions
+  - Section 10 names funding-stage capability unlocks explicitly
+  - Section 11 maps marketing skills + MCPs to each AARRR stage
+  - Section 12 cross-references all 139 marketing-ideas with client-specific status
+  - Output is Notion-paste-ready markdown
+  - Plan is specific to the client (their budget, team, current channels), not generic
+  rubric: 'Should check for product-marketing.md first. Should ask for client name or use
+    a slug. Should walk through three-phase workflow (INIT → REVIEW → FINALIZE), starting
+    with intake covering funding state, team, budget, channels, what''s done, in-flight, tooling
+    stack. Should produce a 13-section AARRR-structured plan: executive summary, strategic
+    frame, current state (scored against the embedded 17-section rubric), Acquisition, Activation,
+    Retention, Referral, Revenue, 90-day roadmap with owner-assigned moves, 12-month outlook
+    with funding-stage capability unlocks, marketing operations stack mapping skills + MCPs
+    to AARRR stages, tactical idea bank cross-referencing all 139 marketing-ideas to AARRR
+    + client-specific status, measurement framework with north-star + leading indicators +
+    RACI + open decisions. Should be ~8–12K words, Notion-paste-ready. Should be specific
+    to the client (their budget, team, channels), not generic.'
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-plan-02
+  department: marketing
+  prompt: We're pre-seed bootstrapped, $0 paid marketing budget, 4-person team building a
+    D2C consumer app. Founder wants a 90-day plan + 12-month roadmap they can show investors
+    during the upcoming raise. The product is in beta.
+  expected_properties:
+  - Recognizes pre-seed tier and uses Tier 1 budget profile
+  - Skips paid acquisition recommendations until budget unlocks
+  - Leans Acquisition on organic + lifecycle + ambassador
+  - Names what unlocks when seed closes
+  - Accounts for product being in beta
+  - Identifies binding-constraint AARRR stage (likely Activation or Referral)
+  - Executive summary can be lifted into an investor update
+  - Plan is operationally honest — doesn't pretend paid budget exists
+  rubric: 'Should recognize Tier 1 funding profile (pre-seed) and skip paid acquisition recommendations
+    until budget unlocks. Should lean Acquisition heavy on organic + lifecycle + ambassador
+    moves. Should explicitly map what unlocks when seed closes (paid test budget $5–15K/mo,
+    first marketing hire, etc.). Should respect that the product is in beta and account for
+    activation/throttling gates. Should include the AARRR diagnostic — likely binding constraint
+    at this stage is Activation (onboarding) and Referral. Plan must be investor-friendly:
+    exec summary can be lifted into an update.'
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-plan-03
+  department: marketing
+  prompt: we have an audit already done — can you take that and turn it into a real plan
+  expected_properties:
+  - Asks for the audit output
+  - Ingests prior audit scoring directly into Section 3
+  - Does not re-score what's already been scored
+  - Notes the scoring date and flags any shifted material
+  - Uses audit gaps to inform 90-day roadmap and AARRR section moves
+  - Still produces a full 13-section plan, not just Section 3
+  rubric: Should ask for the audit output (file path or paste). Should recognize that current-state
+    scoring already exists and ingest it directly into Section 3 — don't re-score. Should
+    note scoring date in case material has shifted since. Should proceed with full 13-section
+    plan generation using audit findings to inform 90-day roadmap and AARRR sections (gaps
+    from audit become moves in the plan).
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-plan-04
+  department: marketing
+  prompt: /marketing-plan acme-saas — pick up where we left off
+  expected_properties:
+  - Reads ~/marketing-plans/acme-saas/progress.md
+  - Resumes from next unfinished section based on state machine
+  - Does not silently restart from scratch
+  - Handles finalized state by asking user how to proceed (revise / fresh / re-open)
+  - Saves each newly confirmed section to the progress file
+  rubric: 'Should read ~/marketing-plans/acme-saas/progress.md to determine state machine
+    phase. Should resume from the next unfinished section in REVIEW phase, or transition to
+    FINALIZE if all sections approved. Should NOT silently restart from scratch. If progress.md
+    is missing or shows ''finalized'', should ask: revise as v{N+1}, start fresh, or re-open
+    a section.'
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-plan-05
+  department: marketing
+  prompt: I need a plan for a hybrid hardware+software wellness company. They sell a physical
+    product and a subscription app. Series A, $100K/month marketing budget, 8-person team
+    including a marketing lead.
+  expected_properties:
+  - Recognizes hybrid hardware+software archetype
+  - Acquisition leans on PR, retail, Amazon, Shopify SEO, paid
+  - Activation covers unboxing, setup, first session, paywall
+  - Retention covers lifecycle, community
+  - Referral covers gifting, reviews
+  - Revenue covers blended LTV with hardware + subscription + accessories
+  - Recognizes Series A tier in budget recommendations
+  - Idea bank skips ideas that conflict with brand fit, with explicit rationale
+  rubric: Should recognize hybrid hardware+software archetype and consult references/client-types.md
+    for archetype-specific emphases. Acquisition leans PR + retail + Amazon + Shopify SEO
+    + paid. Activation = unboxing + setup + first session + paywall. Retention = lifecycle
+    + community. Referral = gifting + reviews. Revenue = blended LTV (hardware + subscription
+    + accessories). Should recognize Series A tier and recommend appropriate paid spend. Should
+    include cross-cutting brand + customer-research moves. Idea bank should skip ideas that
+    conflict with premium positioning or hardware constraints.
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-plan-06
+  department: marketing
+  prompt: Just give me a quick marketing plan. Don't make it long.
+  expected_properties:
+  - Resists short-plan request and explains why
+  - Names marketing-plan as the comprehensive fCMO artifact
+  - Recommends channel-specific skills for single-channel quick plans
+  - Offers alternatives clearly
+  - Does not silently produce a stripped-down plan
+  rubric: 'Should resist defaulting to a short plan. Should explain that a marketing-plan
+    is the comprehensive fCMO-deliverable artifact (~10K words) and that for a single-channel
+    quick plan, the channel-specific skill is the right tool (emails, ads, seo-audit, etc.).
+    Should offer alternatives: (a) full marketing-plan as designed, or (b) point to a specific
+    skill for the user''s actual need. Should NOT silently produce a stripped-down 3K-word
+    plan that misses the ops stack or the idea bank.'
+  tags:
+  - marketing-plan
+  - imported
+- id: marketing-marketing-psychology-01
+  department: marketing
+  prompt: How can I use psychology to increase conversions on our pricing page? We sell a
+    B2B SaaS tool with three tiers ($29, $79, $199/month).
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies pricing psychology models (anchoring, charm pricing, Rule of 100)
+  - Applies Good-Better-Best framing
+  - Applies loss aversion to tier differentiation
+  - Applies social proof near pricing
+  - Provides specific recommendations for their price points
+  - References specific mental models by name
+  rubric: 'Should check for product-marketing.md first. Should apply relevant pricing psychology
+    models: anchoring (show the highest plan first or use a decoy), charm pricing (consider
+    $29 vs $30), Rule of 100 (percentage vs dollar discounts), Good-Better-Best framing, loss
+    aversion (show what they miss on lower tiers). Should also apply broader persuasion models:
+    social proof near pricing, scarcity for limited-time offers, default effect (pre-select
+    recommended plan). Should provide specific, actionable recommendations tied to their price
+    points.'
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-marketing-psychology-02
+  department: marketing
+  prompt: Explain the scarcity principle and how to use it ethically in SaaS marketing without
+    being manipulative.
+  expected_properties:
+  - Explains scarcity principle clearly
+  - Provides legitimate SaaS applications
+  - Distinguishes ethical from manipulative use
+  - Provides specific examples
+  - References related mental models
+  - Addresses ethical considerations directly
+  rubric: 'Should explain scarcity as a mental model (limited availability increases perceived
+    value). Should provide legitimate SaaS applications: limited beta spots, early-bird pricing
+    with real deadlines, limited-time feature access, cohort-based launches. Should distinguish
+    ethical scarcity (real constraints) from manufactured urgency (fake countdown timers,
+    artificial limits). Should provide specific examples and implementation guidance. Should
+    reference related models (urgency, FOMO, loss aversion).'
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-marketing-psychology-03
+  department: marketing
+  prompt: what psychological principles should I use to write better marketing copy?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Recommends copy-relevant mental models
+  - Explains each principle briefly
+  - Provides specific copywriting application per principle
+  - Organizes by where each applies in copy
+  - References multiple model categories
+  rubric: 'Should trigger on casual phrasing. Should recommend copy-relevant mental models
+    from the skill''s taxonomy: social proof, reciprocity, loss aversion, anchoring, scarcity,
+    IKEA Effect, Endowment Effect, Commitment & Consistency. For each principle, should explain
+    what it is and provide a specific copywriting application. Should reference the quick
+    reference table by challenge. Should organize by where in the copy each principle applies
+    (headlines, body, CTAs, testimonials).'
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-marketing-psychology-04
+  department: marketing
+  prompt: I'm designing an onboarding flow and want to use behavioral psychology to increase
+    activation. What models should I apply?
+  expected_properties:
+  - Applies Goal-Gradient Effect
+  - Applies Hick's Law
+  - Applies IKEA Effect or Endowment Effect
+  - Applies Zeigarnik Effect or commitment principles
+  - Explains how each applies to onboarding
+  - Provides actionable recommendations per model
+  rubric: 'Should apply design and behavioral models from the skill''s taxonomy: Goal-Gradient
+    Effect (motivation increases near goal), Hick''s Law (reduce choices), IKEA Effect (let
+    users build something), Endowment Effect (let them experience ownership), Zeigarnik Effect
+    (incomplete tasks drive completion), Commitment & Consistency (small asks first). Should
+    explain how each applies to onboarding specifically. Should provide actionable recommendations
+    for each model.'
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-marketing-psychology-05
+  department: marketing
+  prompt: What's the psychology behind why free trials work better than freemium for some
+    products?
+  expected_properties:
+  - Applies loss aversion to trial context
+  - Applies endowment effect
+  - Applies Zero-Price Effect
+  - Explains how models interact in trial vs freemium
+  - Notes when each approach works best
+  - Provides clear, educational explanation
+  rubric: 'Should apply relevant mental models: loss aversion (trial users fear losing access),
+    endowment effect (they feel ownership after using), sunk cost (time invested during trial),
+    Zero-Price Effect (free removes psychological barrier to start), status quo bias (inertia
+    to keep what they have). Should explain how these models interact in trial vs freemium
+    contexts. Should note when each model works best (trial for products with high activation
+    effort, freemium for products with network effects).'
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-marketing-psychology-06
+  department: marketing
+  prompt: Help me run an A/B test on which psychological principle works better for our CTA
+    — scarcity vs social proof.
+  expected_properties:
+  - Recognizes this as an A/B test setup task
+  - References or defers to ab-testing skill
+  - May provide psychological context for hypothesis
+  - Does not attempt full test design using psychology patterns
+  rubric: Should recognize this is an A/B test setup task, not a psychology task. Should defer
+    to or cross-reference the ab-testing skill for the experiment design. May provide psychological
+    context on both principles to inform the hypothesis, but should make clear that ab-testing
+    is the right skill for designing and running the experiment.
+  tags:
+  - marketing-psychology
+  - imported
+- id: marketing-product-marketing-01
+  department: marketing
+  prompt: I want to set up my product marketing context. We're a B2B SaaS company that sells
+    a customer feedback platform to product teams.
+  expected_properties:
+  - Checks for existing product-marketing.md
+  - 'Offers two options: auto-draft or start from scratch'
+  - Covers applicable sections
+  - Walks through sections conversationally one at a time
+  - Creates file at .agents/product-marketing.md
+  rubric: 'Should check if .agents/product-marketing.md already exists. If not, should offer
+    two options: (1) Auto-draft from codebase (recommended) or (2) Start from scratch. If
+    user chooses start from scratch, should walk through sections conversationally one at
+    a time. Should cover all applicable sections: Product Overview, Target Audience, Personas,
+    Problems You Solve, Competitive Landscape, Differentiation, Objections, Switching Dynamics,
+    Customer Language, Brand Voice, Proof Points, and Goals. Should create the file at .agents/product-marketing.md
+    when complete.'
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-02
+  department: marketing
+  prompt: Update our product marketing context. We just added a new enterprise tier and our
+    target audience has expanded to include VP of Engineering, not just Product Managers.
+  expected_properties:
+  - Reads existing product-marketing.md
+  - Identifies sections that need updating
+  - Updates Target Audience with VP of Engineering
+  - Adds new persona for the expanded audience
+  - Updates Product Overview for enterprise tier
+  - Preserves unchanged sections
+  rubric: 'Should check for existing .agents/product-marketing.md and read it. Should identify
+    which sections need updating based on the changes: Target Audience (add VP of Engineering),
+    Personas (add new persona), Product Overview (new enterprise tier, including pricing updates
+    within that section), Objections (enterprise-specific), and Competitive Landscape (enterprise
+    competitors). Should update only the relevant sections, preserving existing content that
+    hasn''t changed.'
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-03
+  department: marketing
+  prompt: create a product context doc for my app. it's a mobile app that helps people find
+    hiking trails. we're just getting started.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Checks for existing context doc
+  - Offers auto-draft or start-from-scratch options
+  - Adapts questions for early-stage B2C mobile app
+  - Notes some sections may be sparse early on
+  - Skips non-applicable sections rather than forcing all 12
+  - Creates file at .agents/product-marketing.md
+  rubric: Should trigger on casual phrasing. Should check for existing context doc. Should
+    offer auto-draft or start-from-scratch options. Should adapt questions for an early-stage
+    B2C mobile app (outdoor/fitness niche). Should note that some sections may be sparse for
+    an early-stage product and that's okay — they can be filled in as the business matures.
+    Should skip non-applicable sections (e.g., Personas section is B2B-focused) rather than
+    forcing all 12. Should accept lighter answers for sections like Proof Points or Competitive
+    Landscape if the company is new.
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-04
+  department: marketing
+  prompt: Can you auto-draft our product marketing context from our existing codebase and
+    marketing materials?
+  expected_properties:
+  - Activates auto-draft workflow mode
+  - Scans codebase for existing marketing materials
+  - Drafts context from found information
+  - Flags sections needing manual input
+  - Presents draft for review before saving
+  rubric: 'Should activate the auto-draft workflow mode. Should scan the codebase for existing
+    marketing context: README, landing page copy, pricing page, about page, meta descriptions,
+    any existing documentation. Should draft the product-marketing.md from what it finds,
+    filling in sections where information is available and flagging sections that need manual
+    input. Should present the draft for review before saving.'
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-05
+  department: marketing
+  prompt: Do we have a product marketing context set up? I want to make sure the other marketing
+    skills have context about our product.
+  expected_properties:
+  - Checks both file locations
+  - Reports whether context doc exists
+  - Summarizes contents if found
+  - Offers to create if missing
+  - Explains how other skills use it
+  rubric: Should check for .agents/product-marketing.md (and the older .claude/product-marketing.md
+    location). Should report whether it exists and summarize its contents if found. If it
+    doesn't exist, should offer to create one and explain why it's valuable (other skills
+    like copywriting, cro, seo-audit check for it first). Should explain how other skills
+    use this context document.
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-06
+  department: marketing
+  prompt: Write homepage copy for our SaaS product.
+  expected_properties:
+  - Recognizes this as a copywriting task
+  - May check for or suggest creating product-marketing.md
+  - References or defers to copywriting skill for the actual copy
+  - Does not attempt to write homepage copy using context creation patterns
+  rubric: Should recognize this is a copywriting task, not a product marketing context task.
+    Should check for product-marketing.md (as other skills do), and if it doesn't exist, may
+    suggest creating one first. But should defer to the copywriting skill for actually writing
+    the homepage copy.
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-product-marketing-07
+  department: marketing
+  prompt: We just repositioned — we're no longer an 'email tool,' we're a 'deliverability
+    platform,' and our ICP now includes RevOps teams. Update our product marketing context.
+  expected_properties:
+  - Reads the existing doc and surfaces its current version + recent changelog
+  - Updates only the affected sections (positioning + ICP)
+  - Bumps the Document version and updates Last updated
+  - Prepends a newest-first changelog entry naming what changed and why
+  - Preserves prior changelog entries unchanged
+  rubric: Should recognize an existing .agents/product-marketing.md, read it, note its current
+    Document version and recent Changelog entries, and update only the affected sections (product
+    overview/positioning, target audience/ICP). On save, should bump the Document version
+    (e.g. v2 → v3), update the Last updated date, and PREPEND a new newest-first Changelog
+    entry summarizing what changed and why in one line — e.g. 'Repositioned from email tool
+    to deliverability platform; added RevOps to the ICP' — naming the sections touched and
+    the reason, not just 'updated the doc.' Should not rewrite or reorder past changelog entries.
+    Should tell the user the changelog tracks revisions and that downstream skills will now
+    use the new context.
+  tags:
+  - product-marketing
+  - imported
+- id: marketing-programmatic-seo-01
+  department: marketing
+  prompt: We want to create programmatic SEO pages for our CRM. We're thinking of 'CRM for
+    [industry]' pages — like 'CRM for Real Estate,' 'CRM for Healthcare,' etc. How should
+    we approach this?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies as Personas playbook
+  - Applies core principles (unique value, proprietary data, clean URLs)
+  - Recommends keyword research per variation
+  - Addresses data requirements for unique content
+  - Provides template design guidance
+  - Includes internal linking strategy
+  - Warns against thin content
+  rubric: 'Should check for product-marketing.md first. Should identify this as the Personas
+    playbook (industry-specific pages). Should apply the core principles: unique value per
+    page (not just swapping the industry name), proprietary data or insights per industry,
+    clean URL structure. Should recommend the implementation framework: keyword research for
+    each industry variation, data requirements (what industry-specific content makes each
+    page unique), template design, internal linking strategy between industry pages and main
+    pages, and indexation strategy. Should warn against thin content (just template + keyword
+    swap).'
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-programmatic-seo-02
+  department: marketing
+  prompt: Create a comparison page strategy. We want pages like 'Notion vs Asana', 'Notion
+    vs Monday', etc. for all our competitors. We have 15 competitors.
+  expected_properties:
+  - Identifies as Comparisons playbook
+  - Recommends template structure for scale
+  - Addresses unique data per comparison
+  - Includes keyword research for variations
+  - Provides URL structure recommendation
+  - Includes internal linking strategy
+  - Cross-references competitors skill
+  - Applies quality checks
+  rubric: 'Should identify this as the Comparisons playbook. Should apply the programmatic
+    approach for competitor comparison pages at scale. Should recommend: template structure
+    for comparison pages, unique data per comparison (not just the same template with names
+    swapped), keyword research for each ''[competitor A] vs [competitor B]'' variation, URL
+    structure (/compare/notion-vs-asana), internal linking between comparison pages, and quality
+    checks. Should cross-reference the competitors skill for page content structure.'
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-programmatic-seo-03
+  department: marketing
+  prompt: we want to rank for '[tool name] integration' keywords. we integrate with 50+ tools
+    and want a page for each. like 'Slack integration', 'Salesforce integration' etc.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Identifies as Integrations playbook
+  - Recommends template with unique content per integration
+  - Includes setup steps and use cases per page
+  - Provides URL structure recommendation
+  - Recommends hub page for all integrations
+  - Emphasizes genuine unique value per page
+  rubric: 'Should trigger on casual phrasing. Should identify this as the Integrations playbook.
+    Should recommend: template design for integration pages (what it does, how to set up,
+    use cases), unique content per integration (specific workflows, screenshots, setup steps),
+    keyword research for ''[tool] + [your product] integration'', URL structure (/integrations/slack),
+    hub page linking to all integration pages, and schema markup considerations. Should emphasize
+    that each page needs genuine unique value, not just ''we integrate with [tool].'''
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-programmatic-seo-04
+  department: marketing
+  prompt: We built 500 programmatic pages but Google isn't indexing most of them. Only 80
+    are in the index. What's going wrong?
+  expected_properties:
+  - Diagnoses indexation problem
+  - Investigates thin content as likely cause
+  - Checks crawl budget considerations
+  - Checks internal linking to programmatic pages
+  - Checks XML sitemap and robots.txt
+  - Recommends specific fixes for indexation
+  - Warns about Google's thin content policies
+  rubric: 'Should diagnose the indexation problem. Should apply the quality checks and indexation
+    strategy guidance. Should investigate: thin content (are pages providing unique value
+    or just template + keyword?), crawl budget (500 pages may be fine but depends on site
+    authority), internal linking (are the pages discoverable?), XML sitemap inclusion, duplicate/near-duplicate
+    content issues. Should recommend specific fixes: improve content uniqueness, strengthen
+    internal linking, submit sitemap, check robots.txt, use Search Console for indexation
+    requests. Should warn that Google may choose not to index thin pages regardless.'
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-programmatic-seo-05
+  department: marketing
+  prompt: Help me create a glossary section for our marketing automation platform. We want
+    to define 200+ marketing terms and rank for '[term] definition' keywords.
+  expected_properties:
+  - Identifies as Glossary playbook
+  - Provides template design for term pages
+  - Recommends hub/index page
+  - Provides URL structure
+  - Addresses content quality beyond dictionary definitions
+  - Includes internal linking strategy
+  - Recommends starting with highest-volume terms
+  rubric: 'Should identify this as the Glossary playbook. Should apply the template design:
+    term definition page template (definition, examples, related terms, how it applies to
+    the user''s product), hub/index page linking to all terms, URL structure (/glossary/[term]),
+    alphabetical and categorical navigation. Should address quality: each definition should
+    provide genuine value beyond a dictionary definition. Should include internal linking
+    strategy and schema markup (DefinedTerm schema). Should recommend starting with highest-volume
+    terms.'
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-programmatic-seo-06
+  department: marketing
+  prompt: Can you audit our existing programmatic SEO pages for technical issues? We have
+    crawl errors and some pages return 404s.
+  expected_properties:
+  - Recognizes this as technical SEO audit task
+  - References or defers to seo-audit skill
+  - Explains that programmatic-seo is for strategy and template design
+  - Does not attempt full technical SEO audit
+  rubric: Should recognize this is a technical SEO audit task, not a programmatic SEO strategy
+    task. Should defer to or cross-reference the seo-audit skill, which handles crawlability,
+    indexation, and technical SEO issues. Programmatic-seo focuses on strategy, template design,
+    and content planning for scaled pages.
+  tags:
+  - programmatic-seo
+  - imported
+- id: marketing-schema-markup-01
+  department: marketing
+  prompt: Add schema markup to our SaaS product's homepage. We're a project management tool
+    called TaskFlow. We need Organization schema and any other relevant types.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Implements Organization schema in JSON-LD
+  - Includes required and recommended properties
+  - Recommends additional relevant schema types
+  - Uses @graph for multiple types
+  - Provides complete JSON-LD code
+  - Recommends validation tools
+  rubric: 'Should check for product-marketing.md first. Should implement Organization schema
+    in JSON-LD format with all required and recommended properties (name, url, logo, description,
+    sameAs for social profiles). Should recommend additional schema types for a SaaS homepage:
+    WebSite (with SearchAction if applicable), SoftwareApplication or Product. Should use
+    @graph for multiple schema types on one page. Should provide the complete JSON-LD code
+    ready to implement. Should recommend validation with Google''s Rich Results Test and Schema.org
+    validator.'
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-schema-markup-02
+  department: marketing
+  prompt: We have a FAQ page with 20 questions about our product. How do I add FAQ schema
+    to get the rich results in Google?
+  expected_properties:
+  - Implements FAQPage schema in JSON-LD
+  - Shows correct nested structure (FAQPage > Question > Answer)
+  - Provides complete code example
+  - Explains rich result benefits
+  - Notes Google's FAQ schema guidelines
+  - Recommends validation
+  rubric: 'Should implement FAQPage schema in JSON-LD format. Should show the correct structure:
+    FAQPage as mainEntity containing Question items, each with acceptedAnswer. Should provide
+    a complete code example with 2-3 sample questions. Should explain that FAQ schema can
+    enable rich results showing questions/answers directly in search. Should note Google''s
+    guidelines for FAQ schema (factual answers, not promotional). Should recommend validation
+    approach.'
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-schema-markup-03
+  department: marketing
+  prompt: add schema to our blog posts. we publish articles about marketing tips.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Implements Article or BlogPosting schema
+  - Includes author, datePublished, image, publisher
+  - Recommends BreadcrumbList alongside
+  - Provides reusable template code
+  - Addresses CMS integration for dynamic fields
+  rubric: 'Should trigger on casual phrasing. Should implement Article (or BlogPosting) schema
+    in JSON-LD. Should include required properties: headline, author (as Person with name
+    and url), datePublished, dateModified, image, publisher (as Organization). Should recommend
+    BreadcrumbList schema alongside the article schema. Should provide template code that
+    can be reused across blog posts. Should address how to populate dynamic fields (date,
+    author, headline) from the CMS.'
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-schema-markup-04
+  department: marketing
+  prompt: We're an e-commerce site selling physical products. What schema markup do we need
+    for our product pages?
+  expected_properties:
+  - Implements Product schema with full properties
+  - Includes Offer with price, availability
+  - Recommends AggregateRating and Review schema
+  - Includes BreadcrumbList
+  - Provides complete JSON-LD code
+  - Notes rich result benefits for products
+  rubric: 'Should implement Product schema with full properties: name, description, image,
+    brand, sku, offers (with price, priceCurrency, availability, url). Should recommend AggregateRating
+    if they have reviews, and Review schema for individual reviews. Should include BreadcrumbList
+    for navigation. Should address common e-commerce schema types: Product, Offer, AggregateRating,
+    Review. Should provide complete JSON-LD code. Should note that Product schema can enable
+    rich results (price, availability, ratings in search).'
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-schema-markup-05
+  department: marketing
+  prompt: We added schema markup to our site but it's not showing rich results in Google.
+    Can you help debug?
+  expected_properties:
+  - Recommends validation tools for debugging
+  - Checks for common schema errors
+  - Explains valid schema doesn't guarantee rich results
+  - Recommends Search Console structured data reports
+  - Addresses warnings vs errors distinction
+  - Provides systematic debugging approach
+  rubric: 'Should provide a systematic debugging approach: first validate with Google Rich
+    Results Test and Schema.org validator (syntax errors), then check for common issues (incorrect
+    nesting, missing required properties, JSON-LD placement errors). Should explain that valid
+    schema doesn''t guarantee rich results — Google chooses when to show them. Should recommend
+    checking Search Console for structured data reports and errors. Should address common
+    debugging scenarios: schema not detected, warnings vs errors, eligible vs displayed.'
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-schema-markup-06
+  department: marketing
+  prompt: Our organic search traffic dropped after a site redesign. Can you do a technical
+    SEO audit?
+  expected_properties:
+  - Recognizes this as a technical SEO audit request
+  - References or defers to seo-audit skill
+  - Does not attempt full SEO audit using schema markup patterns
+  rubric: Should recognize this is a technical SEO audit request, not a schema markup task.
+    Should defer to or cross-reference the seo-audit skill, which handles comprehensive technical
+    SEO audits. Schema markup is one component of SEO but doesn't address the broader technical
+    issues (redirects, crawlability, indexation) that likely caused the traffic drop.
+  tags:
+  - schema-markup
+  - imported
+- id: marketing-seo-audit-01
+  department: marketing
+  prompt: 'Can you do an SEO audit of our SaaS website? We''re getting about 2,000 organic
+    visits/month but feel like we should be getting more. URL: https://example.com'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks clarifying questions about keywords, Search Console, recent changes
+  - 'Follows audit priority order: crawlability first, then technical, on-page, content, authority'
+  - Checks robots.txt and XML sitemap
+  - Evaluates title tags, meta descriptions, heading structure
+  - Does NOT claim 'no schema found' based on web_fetch alone
+  - Notes schema markup detection limitation
+  - Output has Executive Summary
+  - Output has Prioritized Action Plan
+  - Each finding has Issue, Impact, Evidence, Fix, and Priority
+  rubric: 'Should check for product-marketing.md first. Should ask clarifying questions about
+    priority keywords, Search Console access, recent changes, and competitors. Should follow
+    the audit framework priority order: Crawlability & Indexation, Technical Foundations,
+    On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML
+    sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure,
+    and content optimization. Should NOT report on schema markup based solely on web_fetch
+    (must note the detection limitation). Output should follow the Audit Report Structure:
+    Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and
+    Prioritized Action Plan.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-02
+  department: marketing
+  prompt: Why am I not ranking for 'project management software'? We have a page targeting
+    that keyword but it's stuck on page 3.
+  expected_properties:
+  - Triggers on casual 'why am I not ranking' phrasing
+  - Checks title tag, H1, URL alignment with target keyword
+  - Evaluates content depth vs competitors
+  - Checks for keyword cannibalization
+  - Checks indexation status and canonical tags
+  - Assesses E-E-A-T signals
+  - Mentions competitive analysis against top-ranking pages
+  - Provides actionable fixes organized by priority
+  rubric: 'Should trigger on the casual ''why am I not ranking'' phrasing. Should investigate
+    both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword;
+    evaluate content depth vs competitors; check for keyword cannibalization. Technical: check
+    indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals,
+    content depth, user engagement. Should provide specific, actionable fixes organized by
+    priority. Should mention competitive analysis against current top-ranking pages.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-03
+  department: marketing
+  prompt: We just migrated from WordPress to Next.js and our organic traffic dropped 40% in
+    the last month. Help!
+  expected_properties:
+  - Treats as urgent migration diagnostic
+  - Checks redirect mapping (301s)
+  - Checks canonical tags on new pages
+  - Checks robots.txt not blocking crawlers
+  - Checks XML sitemap updated and submitted
+  - Checks for redirect chains or loops
+  - Checks for soft 404s
+  - References Search Console coverage report
+  - Provides prioritized recovery plan
+  - Mentions recovery timeline expectations
+  rubric: 'Should treat this as an urgent migration diagnostic. Should immediately check:
+    redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt
+    not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should
+    check for common migration issues: redirect chains/loops, soft 404s, lost internal links,
+    changed URL structures without redirects. Should reference Search Console coverage report
+    for indexation issues. Should provide a prioritized recovery plan with critical fixes
+    first. Should mention monitoring timeline expectations (recovery can take weeks).'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-04
+  department: marketing
+  prompt: Review the technical SEO of our e-commerce site. We have about 50,000 products and
+    use faceted navigation.
+  expected_properties:
+  - Addresses faceted navigation duplicate content
+  - Addresses crawl budget for large catalog
+  - Checks for parameterized URL issues
+  - Mentions product schema with detection limitation caveat
+  - Checks for thin category pages
+  - Checks for duplicate product descriptions
+  - Addresses out-of-stock page handling
+  - Addresses pagination and infinite scroll
+  - Findings include Impact ratings and specific fixes
+  rubric: 'Should focus on e-commerce-specific technical issues: faceted navigation creating
+    duplicate content, crawl budget management for large product catalog, parameterized URLs,
+    product schema markup (with the caveat about detection limitations). Should check for
+    thin category pages, duplicate product descriptions, out-of-stock page handling. Should
+    address crawl budget issues: pagination, infinite scroll handling, session IDs in URLs.
+    Should provide structured findings with Impact ratings and specific fixes.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-05
+  department: marketing
+  prompt: Can you check our blog posts for on-page SEO issues? We publish 4 posts per week
+    but traffic has been flat for 6 months.
+  expected_properties:
+  - Applies Content/Blog Sites framework
+  - Checks for outdated content
+  - Checks for keyword cannibalization
+  - Checks for topical clustering
+  - Checks for internal linking quality
+  - Checks for author pages and E-E-A-T signals
+  - Audits title tags, meta descriptions, heading structure
+  - Assesses whether content answers search intent
+  - Recommends content audit process
+  - Provides prioritized action plan
+  rubric: 'Should apply the Content/Blog Sites framework: check for outdated content not refreshed,
+    keyword cannibalization, missing topical clustering, poor internal linking, missing author
+    pages. Should audit on-page elements: title tags, meta descriptions, heading structure,
+    keyword targeting per post. Should assess E-E-A-T signals for blog content. Should check
+    for content depth issues and whether posts answer search intent. Should recommend a content
+    audit process and provide a prioritized action plan for the existing content library.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-06
+  department: marketing
+  prompt: I run a local plumbing business with 3 locations. My website barely shows up when
+    people search for 'plumber near me' in our areas. What's wrong?
+  expected_properties:
+  - Applies Local Business framework
+  - Checks NAP consistency
+  - Checks for local schema markup with detection caveat
+  - Addresses Google Business Profile optimization
+  - Recommends individual location pages for each location
+  - Recommends local content strategy
+  - Checks standard technical SEO factors too
+  - Provides prioritized local SEO action plan
+  rubric: 'Should apply the Local Business site-type framework. Should check for: inconsistent
+    NAP (Name, Address, Phone) across the site, missing local schema markup (with detection
+    limitation caveat), Google Business Profile optimization, missing individual location
+    pages for each of the 3 locations, and missing local content. Should also check standard
+    technical and on-page factors. Should recommend local-specific fixes: location-specific
+    pages with unique content, local schema on each, GBP optimization, citation consistency.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-07
+  department: marketing
+  prompt: Our site loads really slowly, especially on mobile. Pages take 5-6 seconds to load.
+    Is this hurting our SEO?
+  expected_properties:
+  - Focuses on Core Web Vitals
+  - Explains CWV thresholds (LCP, INP, CLS)
+  - Identifies 5-6s as well above acceptable
+  - Investigates specific speed factors
+  - Recommends specific diagnostic tools
+  - Confirms page speed impacts SEO rankings
+  - Provides prioritized speed fixes
+  - Addresses mobile-specific performance
+  rubric: 'Should focus on Site Speed and Core Web Vitals. Should explain CWV thresholds:
+    LCP < 2.5s, INP < 200ms, CLS < 0.1, and that 5-6s load time is well above acceptable.
+    Should investigate speed factors: server response time (TTFB), image optimization, JavaScript
+    execution, CSS delivery, caching headers, CDN usage, font loading. Should recommend specific
+    tools: PageSpeed Insights, WebPageTest, Chrome DevTools, Search Console CWV report. Should
+    explain that yes, page speed is a ranking factor and directly impacts SEO. Should provide
+    prioritized fixes.'
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-seo-audit-08
+  department: marketing
+  prompt: I want to add FAQ schema to my product pages. Can you help me set that up?
+  expected_properties:
+  - Recognizes this as schema markup implementation
+  - References or defers to schema skill
+  - Does not attempt a full SEO audit
+  - May briefly mention FAQ schema benefits
+  rubric: Should recognize this is a schema markup implementation task, not an SEO audit.
+    Should defer to or cross-reference the schema skill, which specifically handles structured
+    data implementation including FAQ schema. May briefly mention that FAQ schema can enable
+    rich results, but should make clear that schema is the right skill for implementation.
+  tags:
+  - seo-audit
+  - imported
+- id: marketing-sms-campaign-01
+  department: marketing
+  prompt: We're a Shopify DTC brand doing $5M/year in skincare. We have 80K email subscribers
+    but no SMS program yet. Where do we start?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Runs compliance/A2P 10DLC readiness check
+  - Recommends Klaviyo SMS or Postscript with rationale
+  - Prioritizes abandoned cart as highest-ROI flow
+  - Mentions replenishment for skincare specifically
+  - Warns about treating SMS like email
+  - References compliance.md or opt-in disclosure requirements
+  - Mentions per-send cost economics
+  rubric: 'Should check for product-marketing.md first. Should run Phase 0 compliance check:
+    are they US-based, is A2P 10DLC registration started, is the opt-in mechanism planned.
+    Should recommend Klaviyo SMS or Postscript given Shopify + DTC ecom (Klaviyo if already
+    on Klaviyo email, Postscript for SMS-first depth). Should rank flows by ROI for skincare:
+    (1) abandoned cart sequence first (highest-ROI flow), (2) post-purchase + replenishment
+    (skincare has predictable cycles), (3) welcome opt-in flow with capture incentive, (4)
+    win-back at 60-90 days. Should warn about treating SMS like email (frequency cap, relevance
+    bar, real per-send cost ~$0.0075-$0.04). Should reference compliance.md for opt-in disclosure
+    language and quiet hours.'
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-sms-campaign-02
+  department: marketing
+  prompt: Write me an abandoned cart SMS sequence. We sell custom apparel, average order $80.
+  expected_properties:
+  - Outputs 3-message sequence with timing
+  - Send 1 at 30 min, Send 2 at 4 hours, Send 3 at 24 hours
+  - No discount on Send 1
+  - Each message has sender ID + single CTA + short link
+  - Character counts shown, target ~160 GSM-7
+  - Compliance footer on first send (STOP to opt out)
+  - Warns about discount on first send
+  - Mentions exclusion rules
+  - Mentions UTM tagging or attribution
+  rubric: 'Should output a 3-message sequence following references/sequence-templates.md pattern.
+    Should specify timing: Send 1 at 30 min after abandon (no discount, gentle reminder),
+    Send 2 at 4 hours (soft urgency, no discount), Send 3 at 24 hours (discount allowed).
+    Should include actual SMS copy with character counts (target 160 GSM-7 for 1 segment).
+    Each message must start with sender ID ''From [Brand]:'', have a single CTA + short link,
+    and the first message should include ''Reply STOP to opt out'' compliance footer. Should
+    warn against discount on first send (trains customers to abandon). Should mention exclusion
+    rules: stop sequence on purchase, opt-out, or 48 hours elapsed. Should recommend UTM tagging
+    for attribution and cross-reference analytics skill for measurement.'
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-sms-campaign-03
+  department: marketing
+  prompt: Can I just send SMS without any opt-in if customers gave me their phone number at
+    checkout?
+  expected_properties:
+  - Refuses the no-opt-in approach
+  - Distinguishes marketing SMS from transactional SMS
+  - Lists express written consent requirements
+  - Mentions TCPA penalty exposure ($500-$1,500 per message)
+  - Mentions class action risk
+  - Recommends compliant opt-in flow
+  - References compliance.md
+  - Clarifies checkout phone capture is not marketing consent
+  rubric: 'Should refuse and explain TCPA requires express written consent for marketing SMS.
+    Should distinguish marketing SMS (requires express written consent) from transactional/account
+    SMS (order updates, auth — implied consent during transaction OK if directly related).
+    Should explain the express written consent requirements: clear disclosure adjacent to
+    the phone field, frequency expectation, msg & data rates notice, STOP/HELP instructions,
+    terms link, electronically captured with timestamp. Should mention penalty exposure: $500-$1,500
+    per message, class actions reach 7-8 figures. Should recommend implementing a compliant
+    opt-in flow: checkbox + disclosure text, double opt-in optional but cleaner. Should reference
+    compliance.md for the full disclosure template. Should warn that ''customers gave their
+    number at checkout'' is NOT sufficient for marketing SMS — it''s only sufficient for the
+    specific transaction''s communications.'
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-sms-campaign-04
+  department: marketing
+  prompt: Our SMS list is 50K subscribers. We send 3 promotional messages per week. Opt-out
+    rate has crept up to 4% per send. What's wrong?
+  expected_properties:
+  - Diagnoses as over-sending / audience fatigue
+  - Cites healthy benchmark (<2% opt-out per send, <0.5% promotional)
+  - Recommends reducing send frequency
+  - Recommends segmentation by engagement
+  - Suggests reactivation flow for cold subscribers
+  - Calculates list erosion impact
+  - Mentions 'every send must justify itself' principle
+  rubric: 'Should diagnose this as audience fatigue from over-sending. Should reference healthy
+    benchmarks: opt-out rate should be <2% per send and <0.5% for promotional sends — 4% is
+    significantly elevated. Should review send frequency: 3 promotional sends/week is on the
+    high side; recommend reducing to 1-2/week, especially for newer subscribers. Should audit
+    relevance: are sends segmented or going to entire list? Generic blasts to a 50K list will
+    burn out the inactive 30K. Should recommend segmenting by engagement (recently engaged
+    vs cold), purchase recency, and opt-in source. Should suggest reactivating cold subscribers
+    with a re-engagement flow before sending more promos. Should warn that 4% opt-out per
+    send means the list is being destroyed at the rate of ~2K/week. Should cross-reference
+    analytics for proper measurement and the principle ''every send must justify itself.'''
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-sms-campaign-05
+  department: marketing
+  prompt: We just submitted our A2P 10DLC registration and our sends are working. Can we start
+    scaling to 100K+ messages per day?
+  expected_properties:
+  - Asks about phone number type (10DLC vs toll-free vs short code)
+  - Explains throughput limits with specific msg/sec numbers
+  - Calculates time-to-send for 100K volume
+  - Mentions quiet hour considerations
+  - Recommends short code for high sustained volume
+  - Warns about carrier filtering / throttling
+  - Mentions A2P sample text alignment requirement
+  - References platforms.md or trust score monitoring
+  rubric: 'Should ask about phone number type currently in use: 10DLC, toll-free, or short
+    code. Should explain throughput limits: 10DLC standard brand ~4-10 msg/sec, verified brand
+    ~75-100+ msg/sec, toll-free ~3 msg/sec, short code 100+ msg/sec. Should calculate: 100K
+    msgs at 10 msg/sec = ~2.8 hours of continuous send time, may run into quiet hour cutoff.
+    Should recommend short code lease for 100K+/day sustained volume. Should warn about carrier
+    filtering on burst sends — use platform throttling. Should mention that sample message
+    text from A2P registration must match actual sends or carriers will flag. Should recommend
+    monitoring trust score and deliverability dashboards. Should reference platforms.md for
+    short code provisioning details.'
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-sms-campaign-06
+  department: marketing
+  prompt: Should we put emojis in our SMS messages? Other brands seem to use them a lot.
+  expected_properties:
+  - Explains UCS-2 encoding cost
+  - Specifies 160 GSM-7 vs 70 UCS-2 segment sizes
+  - Recommends max 1 emoji per message
+  - Warns about doubled per-send cost
+  - Mentions accented characters / curly quotes also trigger UCS-2
+  - Recommends previewing segment count
+  - Calculates cost impact at scale
+  rubric: 'Should explain the cost trade-off: emojis force UCS-2 encoding, which cuts segment
+    size from 160 GSM-7 chars to 70 chars. A 100-char message with one emoji becomes 2 segments
+    billed instead of 1 — effectively doubling the per-send cost. Should advise: 1 emoji per
+    message max, situationally relevant, only when the emoji genuinely earns its segment cost
+    (high-energy promotional, brand-personality fit, etc.). Should warn against emoji clutter
+    — it signals ''mass send'' rather than personal. Should note that some accented characters
+    (curly quotes, em dashes) also force UCS-2 — copy-pasting from Word/Google Docs is a common
+    silent cause of doubled costs. Should recommend testing in the platform''s preview to
+    verify segment count before scheduling. Should remind that segment count matters at scale:
+    100K sends at 2 segments instead of 1 = $750-$4,000 in extra cost per campaign.'
+  tags:
+  - sms-campaign
+  - imported
+- id: marketing-social-strategy-01
+  department: marketing
+  prompt: Help me create a LinkedIn content strategy. I'm a SaaS founder building in public
+    and want to grow my personal brand to drive awareness for my product. I currently have
+    500 followers and post maybe once a week.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Establishes 3-5 content pillars
+  - Applies LinkedIn platform guidance
+  - Provides hook formulas
+  - Creates weekly content calendar
+  - Includes engagement strategy
+  - Addresses batching strategy for consistency
+  - Recommends increasing from 1x to 3-5x per week
+  rubric: 'Should check for product-marketing.md first. Should establish content pillars (3-5)
+    appropriate for a SaaS founder building in public: industry insights, behind-the-scenes,
+    educational content, personal stories, promotional (minimal). Should apply the platform
+    quick reference for LinkedIn (3-5x/week recommended, carousels and stories perform well).
+    Should provide hook formulas for LinkedIn posts. Should create a weekly content calendar.
+    Should include engagement strategy (daily 30-min routine). Should address going from 1x/week
+    to 3-5x/week with a batching strategy.'
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-02
+  department: marketing
+  prompt: Write me a Twitter/X thread about the lessons I learned bootstrapping my SaaS to
+    $10k MRR. Include hooks and a CTA at the end.
+  expected_properties:
+  - Applies hook formulas from the skill
+  - Uses a story hook for the first tweet
+  - Structures thread with standalone but flowing tweets
+  - Uses specific numbers and stories
+  - Ends with clear CTA
+  - Provides 8-12 tweet thread content
+  - Includes engagement prompts
+  rubric: 'Should apply the hook formulas for a story hook (e.g., ''6 months ago, I had $0
+    MRR. Today, I hit $10k.''). Should structure the thread following platform best practices:
+    strong hook in tweet 1, each tweet should stand alone but flow together, use specific
+    numbers and stories, end with a CTA. Should reference the content pillar this fits into
+    (behind-the-scenes / founder journey). Should provide the actual thread content with 8-12
+    tweets. Should include engagement prompts.'
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-03
+  department: marketing
+  prompt: i have a blog post that did really well. how do i turn it into social media content
+    for multiple platforms?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies content repurposing system
+  - Uses Blog Post → Social Content mapping
+  - Provides format for LinkedIn, Twitter/X, and Instagram
+  - Follows the repurposing workflow
+  - Extracts 3-5 key insights to repurpose
+  - Provides platform-specific format recommendations
+  rubric: 'Should trigger on casual phrasing. Should apply the content repurposing system.
+    Should use the Blog Post → Social Content mapping: LinkedIn (key insight post + carousel
+    of main points), Twitter/X (thread of key takeaways), Instagram (carousel with visuals
+    + Reel summarizing the post). Should follow the repurposing workflow: create pillar content
+    → extract key insights (3-5) → adapt to each platform → schedule across the week. Should
+    provide specific format recommendations per platform.'
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-04
+  department: marketing
+  prompt: My LinkedIn posts get like 200 impressions and almost no engagement. What am I doing
+    wrong?
+  expected_properties:
+  - Applies analytics and optimization guidance
+  - Diagnoses potential engagement issues
+  - Addresses hook quality
+  - Addresses posting timing
+  - Recommends daily engagement routine
+  - Suggests trying different content formats
+  - Provides specific before/after hook examples
+  rubric: 'Should apply the analytics and optimization section, specifically the ''if engagement
+    is low'' guidance. Should diagnose potential issues: weak hooks (first line not compelling),
+    posting at wrong times, not engaging with others'' content, poor formatting (no line breaks,
+    walls of text), content not resonating with audience. Should recommend specific fixes:
+    test new hook formulas, post at different times, increase engagement with others (the
+    daily engagement routine), try different formats (carousels, stories). Should provide
+    before/after hook examples.'
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-05
+  department: marketing
+  prompt: Help me reverse-engineer what's working for top creators in the DevTools space on
+    Twitter. I want to understand their content patterns.
+  expected_properties:
+  - Applies reverse engineering viral content framework
+  - Walks through the full process (find, collect, analyze, codify, apply)
+  - Recommends identifying 10-20 accounts
+  - Describes what patterns to analyze
+  - Emphasizes layering authentic voice
+  - Provides data collection guidance
+  rubric: 'Should apply the reverse engineering viral content framework. Should walk through
+    the process: identify 10-20 top accounts in DevTools, collect high-performing posts, analyze
+    patterns (hooks, formats, CTAs, topics, posting times), codify a playbook of repeatable
+    patterns, then layer the user''s authentic voice. Should provide specific guidance on
+    what to look for in the analysis. Should recommend tools or methods for collecting the
+    data.'
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-06
+  department: marketing
+  prompt: Write me a 5-email welcome sequence for new email subscribers who came from my LinkedIn
+    audience.
+  expected_properties:
+  - Recognizes this as email sequence work
+  - References or defers to emails skill
+  - Does not attempt to write email sequence using social content patterns
+  - May note social-to-email bridge context
+  rubric: Should recognize this is an email sequence task, not social content. Should defer
+    to or cross-reference the emails skill, which handles welcome sequences, drip campaigns,
+    and lifecycle emails. May note the social-to-email bridge context but should make clear
+    that emails is the right skill for writing email sequences.
+  tags:
+  - social-strategy
+  - imported
+- id: marketing-social-strategy-07
+  department: marketing
+  prompt: I want to turn our new pricing guide into a LinkedIn carousel. It has 9 negotiation
+    tactics for SaaS buyers. Help me structure the slides.
+  expected_properties:
+  - Loads or applies the carousel-frameworks reference
+  - Selects an appropriate framework (Hack List or Value-Stack) with a stated reason before
+    drafting slides
+  - Slide 1 is written as a standalone scroll-stopper with the count or contrarian claim
+  - One tactic/idea per slide, each named
+  - Final slide has a synthesis and exactly one CTA
+  - Applies LinkedIn document-post guidance (PDF, post text as its own hook)
+  - Does not invent stats or pad the tactic count
+  rubric: 'Should load references/carousel-frameworks.md and pick a framework BEFORE writing
+    slides — a list of 9 named tactics maps to Hack List (or Value-Stack; should justify the
+    choice), not Rant Callout or Demo Walkthrough. Should produce a slide-by-slide structure:
+    contrarian or exact-count cover (slide 1 written as a standalone scroll-stopper), one
+    named tactic per slide, and a synthesis + single-CTA close. Should apply LinkedIn document-post
+    notes (PDF upload, denser text tolerated, post text written as its own hook rather than
+    ''see attached''). Should keep any count promised on the cover exactly delivered and flag
+    that stats/claims must be real. Should mention judging performance on saves/completion
+    rather than likes.'
+  tags:
+  - social-strategy
+  - imported
+# --- END imported ---