luckiest-co 1.0.37 → 1.0.39

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "luckiest",
       "source": "./",
       "description": "Plan, go, finish, plus bundled free Luckiest skills that work in Claude Code, web chat, and Cowork.",
-      "version": "0.1.36",
+      "version": "0.1.38",
       "author": { "name": "Luckiest" }
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest",
   "description": "Plan, go, finish. Guided planning, progress dashboards, and your luckiest.co tribe inside Claude Code.",
-  "version": "0.1.36",
+  "version": "0.1.38",
   "author": { "name": "Luckiest" }
 }

package/bin/install.js

@@ -135,6 +135,27 @@ function copyWithPathReplacement(srcDir, destDir, pathPrefix) {
   }
 }
 
+// Plugin skills live in short folders (skills/ads, skills/plan) so the plugin
+// menu shows /luckiest:ads with no folder alias. Outside the plugin there is no
+// namespace, so they go to ~/.claude/skills as luckiest-ads instead of a bare
+// ads that could overwrite or clash with the user's own skills.
+const BARE_SKILLS = new Set(['brainstorm', 'remix']);
+const homeName = (folder) =>
+  folder.startsWith('luckiest-') || BARE_SKILLS.has(folder) ? folder : `luckiest-${folder}`;
+
+/** Copy each plugin skill folder into skillsRoot under its home name, then fix its name line. */
+function copySkills(srcDir, skillsRoot, pathPrefix) {
+  const placed = [];
+  for (const folder of fs.readdirSync(srcDir)) {
+    if (!fs.statSync(path.join(srcDir, folder)).isDirectory()) continue;
+    const dest = homeName(folder);
+    copyWithPathReplacement(path.join(srcDir, folder), path.join(skillsRoot, dest), pathPrefix);
+    placed.push(dest);
+  }
+  restoreSkillNames(skillsRoot, placed);
+  return placed;
+}
+
 /**
  * Plugin skills carry short names (name: ads) so the plugin menu shows
  * /luckiest:ads. A copy in ~/.claude/skills has no namespace, so a bare /ads
@@ -264,7 +285,7 @@ function pluginSkillNames(globalClaudeDir) {
   // A desktop plugin has no folder to read; it ships the same skills as this package.
   if (desktopPlugin(globalClaudeDir)) {
     const own = path.join(__dirname, '..', 'skills');
-    if (fs.existsSync(own)) fs.readdirSync(own).forEach((n) => names.add(n));
+    if (fs.existsSync(own)) fs.readdirSync(own).forEach((n) => names.add(homeName(n)));
   }
   try {
     const manifest = JSON.parse(
@@ -274,7 +295,7 @@ function pluginSkillNames(globalClaudeDir) {
       if (!key.startsWith('luckiest@')) continue;
       for (const item of Array.isArray(value) ? value : [value]) {
         const dir = item && item.installPath && path.join(item.installPath, 'skills');
-        if (dir && fs.existsSync(dir)) fs.readdirSync(dir).forEach((n) => names.add(n));
+        if (dir && fs.existsSync(dir)) fs.readdirSync(dir).forEach((n) => names.add(homeName(n)));
       }
     }
   } catch {
@@ -536,8 +557,8 @@ function install(isGlobal) {
     const dirSrc = path.join(src, dir);
     const dirDest = path.join(claudeDir, dir);
     if (fs.existsSync(dirSrc)) {
-      copyWithPathReplacement(dirSrc, dirDest, pathPrefix);
-      if (dir === 'skills') restoreSkillNames(dirDest, fs.readdirSync(dirSrc));
+      if (dir === 'skills') copySkills(dirSrc, dirDest, pathPrefix);
+      else copyWithPathReplacement(dirSrc, dirDest, pathPrefix);
       console.log(`  ${green}✓${reset} Installed ${dir}`);
     }
   }
@@ -822,4 +843,4 @@ if (require.main === module) {
   });
 }
 
-module.exports = { placeSkills, dropPluginDuplicates, restoreSkillNames, hasMarketplacePlugin, pluginSkillNames };
+module.exports = { placeSkills, dropPluginDuplicates, restoreSkillNames, hasMarketplacePlugin, pluginSkillNames, copySkills, homeName };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest-co",
-  "version": "1.0.37",
+  "version": "1.0.39",
   "description": "Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.",
   "bin": {
     "luckiest-co": "./bin/install.js"

package/skills/{luckiest-ab-testing → ab-testing}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-ab-testing
+name: ab-testing
 description: Plan, design, analyze, and scale A/B tests and growth experiments for marketers — builds valid hypotheses, sizes samples, picks primary/secondary/guardrail metrics, guards against peeking and Sample Ratio Mismatch, and runs an ongoing experimentation program. Use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "MVT," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," "experiment playbook," "sample ratio mismatch," "SRM," "my test results look weird," "why is my split uneven," or "Bayesian A/B test." Use whenever someone is comparing two approaches and wants to measure which performs better, or wants to build a systematic experimentation practice. For tracking implementation, see luckiest-analytics. For page-level conversion optimization, see luckiest-cro.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-ad-creative → ad-creative}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-ad-creative
+name: ad-creative
 description: "Generates, iterates, and scales ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform, and iterates from real performance data. Use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see luckiest-ads. For landing page copy, see luckiest-copywriting."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-ads → ads}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-ads
+name: ads
 description: "Plans, optimizes, and scales paid advertising campaigns — campaign strategy, audience targeting, bidding, and optimization. Use when the user wants help with paid advertising on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' For bulk ad creative generation and iteration, see luckiest-ad-creative. For landing page optimization, see luckiest-cro."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-advisors → advisors}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-advisors
+name: advisors
 description: Use when someone asks to pressure-test, stress-test, validate, or get a brutal second opinion on an idea before building it — "convene the council", "kill or keep this", "should I build this", "roast this idea", "advisors", or "/luckiest-advisors". Spins up SEVEN independent persona agents who attack the idea from every angle using current real-world signals, then a Judge returns one LOVE / UPLIFT / LEAVE OUT verdict with the cheapest 48-hour test to de-risk it.
 argument-hint: "[the idea to pressure-test]  [--days N]"
 license: See ATTRIBUTION.md

package/skills/{luckiest-aeo-grader → aeo-grader}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-aeo-grader
+name: aeo-grader
 description: Grade a website's AEO (Answer Engine Optimization) — how findable and citable it is to AI answer engines like ChatGPT, Perplexity, Gemini, and Claude. Use this whenever the user wants an AEO audit, asks "how does my site do in AI search / LLMs / ChatGPT", wants an AEO score or grade, mentions getting cited by AI, llms.txt, AI crawlers (GPTBot, ClaudeBot, PerplexityBot), or asks why an AI engine isn't surfacing their content. Also trigger on "luckiest-aeo-grader", "AEO report", "AEO grade", or "answer engine optimization", even if the user just pastes a URL and asks how it scores.
 license: See ATTRIBUTION.md
 allowed-tools: Bash, Read, WebSearch, AskUserQuestion

package/skills/{luckiest-ai-seo → ai-seo}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-ai-seo
+name: ai-seo
 description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'AGENTS.md,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see luckiest-seo-audit. For structured data implementation, see luckiest-schema."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-analytics → analytics}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-analytics
+name: analytics
 description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "consent mode," "server-side tracking," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see luckiest-ab-testing.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-aso → aso}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-aso
+name: aso
 description: "When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'app store audit,' 'Play Store listing,' 'grade my app listing,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-brandkit → brandkit}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-brandkit
+name: brandkit
 description: >-
   Produce a full set of photoreal brand mockups for a campaign or portfolio: merch
   (hat, hoodie, tee), print (business cards, letterhead, posters, gift card, brand

package/skills/{luckiest-brandkit-sizing → brandkit-sizing}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-brandkit-sizing
+name: brandkit-sizing
 description: >-
   Real-world logo size and placement for brand mockups: apparel (left chest,
   center chest, full front, upper back, full back, back neck, sleeve, hoodie),

package/skills/{luckiest-churn-prevention → churn-prevention}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-churn-prevention
+name: churn-prevention
 description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see luckiest-emails. For in-app upgrade paywalls, see luckiest-paywalls."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-co-marketing → co-marketing}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-co-marketing
+name: co-marketing
 description: "When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' Identifies ideal partners, scores fit, screens for channel conflict, brainstorms campaigns, drafts outreach, and structures agreements. For customer referral programs, see luckiest-referrals. For launch-specific partnerships, see luckiest-launch."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder → coder}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder
+name: coder
 description: Use when starting ANY coding conversation or task — establishes how to find and invoke the right Luckiest Coder skill before you do anything else, including clarifying questions, reading files, or exploring the codebase. Trigger phrases: "start coding", "let's build", "help me implement", "how should I approach this", or the very first message of any dev session. Requires skill invocation BEFORE any response.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-brainstorming → coder-brainstorming}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-brainstorming
+name: coder-brainstorming
 description: Use BEFORE any creative or build work — creating features, building components, adding functionality, or modifying behavior. Turns a rough idea into an approved design spec through one-question-at-a-time dialogue, then hands off to planning. Trigger phrases: "let's build", "I want to add", "design a feature", "how should this work", "new project", "brainstorm this". Gates all implementation until a design is approved.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-consistency → coder-consistency}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-consistency
+name: coder-consistency
 description: Use before finishing a branch, opening a PR, or calling a multi-step feature done — a read-only cross-check that what was built matches what was planned, with no drift, scope creep, or constitution violations. Trigger on "does this match the plan", "check for drift", "did we build what we said", "consistency check", or the moment implementation is complete and you are about to ship. Distinct from verification (does it run) — this checks does it match intent.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-constitution → coder-constitution}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-constitution
+name: coder-constitution
 description: Use to create, amend, or check a project's constitution — the small set of versioned, non-negotiable principles every plan, review, and implementation must obey. Trigger on "set up a constitution", "what are our project rules", "amend the constitution", "does this violate our principles", or the start of any multi-session build where the guardrails should be fixed in writing. Also runs as the Constitution Check gate inside planning and review.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-debugging → coder-debugging}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-debugging
+name: coder-debugging
 description: Use when hunting the root cause of any bug, test failure, crash, or unexpected behavior — before proposing or attempting a fix. Trigger phrases include "debug this", "why is this failing", "find the root cause", "this test is flaky", "the build broke", "it works sometimes", or "/luckiest-coder-debugging". Enforces a four-phase root-cause-first process (investigate, pattern-match, hypothesize, implement) and blocks symptom fixes.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-dispatching-parallel-agents → coder-dispatching-parallel-agents}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-dispatching-parallel-agents
+name: coder-dispatching-parallel-agents
 description: Use when you face 2+ independent problems that can be worked without shared state or sequential dependencies — e.g. 3+ test files failing for different root causes, multiple subsystems broken independently, or several bugs in different domains. Dispatches one focused subagent per problem domain so investigations run concurrently. Trigger on "fix all these failing tests", "these are unrelated bugs", "parallelize this", or "split this across agents".
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-executing-plans → coder-executing-plans}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-executing-plans
+name: coder-executing-plans
 description: Use when you have a written implementation plan and need to execute it task-by-task in this session with review checkpoints. Trigger phrases include "execute this plan", "run the plan", "implement this plan", "work through the plan", or "/luckiest-coder-executing-plans". Loads the plan, reviews it critically, executes each task with verifications, and stops to ask rather than guess when blocked.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-finishing-a-branch → coder-finishing-a-branch}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-finishing-a-branch
+name: coder-finishing-a-branch
 description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. Guides completion of a development branch by verifying tests, detecting the workspace environment (normal repo, named-branch worktree, or detached HEAD), then presenting structured options for local merge, pushing a Pull Request, keeping the branch, or discarding it — and handling worktree cleanup safely. Trigger phrases include "finish this branch", "I'm done, what next", "merge or PR this work", "wrap up this feature", or "clean up after implementation".
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-git-worktrees → coder-git-worktrees}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-git-worktrees
+name: coder-git-worktrees
 description: Use when starting feature work that needs isolation from your current workspace, or before executing an implementation plan, to guarantee an isolated workspace exists. Sets up isolation via your platform's native worktree tools or a manual git worktree fallback, verifies the directory is gitignored, runs project setup, and confirms a clean test baseline. Trigger phrases include "set up a worktree", "isolate this work", "create an isolated workspace", "work on a separate branch safely", or before starting any multi-step implementation.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-guard → coder-guard}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-guard
+name: coder-guard
 description: >-
   Safety guardrails for risky sessions. Warns before destructive shell commands
   (rm -rf, DROP TABLE, TRUNCATE, git push --force, git reset --hard, kubectl delete,

package/skills/{luckiest-coder-qa → coder-qa}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-qa
+name: coder-qa
 description: >-
   Systematically QA-test a running web app in a real browser, then fix the bugs it
   finds. Explores pages, drives interactions, captures screenshot evidence, scores app

package/skills/{luckiest-coder-receiving-code-review → coder-receiving-code-review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-receiving-code-review
+name: coder-receiving-code-review
 description: Use when you receive code review feedback (from a human, a reviewer subagent, or a GitHub PR comment) and are about to respond or implement, especially if a suggestion seems unclear, technically questionable, or conflicts with prior decisions. Trigger phrases include "the reviewer said", "respond to this review", "should I make this change they suggested". Enforces verify-before-implement and bans performative agreement like "You're absolutely right".
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-requesting-code-review → coder-requesting-code-review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-requesting-code-review
+name: coder-requesting-code-review
 description: Use when you have finished a task, implemented a major feature, fixed a complex bug, or are about to merge to main and want a fresh reviewer to catch issues before they cascade. Trigger phrases include "review this before I merge", "get a code review", "check my changes", "is this ready to merge". Dispatches a reviewer subagent with crafted context (a git SHA range), not your session history.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-shipping → coder-shipping}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-shipping
+name: coder-shipping
 description: >-
   Release engineering for a finished feature branch — the step after
   luckiest-coder-finishing-a-branch. Runs the full path to production: merge base,

package/skills/{luckiest-coder-subagent-driven-development → coder-subagent-driven-development}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-subagent-driven-development
+name: coder-subagent-driven-development
 description: Use when executing an implementation plan of mostly-independent tasks in the current session — dispatches a fresh implementer subagent per task, a spec+quality review after each, and a broad whole-branch review at the end. Trigger on "execute this plan", "run the plan with subagents", "implement these tasks one by one", or after writing a plan when you want same-session execution with review gates rather than a parallel session.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-tdd → coder-tdd}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-tdd
+name: coder-tdd
 description: Use when implementing ANY feature or bugfix, before writing implementation code — enforces the red-green-refactor cycle (write a failing test, watch it fail, write minimal code to pass). Trigger phrases: "add a feature", "fix this bug", "implement", "write tests", "TDD this", "should I test first". Covers new features, bug fixes, refactors, and behavior changes.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-verification → coder-verification}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-verification
+name: coder-verification
 description: Use before claiming any work is done, fixed, passing, or ready — and before committing, pushing, or opening a PR. Requires running the actual verification command and reading its output first. Trigger on "is it done", "did the tests pass", "confirm the fix", "ready to commit", or any moment you are about to say "Done", "Fixed", "Perfect", or "should work now". Evidence before assertions, always.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-writing-plans → coder-writing-plans}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-writing-plans
+name: coder-writing-plans
 description: Use when you have a spec or requirements for a multi-step coding task and need a detailed implementation plan before touching code. Trigger phrases include "write a plan", "plan this feature", "break this into tasks", "create an implementation plan", "turn this spec into steps", or "/luckiest-coder-writing-plans". Produces a bite-sized, TDD-structured, fully-specified plan an engineer with zero codebase context can execute task-by-task.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-coder-writing-skills → coder-writing-skills}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-coder-writing-skills
+name: coder-writing-skills
 description: Use when creating a new Agent Skill, editing or refactoring an existing SKILL.md, or verifying a skill actually changes agent behavior before deployment. Trigger phrases include "write a skill", "create a skill", "improve this skill", "why isn't my skill triggering", "test this skill", "the skill description isn't matching". Applies TDD (baseline failure first, then write, then close loopholes) to process documentation.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-cold-email → cold-email}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-cold-email
+name: cold-email
 description: Writes B2B cold emails and follow-up sequences that get replies, and helps land them in the inbox and stay compliant. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, multi-touch follow-up sequences, reply handling, deliverability, and outbound compliance. For warm/lifecycle email sequences, see luckiest-emails. For sales collateral beyond emails, see luckiest-sales-enablement.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-community-marketing → community-marketing}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-community-marketing
+name: community-marketing
 description: "Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, turn customers into evangelists, moderate or handle a community crisis, or wind down a fading community. Trigger phrases: \"build a community,\" \"community strategy,\" \"Discord community,\" \"Slack community,\" \"community-led growth,\" \"brand advocates,\" \"user community,\" \"forum strategy,\" \"community engagement,\" \"grow our community,\" \"ambassador program,\" \"community flywheel,\" \"community moderation,\" \"community is dying.\""
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-competitor-profiling → competitor-profiling}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-competitor-profiling
+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.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-competitors → competitors}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-competitors
+name: competitors
 description: "Creates competitor comparison and alternative pages for SEO, AI answer engines, and sales enablement. Use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'best alternative to X,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Handles content that positions a product against competitors across four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see luckiest-sales-enablement."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-content-strategy → content-strategy}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-content-strategy
+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:

package/skills/{luckiest-copy-editing → copy-editing}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-copy-editing
+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.' 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:

package/skills/{luckiest-copywriting → copywriting}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-copywriting
+name: copywriting
 description: "Writes, rewrites, and improves conversion marketing copy for any page — homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Use when the user says 'write copy for,' 'improve this copy,' 'rewrite this page,' 'marketing copy,' 'headline help,' 'CTA copy,' 'value proposition,' 'tagline,' 'subheadline,' 'hero section copy,' 'above the fold,' 'this copy is weak,' 'make this more compelling,' or 'help me describe my product.' Use whenever someone is working on website text that needs to persuade or convert. For email copy, see luckiest-emails. For popup copy, see luckiest-popups. For editing existing copy, see luckiest-copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see luckiest-offers."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-copywriting-humanize → copywriting-humanize}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-copywriting-humanize
+name: copywriting-humanize
 description: "When the user wants text to stop sounding AI-generated. Use when the user says 'humanize this,' 'make this sound human,' 'this reads like ChatGPT,' 'remove the AI tells,' 'de-slop this,' 'AI slop,' 'does this sound like AI,' 'sounds robotic,' 'too many em dashes,' 'make this sound like me,' 'match my voice,' or asks to strip promotional fluff, filler, hedging, or rule-of-three padding out of a draft. Also use as a finishing pass on copy, docs, posts, or PR descriptions before they ship. For editing marketing copy for persuasion, see luckiest-copy-editing. For writing new copy, see luckiest-copywriting."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-cro → cro}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-cro
+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:

package/skills/{luckiest-customer-research → customer-research}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-customer-research
+name: customer-research
 description: "When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions \"customer research,\" \"ICP research,\" \"talk to customers,\" \"analyze transcripts,\" \"customer interviews,\" \"survey analysis,\" \"support ticket analysis,\" \"voice of customer,\" \"VOC,\" \"build personas,\" \"customer personas,\" \"jobs to be done,\" \"JTBD,\" \"what do customers say,\" \"what are customers struggling with,\" \"Reddit mining,\" \"G2 reviews,\" \"review mining,\" \"digital watering holes,\" \"community research,\" \"forum research,\" \"competitor reviews,\" \"customer sentiment,\" or \"find out why customers churn/convert/buy.\" Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see luckiest-copywriting. For acting on research to improve pages, see luckiest-cro."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-design-website → design-website}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-design-website
+name: design-website
 description: "Builds a premium, scroll-driven landing page for any business and holds it to a real design floor. Scroll is the timeline: video scrubs under the wheel, sections pin and advance, rails pan sideways, headlines assemble, the ground shifts colour. Interviews the human first, picks one of eight page grammars plus a bespoke signature move so no two builds share a skeleton, writes copy with luckiest-copywriting, builds from own footage or generated assets, ships real semantic HTML, then verifies by screenshotting its own scroll and grading contrast, dead scroll and INP. Use for 'scrollytelling', 'scroll animation site', 'a site where scrolling plays a video', 'Apple-style landing page', 'interactive landing page', 'make my brand a scroll experience', 'rebuild my landing page as an experience', 'this looks like a template', 'this looks AI-made', 'design my website', or any page that should feel like an experience rather than a document."
 license: See ATTRIBUTION.md
 allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion

package/skills/{luckiest-directory-submissions → directory-submissions}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-directory-submissions
+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," "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:

package/skills/{luckiest-emails → emails}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-emails
+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.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-extract-design-system → extract-design-system}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-extract-design-system
+name: extract-design-system
 description: Use when reverse-engineering a public website's visual design into project-local starter token files (colors, fonts, spacing, radius, shadow). Trigger on "extract design system", "pull tokens from this site", "reverse-engineer this site's styling", "get the colors/fonts from", or "generate starter tokens from a URL". Extraction and initialization only — not a full component library or pixel-perfect clone.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-free-tools → free-tools}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-free-tools
+name: free-tools
 description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see luckiest-lead-magnets.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-image → image}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-image
+name: image
 description: "When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. Also use when the user mentions 'AI image generation,' 'generate an image,' 'create a graphic,' 'product mockup,' 'hero image,' 'social media graphic,' 'banner image,' 'cover photo,' 'profile banner,' 'listing screenshot,' 'Flux,' 'Flux Kontext,' 'Midjourney,' 'DALL-E,' 'GPT Image,' 'ChatGPT Images,' 'Ideogram,' 'Gemini image,' 'Nano Banana,' 'Recraft,' 'Stable Diffusion,' 'Canva,' 'Figma,' 'image optimization,' 'compress images,' 'WebP,' or 'OG image.' Use this for general-purpose marketing image creation and optimization. For paid ad image creative and platform-specific ad specs, see luckiest-ad-creative. For video production, see luckiest-video."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-launch → launch}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-launch
+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."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-lead-magnets → lead-magnets}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-lead-magnets
+name: lead-magnets
 description: When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see luckiest-free-tools. For writing the actual content, see luckiest-copywriting. For the email sequence after capture, see luckiest-emails.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-marketing-ideas → marketing-ideas}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-marketing-ideas
+name: marketing-ideas
 description: "When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (luckiest-ads, luckiest-social, luckiest-emails, etc.)."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-marketing-plan → marketing-plan}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-marketing-plan
+name: marketing-plan
 description: When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-marketing-psychology → marketing-psychology}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-marketing-psychology
+name: marketing-psychology
 description: "Applies psychological principles, mental models, and behavioral science to marketing decisions. Diagnoses the real behavioral obstacle, then recommends the 2-3 highest-leverage models (not the whole catalog) with ethical, concrete applications. Use when the user wants to understand why people buy, influence behavior ethically, or make better marketing decisions. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' For applying psychology to specific pages, see luckiest-cro; for pricing tactics, see luckiest-pricing; for copy framing, see luckiest-copywriting."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-model-router → model-router}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-model-router
+name: model-router
 description: Use when the user asks which agent or which model should handle a task. Two modes. Agent mode detects which of Claude, Codex, Cursor, Conductor, or Factory is installed and picks the best fit for the prompt. Model mode tags each task with a Haiku, Sonnet, or Opus tier by task type, so subagents run on the smallest model that fits. Triggers include "which tool should I use", "route this", "best model for this task", "haiku or opus", "which model for each task", "tag tasks with models", and /luckiest plan drafting a task list. Use it whenever someone is choosing between coding agents or model sizes, even if they don't name one.
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-offers → offers}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-offers
+name: offers
 description: "When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read luckiest-pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see luckiest-pricing. For the page that presents the offer, see luckiest-copywriting. For the launch moment, see luckiest-launch. For sales collateral, see luckiest-sales-enablement."
 license: See ATTRIBUTION.md
 metadata:

package/skills/{luckiest-onboarding → onboarding}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: luckiest-onboarding
+name: onboarding
 description: Optimizes post-signup onboarding, user activation, first-run experience, and time-to-value so signups turn into retained users. Use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," "first session experience," "trial-to-paid conversion," "free trial activation," "reverse trial," "app onboarding screens," or "permission priming." Use whenever users are signing up but not sticking around. For signup/registration optimization, see luckiest-signup. For ongoing email sequences, see luckiest-emails.
 license: See ATTRIBUTION.md
 metadata: