luckiest-co 1.0.47 → 1.0.48

package/skills/competitor-profiling/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-competitor-profiling
 
+## 1.2.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Description points account research at luckiest-prospecting.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/competitor-profiling/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: competitor-profiling
-description: Researches, profiles, and analyzes competitors from their URLs, producing structured competitor-profile markdown built from live site scraping plus SEO and market data. Use when the user wants to research or profile competitors, or mentions "competitor profile," "competitor research," "competitor analysis," "profile this competitor," "analyze competitor," "competitive intelligence," "competitor deep dive," "who are my competitors," "competitor landscape," "competitor dossier," "competitive audit," or "research these competitors." Input is a list of competitor URLs; output is structured competitor-profile markdown files. For creating comparison/alternative pages from profiles, see luckiest-competitors. For sales-specific battle cards, see luckiest-sales-enablement.
+description: Researches, profiles, and analyzes competitors from their URLs, producing structured competitor-profile markdown built from live site scraping plus SEO and market data. Use when the user wants to research or profile competitors, or mentions "competitor profile," "competitor research," "competitor analysis," "profile this competitor," "analyze competitor," "competitive intelligence," "competitor deep dive," "who are my competitors," "competitor landscape," "competitor dossier," "competitive audit," or "research these competitors." Input is a list of competitor URLs; output is structured competitor-profile markdown files. For creating comparison/alternative pages from profiles, see luckiest-competitors. For sales-specific battle cards, see luckiest-sales-enablement. For researching accounts you are selling to, see luckiest-prospecting.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.2.0"
+  version: "1.2.1"
   listing_id: luckiest-competitor-profiling
   author: luckiest
 ---
@@ -14,9 +14,9 @@ The assistant acts as an expert competitive intelligence analyst. The goal is to
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "ba5cb7e6-afc1-4035-a3d4-ce5b4229535f", installedSemver: "1.2.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "ba5cb7e6-afc1-4035-a3d4-ce5b4229535f", installedSemver: "1.2.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-competitor-profiling", skill_version: "1.2.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-competitor-profiling", skill_version: "1.2.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
 
 ## Initial Assessment
 

package/skills/content-strategy/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-content-strategy
 
+## 1.1.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Information-gain gate: write one sentence on what a searchable piece adds that the current top results lack, or don't write it.
+
 ## 1.1.0 — 2026-07-06
 Skill updater pass: analytics integration.
 

package/skills/content-strategy/SKILL.md

@@ -3,7 +3,7 @@ name: content-strategy
 description: Plans what content to create — content pillars, topic clusters, buyer-stage keyword mapping, and prioritization — so a brand builds traffic, authority, and leads through searchable and shareable content. Use when the user wants to plan a content strategy, decide what to create, audit and refresh an existing library, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," "content audit," "our content feels random," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see luckiest-copywriting. For SEO-specific audits, see luckiest-seo-audit.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.0"
+  version: "1.1.1"
   listing_id: luckiest-content-strategy
   author: luckiest
 ---
@@ -14,9 +14,9 @@ The agent acts as a content strategist. The goal is to plan content that drives
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "72a19125-282a-4954-b958-4d71934ce77f", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "72a19125-282a-4954-b958-4d71934ce77f", installedSemver: "1.1.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-content-strategy", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-content-strategy", skill_version: "1.1.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
 
 ## Before Planning
 
@@ -73,6 +73,8 @@ Every piece of content must be searchable, shareable, or both. Prioritize in tha
 
 ### When Writing Searchable Content
 
+**The information-gain gate:** before committing to a searchable piece, read the current top results for its query and write one sentence on what yours will add that none of them have: original data, a real product example, a working tool or template, a clearer answer, a stronger opinion. If you can't write that sentence, don't write the piece. It will be the eleventh copy of the same article, and neither Google nor AI assistants have a reason to prefer it.
+
 - Target a specific keyword or question
 - Match search intent exactly — answer what the searcher wants
 - Use clear titles that match search queries

package/skills/copy-editing/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-copy-editing
 
+## 1.2.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Content refresh starts with a SERP gap grid (expected, common, distinctive, uncovered) and keeps the URL, anchors and voice.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/copy-editing/SKILL.md

@@ -3,7 +3,7 @@ name: copy-editing
 description: "When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit,' 'this sounds like AI,' 'AI slop,' 'de-slop this,' or 'make it sound human.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see luckiest-copywriting."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.2.0"
+  version: "1.2.1"
   listing_id: luckiest-copy-editing
   author: luckiest
 ---
@@ -14,9 +14,9 @@ This skill acts as an expert copy editor specializing in marketing and conversio
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "8f895dc3-9d85-4b40-9c80-2b1d396bc579", installedSemver: "1.2.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "8f895dc3-9d85-4b40-9c80-2b1d396bc579", installedSemver: "1.2.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-copy-editing", skill_version: "1.2.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-copy-editing", skill_version: "1.2.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
 
 ## Core Philosophy
 
@@ -475,7 +475,7 @@ This iterative process ensures each edit doesn't create new problems while respe
 ## References
 
 - [Plain English Alternatives](references/plain-english-alternatives.md): Replace complex words with simpler alternatives
-- [Content Refresh](references/content-refresh.md): Full checklist, refresh vs. rewrite matrix, and cadence guide
+- [Content Refresh](references/content-refresh.md): SERP gap analysis, full checklist, refresh vs. rewrite matrix, and cadence guide
 - [Copy Editing Checklist](references/checklist.md): Full QA checklist across all seven sweeps plus the AI-tell check
 
 ---
@@ -484,7 +484,7 @@ This iterative process ensures each edit doesn't create new problems while respe
 
 Copy editing isn't just for new content. Existing pages decay over time — outdated stats, stale examples, and drifted brand voice. Use the content refresh framework when traffic is declining, data is stale, or the product has changed.
 
-**For the full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide**: See [references/content-refresh.md](references/content-refresh.md)
+**For the SERP gap analysis, full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide**: See [references/content-refresh.md](references/content-refresh.md)
 
 ---
 

package/skills/copy-editing/references/content-refresh.md

@@ -19,6 +19,39 @@ Copy editing isn't just for new content. Existing pages and posts decay over tim
 5. **Proof pass** — Can you add newer testimonials, case studies, or data points that didn't exist when this was first published?
 6. **Structure pass** — Add comparison tables, FAQ sections, or other scannable formats that make the content easier to consume.
 
+## Before You Edit: Find the Gap
+
+A refresh aimed at a ranking page should start from the results page. The first question to answer is why the pages above yours are winning.
+
+1. **Read the results page for the post's main query.** Note the dominant format (list, guide, tool, comparison), the featured snippet and how it's formatted, People Also Ask questions, and related searches.
+2. **Pick five competitors**: the top three results, plus any direct competitor or recently updated page ranking near you.
+3. **Map coverage.** List the subtopics each page covers in a simple grid, with your post as the first column:
+
+| Subtopic / element | Your post | Comp 1 | Comp 2 | Comp 3 | Comp 4 | Comp 5 |
+|--------------------|:---------:|:------:|:------:|:------:|:------:|:------:|
+| [Subtopic A] | ✗ | ✓ | ✓ | ✓ | ✓ | — |
+| Comparison table | ✗ | ✓ | — | ✓ | — | — |
+| Current-year data | ✗ | ✓ | ✓ | — | ✓ | ✓ |
+
+4. **Rank what's missing** by how many competitors cover it:
+   - **Expected** (4–5 of 5): searchers assume it's there. Add it.
+   - **Common** (2–3): add it if it serves your reader.
+   - **Distinctive** (1): add it only if it's genuinely useful, not to copy one page.
+   - **Uncovered** (0): the angle nobody has. Your best chance to be the result worth citing.
+5. **Match coverage.** Ignore competitors' word counts. Close the gaps that matter, and stop when the reader's question is answered.
+
+Present the gap grid and a proposed outline before rewriting. Mark each section **Keep**, **Revise**, or **New**, propose 2–3 title options (see the `luckiest-seo-audit` skill), and wait for approval. Don't promise a ranking or traffic outcome.
+
+## Keep What Already Works
+
+A page that ranks has signals worth protecting:
+- **Keep the URL.** If it must change, 301 the old one.
+- **Keep heading anchors** other pages link to, and the sections that rank for their own queries (check Search Console's query list for the page).
+- **Keep the voice.** A refresh shouldn't read like a different author wrote it.
+- **Show the update**: a visible "Last updated" date, with the year next to every statistic.
+
+When handing the refresh to whoever publishes it, include the new meta description, schema types to add, internal links to add to and from the post, images or screenshots needed, and the URL plan.
+
 ## Refresh vs. Rewrite
 
 | Signal | Action |

package/skills/cro/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-cro
 
+## 1.1.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Reference routing table (form, experiments); enrichment after a lead form points at luckiest-revops; enrichment tool list updated.
+
 ## 1.1.0 — 2026-07-06
 Skill updater pass: analytics integration.
 

package/skills/cro/SKILL.md

@@ -3,7 +3,7 @@ name: cro
 description: "When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see luckiest-signup. For post-signup activation, see luckiest-onboarding. For popups/modals, see luckiest-popups."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.0"
+  version: "1.1.1"
   listing_id: luckiest-cro
   author: luckiest
 ---
@@ -14,9 +14,18 @@ This skill analyzes marketing pages and produces actionable recommendations to i
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "5273389c-5f29-4e4e-9068-03e7c3fe5f4c", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "5273389c-5f29-4e4e-9068-03e7c3fe5f4c", installedSemver: "1.1.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-cro", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-cro", skill_version: "1.1.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Reference Routing
+
+Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations.
+
+| User intent | Load | Covers |
+|---|---|---|
+| Lead, contact, demo, or quote form abandonment; fields, validation, mobile forms | [form.md](references/form.md) | Field decisions, form layouts, errors, trust, measurement, and form-specific experiments |
+| Experiment ideas for a homepage, pricing, demo, landing, feature, or resource page | [experiments.md](references/experiments.md) | Hypotheses organized by page type and cross-page tests; use **luckiest-ab-testing** for test design and measurement |
 
 ## Initial Assessment
 
@@ -206,6 +215,8 @@ When recommending experiments, consider tests for:
 
 ## Form Optimization
 
+When enrichment controls the next step after a lead form, use the **luckiest-revops** skill for inbound routing: preserve valid submissions, bound the lookup wait, and provide a useful fallback when qualification is unknown.
+
 For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references/form.md](references/form.md).
 
 ---

package/skills/cro/references/form.md

@@ -78,7 +78,7 @@ For each field, ask:
 
 ### Company/Organization
 - Auto-suggest for faster entry
-- Enrichment after submission (Clearbit, etc.)
+- Enrichment after submission (HubSpot Breeze, Clay, Apollo, etc.)
 - Consider inferring from email domain
 
 ### Job Title/Role

package/skills/directory-submissions/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-directory-submissions
 
+## 1.2.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Backlink check inspects the actual anchor's `href` and `rel` in HTML (not `curl -I` headers); records unqualified, missing or unverified. One updated eval.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/directory-submissions/SKILL.md

@@ -3,7 +3,7 @@ name: directory-submissions
 description: When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "publish my MCP server," "awesome list," "llms.txt directory," "Claude plugin directory," "agent directory," "dofollow backlinks," "launch directories," "directory tracker," "my listing got rejected," or "audit my backlink profile." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see luckiest-launch. For programmatic SEO pages that should live behind these backlinks, see luckiest-programmatic-seo. For AI citation optimization, see luckiest-ai-seo.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.2.0"
+  version: "1.2.1"
   listing_id: luckiest-directory-submissions
   author: luckiest
 ---
@@ -14,9 +14,9 @@ This skill makes the agent an expert in directory-driven distribution for softwa
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "f3e67fc6-3ebe-4f90-b7dc-785a29f83d12", installedSemver: "1.2.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "f3e67fc6-3ebe-4f90-b7dc-785a29f83d12", installedSemver: "1.2.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-directory-submissions", skill_version: "1.2.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-directory-submissions", skill_version: "1.2.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
 
 ## Before Starting
 
@@ -146,7 +146,16 @@ Per submission:
 3. Upload assets.
 4. Submit.
 5. Log: date, URL, status, moderator notes.
-6. Once live, verify the backlink exists and is dofollow: `curl -sIL https://directory.com/your-listing | grep -i rel=`. If absent, the link is dofollow.
+6. Once live, inspect the actual link to your product using the procedure below; an empty HTTP-header search does not verify a backlink.
+
+### Verify the Actual Backlink
+
+Fetch the listing's HTML with `curl -fsSL https://directory.com/your-listing`, or inspect its rendered DOM in a browser. `curl -I` requests headers; it cannot inspect an anchor's `href` or `rel` attributes.
+
+1. Locate the specific `<a>` that links to your product. Check the destination, including redirects; don't classify an unrelated navigation link or a canonical tag.
+2. Record its actual `rel` tokens, such as `nofollow`, `sponsored`, or `ugc`. For an inspected anchor without those qualifiers, record **unqualified link observed**. There is no `dofollow` attribute to look for, and this is not a guarantee of indexing, ranking credit, or referral traffic. See [Google's link-qualification guidance](https://developers.google.com/search/docs/crawling-indexing/qualify-outbound-links).
+3. If the destination anchor is absent from downloaded HTML, check whether the page renders it with JavaScript. If the page is blocked, requires login, or cannot be inspected, record **unverified**; if inspection confirms no destination link, record **missing**. Neither outcome proves an unqualified backlink.
+4. Save the listing URL, checked destination, observed attributes, timestamp, and any access limitation in the tracker notes. Recheck after a directory changes its template or submission tier.
 
 ### Step 4b: Dedup against the existing backlink profile first
 

package/skills/directory-submissions/evals/evals.json

@@ -78,7 +78,7 @@
     {
       "id": 6,
       "prompt": "We submitted to 50 directories last week. Now what?",
-      "expected_output": "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.",
+      "expected_output": "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 checking the actual destination anchor in fetched HTML or the rendered DOM, recording its href and rel tokens; HEAD headers alone cannot verify a backlink. 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.",
       "assertions": [
         "Warns against over-indexing on launch spike",
         "Recommends verifying dofollow status of backlinks",
@@ -89,6 +89,20 @@
         "Says investigate before submitting more"
       ],
       "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "Our directory submission is live. curl -sIL on the listing returns 200 but grep rel= is empty. Can I mark the backlink dofollow? Another listing has only a canonical tag pointing at itself, and a third requires login.",
+      "expected_output": "Should explain that HEAD returns headers and cannot establish destination anchor attributes or even link existence. Inspect HTML or the rendered DOM for the actual product anchor and destination; distinguish canonical tags and unrelated links. Record nofollow/sponsored/ugc tokens when observed. Mark an inspected anchor without those qualifiers unqualified, without promising ranking credit. Missing anchor is missing only after inspection; blocked/login/JS content that cannot be inspected is unverified. Log evidence and timestamp.",
+      "assertions": [
+        "Does not classify an empty header grep as dofollow",
+        "Inspects the actual destination anchor href and rel",
+        "Distinguishes missing and unverified links from observed unqualified links",
+        "Does not confuse canonical tags with backlinks",
+        "Does not guarantee search-engine credit from an unqualified link",
+        "Records evidence and access limitations"
+      ],
+      "files": []
     }
   ]
 }

package/skills/directory-submissions/references/directory-list.md

@@ -468,10 +468,8 @@ Industry-specific directories. Only submit if your product genuinely fits the ve
 
 ## Verification
 
-After any submission goes live, verify the backlink exists and is dofollow. You can:
+After a submission goes live, follow [Verify the Actual Backlink](../SKILL.md#verify-the-actual-backlink). Inspect the product's destination anchor in fetched HTML or the rendered DOM and record its `href` and `rel` tokens, including `nofollow`, `sponsored`, and `ugc`. HTTP headers or a canonical tag do not establish a backlink. Record missing or inaccessible links separately from observed unqualified links; none guarantees ranking credit.
 
-1. **Manual:** Open the listing, right-click your product link, "Inspect" → check for `rel="nofollow"` or `rel="ugc"`. If absent, the link is dofollow.
-2. **curl:** `curl -sIL https://directory.com/your-listing | grep -i link`
-3. **SEO tools:** Ahrefs Site Explorer → Backlinks → filter by this directory's domain.
+Catalog descriptions and tracker defaults are planning assumptions, not evidence for your particular listing. An SEO tool's backlink report can help find a listing, but verify the current anchor and timestamp the observation before reporting its link type.
 
 **Re-verify quarterly.** Directories sometimes change all outbound links to nofollow without warning — if DR stops moving, check whether your biggest inbound links have silently flipped.

package/skills/emails/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-emails
 
+## 1.2.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Reference routing table (sequence templates, email types, copy guidelines); description points outbound sequences at luckiest-cold-email.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/emails/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: emails
-description: Designs and optimizes email sequences, drip campaigns, automated flows, and lifecycle email programs. Use when the user wants to build or improve a multi-email automated flow, or mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." For cold outreach emails, see luckiest-cold-email. For in-app onboarding, see luckiest-onboarding.
+description: Designs and optimizes email sequences, drip campaigns, automated flows, and lifecycle email programs. Use when the user wants to build or improve a multi-email automated flow, or mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." For cold outreach and outbound sequences, see luckiest-cold-email. For in-app onboarding, see luckiest-onboarding.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.2.0"
+  version: "1.2.1"
   listing_id: luckiest-emails
   author: luckiest
 ---
@@ -16,9 +16,19 @@ practice to any multi-email automated flow.
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "aac8d2c2-25c1-435f-a2da-34f6f0e5b5f1", installedSemver: "1.2.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "aac8d2c2-25c1-435f-a2da-34f6f0e5b5f1", installedSemver: "1.2.1" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-emails", skill_version: "1.2.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-emails", skill_version: "1.2.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Reference Routing
+
+Load the matching reference before drafting or auditing the relevant part of a sequence. Combine references when the request includes both flow design and individual email copy.
+
+| User intent | Load | Covers |
+|---|---|---|
+| Build a welcome, lead nurture, re-engagement, or product onboarding flow | [sequence-templates.md](references/sequence-templates.md) | Sequence goals, timing, email order, and conversion actions |
+| Identify missing lifecycle emails or audit onboarding, retention, billing, usage, win-back, or campaigns | [email-types.md](references/email-types.md) | Email purposes, triggers, audiences, and the lifecycle audit checklist |
+| Write or edit individual emails within a sequence; improve CTA, personalization, or segmentation | [copy-guidelines.md](references/copy-guidelines.md) | Structure, tone, length, merge fields, dynamic content, and copy testing |
 
 ## Initial Assessment
 

package/skills/launch/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog — luckiest-launch
 
+## 1.2.0 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- New references: shipped-changes (turn merged work into changelog and announcement copy) and site-launch-qa (pre-launch QA for new sites, redesigns, migrations), linked from the checklist.
+- New triggers: site launch, go live, pre-launch QA, changelog, release notes.
+- Fixed the update check reporting 1.1.0.
+
 ## 1.1.1 — 2026-10-03
 - Points at `luckiest-video-studio-composition` (when installed) for focal point, grid, white space, and safe areas.
 

package/skills/launch/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: launch
-description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see luckiest-marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see luckiest-offers."
+description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'site launch,' 'go live,' 'pre-launch QA,' 'launch checklist,' 'GTM plan,' 'we're about to ship,' 'changelog,' 'release notes,' or 'what did we ship this week.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see luckiest-marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see luckiest-offers."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.1"
+  version: "1.2.0"
   listing_id: luckiest-launch
   author: luckiest
 ---
@@ -14,9 +14,9 @@ This skill helps the user plan SaaS product launches and feature announcements t
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "b65cba33-d644-4eda-b14b-aea9b19f203e", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "b65cba33-d644-4eda-b14b-aea9b19f203e", installedSemver: "1.2.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-launch", skill_version: "1.1.1", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-launch", skill_version: "1.2.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
 
 ## Before Starting
 
@@ -320,6 +320,9 @@ Continue using email, social, and in-app messaging to highlight improvements.
 **Signal active development:**
 Even small changelog updates remind customers the product is evolving. This builds retention and word-of-mouth—customers feel confident the company will be around.
 
+**Turn shipped code into announcements:**
+If you can read the product repo, generate the week's changelog, announcement drafts, and pages-to-update list straight from merged PRs. See [references/shipped-changes.md](references/shipped-changes.md).
+
 ---
 
 ## Launch Checklist
@@ -335,6 +338,7 @@ Even small changelog updates remind customers the product is evolving. This buil
 - [ ] Launch assets created (screenshots, demo video, GIFs). For framing, if `luckiest-video-studio-composition` is installed, read it to place the focal point, pick the grid, and keep white space and platform safe areas
 - [ ] Onboarding flow ready
 - [ ] Analytics/tracking in place
+- [ ] Site QA done if the launch includes a new site, redesign, or migration (see [references/site-launch-qa.md](references/site-launch-qa.md))
 - [ ] Pre-mortem run: top failure modes identified and mitigated
 
 ### Launch Day

package/skills/launch/evals/evals.json

@@ -86,6 +86,35 @@
         "May provide some launch-related tactical ideas"
       ],
       "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "Our redesigned marketing site goes live Thursday on a new platform. What should we check before and after we flip the switch?",
+      "expected_output": "Should load the site launch QA reference and give a before/at/after checklist: forms reach their destinations and conversion tracking fires on confirmed submission; unique titles, canonicals to production, staging noindex not shipped to production, robots and sitemap; redirect map loaded for changed URLs; mobile, Safari and in-app browser checks; Core Web Vitals; a known, practiced rollback for their platform; at switch, HTTPS on all hostnames, top pages return 200, real form test, sitemap submitted; after, daily Search Console 404 checks and page-level traffic comparison.",
+      "assertions": [
+        "Checks forms and conversion tracking on confirmed submission",
+        "Warns about shipping the staging noindex",
+        "Includes the redirect map for changed URLs",
+        "Includes a practiced rollback plan",
+        "Includes post-launch Search Console monitoring"
+      ],
+      "files": []
+    },
+    {
+      "id": 9,
+      "prompt": "You have access to our product repo. Can you look at what we merged this week and turn it into a changelog entry and some announcement drafts?",
+      "expected_output": "Should load the shipped-changes reference. Should read merged PRs (and the commit log for anything without a PR) for the week, exclude anything behind a feature flag or not deployed, and drop invisible changes like refactors, dependency bumps and CI. Should translate each visible change into a 'You can now...' line, tier it as major, medium or minor using the skill's announcement matrix, and produce a changelog entry using Keep a Changelog headings plus drafts matched to tier. Every claim should come from the change itself with no invented metrics or customer results. Should also list marketing pages the changes made wrong and new content opportunities, and stage all drafts for human review rather than publishing.",
+      "assertions": [
+        "Reads merged PRs and commits for the window",
+        "Excludes flagged, undeployed and invisible changes",
+        "Translates changes into customer-facing 'You can now' statements",
+        "Tiers changes and matches output to the tier",
+        "Uses Keep a Changelog headings",
+        "Does not invent metrics or customer outcomes",
+        "Flags existing pages the changes made inaccurate",
+        "Stages drafts for review instead of publishing"
+      ],
+      "files": []
     }
   ]
 }

package/skills/launch/references/shipped-changes.md

@@ -0,0 +1,84 @@
+# From Shipped Code to Marketing
+
+Most product updates never get marketed because nobody translates them. The engineers wrote the PR description for each other, and by the time marketing hears about it, the moment has passed. An agent with access to the repo can close that gap every week: read what shipped, decide what's worth telling, and draft it in customer language.
+
+## Inputs
+
+For the chosen window (usually the last week, or since the last release tag):
+- **Merged PRs** with titles, descriptions, and linked issues. These explain *why* better than commits do.
+- **Commit log** for anything merged without a PR: `git log --since="1 week ago" --no-merges --pretty=format:"%h %s (%an, %ar)"`
+- **Changed files**, read wherever a title doesn't make the user-facing effect clear.
+- **Release notes or tags**, if the team already writes them.
+- **Feature flags**: what's actually live for customers versus merged behind a flag.
+
+Only market what customers can use today. Anything behind a flag, in internal beta, or not yet deployed waits.
+
+## Translate before you write
+
+Engineering changes are described by what changed in the code. Customers care about what changed for them. For each change, write one line: **"You can now ___"** or **"___ no longer ___."** If you can't fill that in, the change is invisible to customers. Refactors, dependency bumps, CI, and test changes go in no marketing output at all.
+
+Then group the visible changes with the tiers in the Ongoing Launch Strategy section of `SKILL.md`:
+
+| Tier | Typical changes | Output |
+|------|-----------------|--------|
+| **Major** | New capability, new plan, big workflow change | Changelog + blog post + email + social + in-app |
+| **Medium** | New integration, notable UX improvement, performance gain customers can feel | Changelog + targeted email or in-app + one social post |
+| **Minor** | Fixes, polish, small additions | Changelog only, batched |
+
+Several medium changes that share a theme ("five improvements to reporting") can be bundled into one major-tier story.
+
+## Ground every claim in the change
+
+- State what the change does, not what it might do for someone. "Exports now include custom fields," not "unlock deeper insights."
+- Use numbers only if they come from the change itself (a benchmark in the PR, a measured speedup). Never invent customer results, adoption, or impact.
+- If a PR says the change is partial ("phase 1," "first step toward"), the announcement says so too.
+- Credit the user who asked for it, where the team does that and the user agreed.
+
+## Watch for marketing that just became wrong
+
+Every shipped change can also make an existing claim false: a new limit, a renamed plan, a removed integration, a price change. Check the site, docs, comparison pages, and ads for statements the change contradicts. On a schedule, this is the claim-drift loop in `marketing-loops`.
+
+New capabilities also open new search demand. A new integration can deserve its own page ("[Product] + [Tool] integration"), and a new feature can answer queries or comparisons the product couldn't win before. Add those to the content backlog (see `content-strategy` and `competitors`).
+
+## Weekly digest format
+
+```markdown
+## Shipped: [date range]
+
+### For customers
+- **[Major]** [You can now ...] (PR #123)
+- **[Medium]** [You can now ...] (PR #130)
+- **[Minor]** [Fixed ...] (PR #131, #134)
+
+### Changelog entry
+## [version or date]
+### Added
+- [Customer-facing description]
+### Changed
+- [...]
+### Fixed
+- [...]
+
+### Drafts
+- Blog post: [working title], [angle], [who it's for]
+- Email: [subject line options] → [segment]
+- Social: [one post per major or medium change, built on its single most useful detail]
+- In-app: [message + where it appears]
+
+### Pages to update
+- [Page]: [statement that's now wrong or incomplete]
+
+### New content opportunities
+- [Query or comparison the change makes winnable]
+```
+
+Use Keep a Changelog headings (Added, Changed, Deprecated, Removed, Fixed, Security) so the changelog stays scannable over time.
+
+## Writing the drafts
+
+- **Changelog:** one line per change, written for a customer and in past or present tense. Link docs for anything non-obvious.
+- **Blog post (major only):** the problem the customer had, what changed, how to use it (with screenshots), and who it's for. The `luckiest-copywriting` skill covers structure; its AI-tell rules apply.
+- **Email:** lead with the change for that segment; one call to action that takes them to the feature. See `emails`.
+- **Social:** one concrete detail per post, with a screenshot or 10-second clip of the feature doing it. See `luckiest-social`.
+
+Drafts are staged for a human to review and send. Nothing in this workflow publishes on its own.