luckiest-co 1.0.38 → 1.0.40

package/skills/luckiest-copywriting/references/natural-transitions.md

@@ -1,272 +0,0 @@
-# Natural Transitions
-
-Transitional phrases to guide readers through your content. Good signposting improves readability, user engagement, and helps search engines understand content structure.
-
-Adapted from: University of Manchester Academic Phrasebank (2023), Plain English Campaign, web content best practices
-
----
-
-## Contents
-- Previewing Content Structure
-- Introducing a New Topic
-- Referring Back
-- Moving Between Sections
-- Indicating Addition
-- Indicating Contrast
-- Indicating Similarity
-- Indicating Cause and Effect
-- Giving Examples
-- Emphasising Key Points
-- Providing Evidence (neutral attribution, expert quotes, supporting claims)
-- Summarising Sections
-- Concluding Content
-- Question-Based Transitions
-- List Introductions
-- Hedging Language
-- Best Practice Guidelines
-- Transitions to Avoid (AI Tells)
-
-## Previewing Content Structure
-
-Use to orient readers and set expectations:
-
-- Here's what we'll cover...
-- This guide walks you through...
-- Below, you'll find...
-- We'll start with X, then move to Y...
-- First, let's look at...
-- Let's break this down step by step.
-- The sections below explain...
-
----
-
-## Introducing a New Topic
-
-- When it comes to X,...
-- Regarding X,...
-- Speaking of X,...
-- Now let's talk about X.
-- Another key factor is...
-- X is worth exploring because...
-
----
-
-## Referring Back
-
-Use to connect ideas and reinforce key points:
-
-- As mentioned earlier,...
-- As we covered above,...
-- Remember when we discussed X?
-- Building on that point,...
-- Going back to X,...
-- Earlier, we explained that...
-
----
-
-## Moving Between Sections
-
-- Now let's look at...
-- Next up:...
-- Moving on to...
-- With that covered, let's turn to...
-- Now that you understand X, here's Y.
-- That brings us to...
-
----
-
-## Indicating Addition
-
-- Also,...
-- Plus,...
-- On top of that,...
-- What's more,...
-- Another benefit is...
-- Beyond that,...
-- In addition,...
-- There's also...
-
-**Note:** Use "moreover" and "furthermore" sparingly. They can sound AI-generated when overused.
-
----
-
-## Indicating Contrast
-
-- However,...
-- But,...
-- That said,...
-- On the flip side,...
-- In contrast,...
-- Unlike X, Y...
-- While X is true, Y...
-- Despite this,...
-
----
-
-## Indicating Similarity
-
-- Similarly,...
-- Likewise,...
-- In the same way,...
-- Just like X, Y also...
-- This mirrors...
-- The same applies to...
-
----
-
-## Indicating Cause and Effect
-
-- So,...
-- This means...
-- As a result,...
-- That's why...
-- Because of this,...
-- This leads to...
-- The outcome?...
-- Here's what happens:...
-
----
-
-## Giving Examples
-
-- For example,...
-- For instance,...
-- Here's an example:...
-- Take X, for instance.
-- Consider this:...
-- A good example is...
-- To illustrate,...
-- Like when...
-- Say you want to...
-
----
-
-## Emphasising Key Points
-
-- Here's the key takeaway:...
-- The important thing is...
-- What matters most is...
-- Don't miss this:...
-- Pay attention to...
-- This is critical:...
-- The bottom line?...
-
----
-
-## Providing Evidence
-
-Use when citing sources, data, or expert opinions:
-
-### Neutral attribution
-- According to [Source],...
-- [Source] reports that...
-- Research shows that...
-- Data from [Source] indicates...
-- A study by [Source] found...
-
-### Expert quotes
-- As [Expert] puts it,...
-- [Expert] explains,...
-- In the words of [Expert],...
-- [Expert] notes that...
-
-### Supporting claims
-- This is backed by...
-- Evidence suggests...
-- The numbers confirm...
-- This aligns with findings from...
-
----
-
-## Summarising Sections
-
-- To recap,...
-- Here's the short version:...
-- In short,...
-- The takeaway?...
-- So what does this mean?...
-- Let's pull this together:...
-- Quick summary:...
-
----
-
-## Concluding Content
-
-- Wrapping up,...
-- The bottom line is...
-- Here's what to do next:...
-- To sum up,...
-- Final thoughts:...
-- Ready to get started?...
-- Now it's your turn.
-
-**Note:** Avoid "In conclusion" at the start of a paragraph. It's overused and signals AI writing.
-
----
-
-## Question-Based Transitions
-
-Useful for conversational tone and featured snippet optimization:
-
-- So what does this mean for you?
-- But why does this matter?
-- How do you actually do this?
-- What's the catch?
-- Sound complicated? It's not.
-- Wondering where to start?
-- Still not sure? Here's the breakdown.
-
----
-
-## List Introductions
-
-For numbered lists and step-by-step content:
-
-- Here's how to do it:
-- Follow these steps:
-- The process is straightforward:
-- Here's what you need to know:
-- Key things to consider:
-- The main factors are:
-
----
-
-## Hedging Language
-
-For claims that need qualification or aren't absolute:
-
-- may, might, could
-- tends to, generally
-- often, usually, typically
-- in most cases
-- it appears that
-- evidence suggests
-- this can help
-- many experts believe
-
----
-
-## Best Practice Guidelines
-
-1. **Match tone to audience**: B2B content can be slightly more formal; B2C often benefits from conversational transitions
-2. **Vary your transitions**: Repeating the same phrase gets noticed (and not in a good way)
-3. **Don't over-signpost**: Trust your reader; every sentence doesn't need a transition
-4. **Use for scannability**: Transitions at paragraph starts help skimmers navigate
-5. **Keep it natural**: Read aloud; if it sounds forced, simplify
-6. **Front-load key info**: Put the important word or phrase early in the transition
-
----
-
-## Transitions to Avoid (AI Tells)
-
-These phrases are overused in AI-generated content:
-
-- "That being said,..."
-- "It's worth noting that..."
-- "At its core,..."
-- "In today's digital landscape,..."
-- "When it comes to the realm of..."
-- "This begs the question..."
-- "Let's delve into..."
-
-See the luckiest-seo-audit skill's `references/ai-writing-detection.md` for a complete list of AI writing tells.

package/skills/luckiest-copywriting-humanize/SKILL.md

@@ -1,82 +0,0 @@
----
-name: luckiest-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:
-  version: "1.0.1"
-  listing_id: luckiest-copywriting-humanize
-  author: luckiest
----
-
-# Copywriting Humanize
-
-This skill acts as an editor that finds and removes the tells of AI-generated writing so a draft reads like a person wrote it. The pattern catalog comes from Wikipedia's "Signs of AI writing" guide, maintained by WikiProject AI Cleanup.
-
-## Staying current
-
-On activation, call the Luckiest MCP check_updates tool with { listingId: "03206f00-d5c7-4e0d-b541-09aec431a0c7", installedSemver: "1.0.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-copywriting-humanize", skill_version: "1.0.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 files
-
-- **references/patterns.md** — the numbered catalog of 34 AI tells with before/after examples. Load it before every rewrite. It is the working reference for both the draft and the audit.
-- **references/detection.md** — what not to flag, and the signs of genuine human writing. Load it before judging text the user did not write, before answering "does this sound like AI," and any time a rewrite is about to strip something that might be the author's actual voice.
-
-## The four rules
-
-1. **Identify the patterns.** Scan against references/patterns.md. Look for clusters, not isolated hits.
-2. **Preserve the information, not the shape.** Every claim in the original survives. Depth does not have to be uniform: compress the dull parts, dwell where a person would, merge or split paragraphs freely. When keeping information and mirroring structure pull against each other, the information wins.
-3. **Never invent facts.** The rewrite must not contain a fact, name, number, date, quote, or citation absent from the source. Trading a vague claim for a specific one is allowed only when the specific comes from the source or the user. If a sentence needs real detail to work, ask for it or write the plain version without it. Opinions and reactions are voice, not facts. (In fiction, invented detail is the job. This rule governs everything else.)
-4. **Match the voice.** Fit the intended register: formal, casual, technical. Add personality only where the content calls for it.
-
-## Voice calibration
-
-If the user supplies a writing sample of their own, read it before rewriting. Note sentence lengths, vocabulary, paragraph openings, punctuation, recurring phrases, and transitions, then match those habits rather than merely deleting AI patterns. Do not upgrade casual words or regularize deliberate quirks.
-
-A sample outranks every style rule in this skill, including the em dash rule in pattern 14. If the sample uses em dashes, keep them at roughly the sample's frequency. Matching the author beats scrubbing the tell.
-
-## Personality and soul
-
-Avoiding AI patterns is half the job. Voiceless writing is as obvious as slop.
-
-Apply this only where the content and the author's voice call for it: blog posts, essays, opinion, personal writing. For encyclopedic, technical, legal, or reference text, neutral and plain is the correct human voice, so do not inject opinions or first person there.
-
-Where voice is appropriate, avoid uniform sentence structures, bloodless neutrality, and perfect organization. Let the writer have opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never add factual claims to manufacture that personality.
-
-## Never touch
-
-Rewrite prose only. Leave code blocks, inline code, YAML frontmatter, data tables, link targets, file paths, command names, and quoted or cited passages exactly as they are. A watched phrase inside a quotation, a title, a proper name, or an example where the phrase is being discussed rather than used stays put.
-
-## Invocation modes
-
-**Pasted text (default).** The user gives text in the conversation. Run the full loop and deliver the draft, the audit bullets, and the final rewrite.
-
-**File mode.** The user points at a file. Read it, run the loop internally, then rewrite the file in place so it contains only the final version. Report a short summary of what changed instead of pasting the whole rewrite back.
-
-**Audit only.** The user asks whether text sounds AI-generated but does not ask for a rewrite. Load references/detection.md first, then name the specific patterns with line references and a confidence read. Do not rewrite anything unless asked.
-
-**Embedded mode.** Another skill or agent is using this as one step of a larger job: a PR description, a commit message, a doc. Run the loop internally and output only the final text. No draft, no audit bullets, no summary.
-
-## Process
-
-1. Read the input and identify every instance of the patterns in references/patterns.md.
-2. Write a draft rewrite. Check that it reads naturally aloud, varies sentence length, prefers specific details and simple constructions (is, are, has), and holds the right register.
-3. Audit the draft against two questions, answered briefly: **"What still makes this read as AI-generated?"** and **"Does the rewrite state any fact, name, number, date, or citation that is not in the source?"** A fabrication is a defect even when it sounds more human than the vague original.
-4. Run the final scan before delivering. The draft is not done while any of these are true:
-   - it contains an em dash (—) or en dash (–), unless a user sample licenses them;
-   - it contains a curly quote (" " ' ') where a straight quote belongs;
-   - three or more consecutive sentences sit in the same length band;
-   - a heading is followed by a one-line paragraph restating the heading;
-   - a bolded inline header opens a list item.
-5. Deliver what the invocation mode calls for.
-
-## Share the pass with your tribe
-
-After delivering the rewrite, optionally offer, never automatically: "Want me to share this humanizing pass with your Luckiest tribe? Anyone cleaning up similar drafts will see the before and after and which tells got cut." If the user accepts, hand off the summary and the pattern list, not the source text unless they say so. If they decline, or the text is confidential, unpublished, or personal, stop and share nothing.
-
-## Related skills
-
-- **luckiest-copy-editing** — editing existing marketing copy for clarity and conversion.
-- **luckiest-copywriting** — writing new page copy from scratch.
-- **luckiest-thinker** — recovering variety when a draft keeps collapsing to the same generic phrasing.

package/skills/luckiest-cro/SKILL.md

@@ -1,215 +0,0 @@
----
-name: luckiest-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"
-  listing_id: luckiest-cro
-  author: luckiest
----
-
-# Conversion Rate Optimization (CRO)
-
-This skill analyzes marketing pages and produces actionable recommendations to improve conversion rates. It operates as a conversion rate optimization expert.
-
-## 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.
-
-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.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before providing recommendations, identify:
-
-1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
-2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
-3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social, AI answer engines)
-
----
-
-## CRO Analysis Framework
-
-Analyze the page across these dimensions, in order of impact:
-
-### 1. Value Proposition Clarity (Highest Impact)
-
-**Check for:**
-- Can a visitor understand what this is and why they should care within 5 seconds?
-- Is the primary benefit clear, specific, and differentiated?
-- Is it written in the customer's language (not company jargon)?
-
-**Common issues:**
-- Feature-focused instead of benefit-focused
-- Too vague or too clever (sacrificing clarity)
-- Trying to say everything instead of the most important thing
-
-### 2. Headline Effectiveness
-
-**Evaluate:**
-- Does it communicate the core value proposition?
-- Is it specific enough to be meaningful?
-- Does it match the traffic source's messaging?
-
-**Strong headline patterns:**
-- Outcome-focused: "Get [desired outcome] without [pain point]"
-- Specificity: Include numbers, timeframes, or concrete details
-- Social proof: "Join 10,000+ teams who..."
-
-### 3. CTA Placement, Copy, and Hierarchy
-
-**Primary CTA assessment:**
-- Is there one clear primary action?
-- Is it visible without scrolling?
-- Does the button copy communicate value, not just action?
-  - Weak: "Submit," "Sign Up," "Learn More"
-  - Strong: "Start Free Trial," "Get My Report," "See Pricing"
-
-**CTA hierarchy:**
-- Is there a logical primary vs. secondary CTA structure?
-- Are CTAs repeated at key decision points?
-
-### 4. Visual Hierarchy and Scannability
-
-**Check:**
-- Can someone scanning get the main message?
-- Are the most important elements visually prominent?
-- Is there enough white space?
-- Do images support or distract from the message?
-
-### 5. Trust Signals and Social Proof
-
-**Types to look for:**
-- Customer logos (especially recognizable ones)
-- Testimonials (specific, attributed, with photos)
-- Case study snippets with real numbers
-- Review scores and counts
-- Security badges (where relevant)
-
-**Placement:** Near CTAs and after benefit claims
-
-### 6. Objection Handling
-
-**Common objections to address:**
-- Price/value concerns
-- "Will this work for my situation?"
-- Implementation difficulty
-- "What if it doesn't work?"
-
-**Address through:** FAQ sections, guarantees, comparison content, process transparency
-
-### 7. Friction Points
-
-**Look for:**
-- Too many form fields
-- Unclear next steps
-- Confusing navigation
-- Required information that shouldn't be required
-- Mobile experience issues
-- Long load times
-
-### 8. AI-Referred Traffic Fit
-
-Traffic from AI answer engines (ChatGPT, Perplexity, Claude, Gemini) is a fast-growing, high-intent source: these visitors arrive "pre-briefed" from a Q&A session and convert at markedly higher rates than organic search, but tolerate far less top-of-funnel education. If a meaningful share of traffic is AI-referred, check that the page:
-
-- Confirms within seconds that the visitor is in the right place (no meandering intro)
-- Offers fast access to the next step: demo, transparent pricing, comparison content, proof
-- Does not re-explain basics the answer engine already covered
-- Handles homepage landings, since AI engines increasingly send visitors to the brand's front door rather than a deep page
-
----
-
-## Output Format
-
-Structure recommendations as:
-
-### Quick Wins (Implement Now)
-Easy changes with likely immediate impact.
-
-### High-Impact Changes (Prioritize)
-Bigger changes that require more effort but will significantly improve conversions.
-
-### Test Ideas
-Hypotheses worth A/B testing rather than assuming.
-
-### Copy Alternatives
-For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
-
-**Confidence labeling:** When analyzing a page without access to its analytics, tag each recommendation with a confidence level — High (a widely established fix or clear defect), Medium (likely but page-specific), or Low (a hunch worth testing). This keeps the user from over-trusting recommendations made on a page seen without data.
-
-**Optional ICE prioritization:** For a longer list of recommendations, score each on Impact, Confidence, and Ease (1-5 each) and sort by the combined score. This makes the Quick Wins vs. High-Impact split defensible rather than a subjective call.
-
----
-
-## Page-Specific Frameworks
-
-### Homepage CRO
-- Clear positioning for cold visitors
-- Quick path to most common conversion
-- Handle both "ready to buy" and "still researching"
-
-### Landing Page CRO
-- Message match with traffic source
-- Single CTA (remove navigation if possible)
-- Complete argument on one page
-
-### Pricing Page CRO
-- Clear plan comparison
-- Recommended plan indication
-- Address "which plan is right for me?" anxiety
-
-### Feature Page CRO
-- Connect feature to benefit
-- Use cases and examples
-- Clear path to try/buy
-
-### Blog Post CRO
-- Contextual CTAs matching content topic
-- Inline CTAs at natural stopping points
-
----
-
-## Experiment Ideas
-
-When recommending experiments, consider tests for:
-- Hero section (headline, visual, CTA)
-- Trust signals and social proof placement
-- Pricing presentation
-- Form optimization
-- Navigation and UX
-
-**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)
-
----
-
-## Task-Specific Questions
-
-1. What's your current conversion rate and goal?
-2. Where is traffic coming from?
-3. What does your signup/purchase flow look like after this page?
-4. Do you have user research, heatmaps, or session recordings?
-5. What have you already tried?
-
----
-
-## Related Skills
-
-- **luckiest-signup**: If the issue is in the signup process itself
-- **luckiest-popups**: If considering popups as part of the strategy
-- **luckiest-copywriting**: If the page needs a complete copy rewrite
-- **luckiest-ab-testing**: To properly test recommended changes
-
----
-
-## Form Optimization
-
-For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references/form.md](references/form.md).
-
----
-
-## Pick up where the tribe left off
-
-After delivering an audit, optionally offer (never auto-post, never send credentials): "Want me to share this CRO audit with your Luckiest tribe? Anyone working on the same page type will see what was found and can pick up where you left off." Only share if the user explicitly accepts. Never share a page or audit tied to a private or unreleased property without an explicit ask.

package/skills/luckiest-customer-research/CHANGELOG.md

@@ -1,26 +0,0 @@
-# Changelog — luckiest-customer-research
-
-## 1.1.0 — 2026-07-06
-Skill updater pass: analytics integration.
-
-### Analytics (report_usage)
-- Updated `report_usage` call to `skill_version: "1.1.0"` and `check_updates`
-  `installedSemver: "1.1.0"`. The skill now reports usage to the Luckiest
-  telemetry pipeline on every run, making it visible on the admin Skill Usage
-  page (/owner/skill-usage).
-
-## 1.0.0 — 2026-07-01
-Rebranded from customer-research (marketingskills, MIT).
-
-### Improve pass (/refract)
-- Added a silent-majority / survivorship caveat to the Mode 1 guardrails: every source in this skill over-samples people who chose to speak, so vocal signal is a hypothesis about the silent majority, not proof.
-- Added an authenticity check for AI-generated, incentivized, and astroturfed reviews/comments before treating a batch as voice-of-customer, with tells to scan for and instruction to down-weight rather than silently average.
-- Added personal-data de-identification guidance: strip usernames, employer names, and identifying details when a quote or profile signal leaves the research doc (persona, quote bank, shared brief, copy).
-- Dropped candidates that were novelty-for-novelty (extra scoring rubrics, new persona templates, added frameworks) — the original already covers those.
-
-### Network hook
-- Share-with-tribe (offer, never auto-post): after delivering a synthesis, quote bank, or persona, offer to surface findings to the user's Luckiest tribe so others researching the same ICP can build on it. De-identifies first; declines and private/sensitive customer data suppress the offer. No credentials referenced.
-
-### Trend pass (/newsjack + /luckiest-trends)
-- The /luckiest-trends live engine requires Python 3.12+ and social/API setup not available in this non-interactive environment; no live social signal was pulled — no fabrication.
-- One actionable, verifiable signal informed the AI-content authenticity check: the U.S. FTC final rule banning fake and AI-generated consumer reviews and testimonials (effective 2024-10-21; source: FTC, "Rule on the Use of Consumer Reviews and Testimonials," ftc.gov). This makes screening AI/incentivized reviews a current, on-domain default rather than a speculative one.