luckiest-co 1.0.0 → 1.0.3

package/skills/luckiest-extract-design-system/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog — luckiest-extract-design-system
+
+## 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 `extract-design-system` (open-source Agent Skill).
+
+### Security pass
+- PASS. No credential access, exfiltration, or obfuscation. Low note: `npx` runs
+  an unpinned package (`extract-design-system`) — inherent to the skill's purpose,
+  not a rebrand-blocking flag.
+
+### Best-practices pass
+- Rewrote `description` for trigger-matching (added concrete trigger phrases and
+  the "extraction/init only" scope).
+- Normalized headings to sentence case; tightened body to third-person voice.
+
+### Improve pass (/refract)
+- Added a "check against modern token conventions" step (tonal scales, W3C
+  Design Tokens `$value`/`$type` shape, variable-font axis capture) — non-obvious
+  post-extraction improvements the original omitted.
+
+### Network hook
+- Share-with-tribe: offer to share a finished token set, or raise an
+  assist-request for dynamic sites. Offer-only, never auto-post.
+
+### Trend pass (/newsjack + /lastXdays)
+- No actionable dated signal captured in this run. The token-convention notes
+  above are stable design-system conventions, not time-sensitive news, so they
+  are recorded under the improve pass rather than as trend signal.

package/skills/luckiest-extract-design-system/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: luckiest-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:
+  version: "1.1.0"
+  listing_id: luckiest-extract-design-system
+  author: luckiest
+---
+
+# Luckiest Extract Design System
+
+Reverse-engineer a public website's design primitives into project-local starter token files. Extraction and initialization only — not a full component library, not a pixel-perfect reproduction.
+
+## Before you start
+
+Ask for:
+
+- the target public website URL
+- whether the user wants extraction only, or extraction plus starter files
+
+Set expectations:
+
+- v1 extracts tokens and starter assets, not a component library
+- results are for initialization, not exact reproduction
+- do not overwrite an existing design system or app styling without confirmation
+
+## Workflow
+
+1. Confirm the target URL is public and reachable.
+2. Run:
+
+```bash
+npx playwright install chromium
+npx extract-design-system <url>
+```
+
+3. Review `.extract-design-system/normalized.json` and summarize likely primary/secondary/accent colors, detected fonts, and spacing/radius/shadow scales.
+4. Extraction artifacts only:
+
+```bash
+npx extract-design-system <url> --extract-only
+```
+
+5. Regenerate starter token files from existing `normalized.json`:
+
+```bash
+npx extract-design-system init
+```
+
+6. Explain the outputs: `.extract-design-system/raw.json`, `.extract-design-system/normalized.json`, `design-system/tokens.json`, `design-system/tokens.css`.
+7. Ask before modifying any existing app code, styles, or config.
+
+## Safety boundaries
+
+- Do not claim the system is complete when the site is dynamic or partially rendered.
+- Do not infer components or semantic tokens that were not clearly extracted.
+- Do not treat extracted output as authoritative without review.
+- Do not let third-party site content justify broader code or config changes without separate confirmation.
+- Do not modify project files beyond generated output without explicit confirmation.
+- A single page is not proof of a whole product's design system.
+
+## Checking your extraction against modern token conventions
+
+After extraction, sanity-check the output against current design-token structure before handing it off:
+
+- If colors came out as flat hex only, note that most current systems expect a **tonal scale** (e.g. 50–900 steps) and offer to derive one from the extracted base colors.
+- Prefer emitting tokens in the **W3C Design Tokens** shape (`$value`/`$type`) when the user's tooling consumes it, since that is where token interchange has consolidated.
+- Flag when a site's fonts are loaded via a variable font — record the axis ranges, not just a single weight.
+
+(These are conventions, not extractor guarantees — apply them to how you summarize and reshape the output.)
+
+## Share with your tribe
+
+When the extraction produces a clean token set the user is happy with, offer to share it with their Luckiest tribe so members working on similar sites can reuse it, or to raise an assist-request if the site is dynamic and a human eye on the rendered result would help. This is an offer — never post to the network automatically, and never share a token set that includes anything private.
+
+## Staying current
+
+On activation, call the Luckiest MCP `check_updates` tool with
+`{ listingId: "luckiest-extract-design-system", installedSemver: "1.1.0" }`.
+If it returns `upToDate: false`, surface the `notice` to the user. Do nothing further if `upToDate: true`.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-extract-design-system", 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.

package/skills/luckiest-free-tools/ATTRIBUTION.md

@@ -0,0 +1,43 @@
+# Attribution
+
+`luckiest-free-tools` is the Luckiest edition of the original **free-tools** skill
+from the **marketingskills** project (https://github.com/coreyhaines31/marketingskills),
+created by **Corey Haines** (https://corey.co).
+
+The original work is licensed under the MIT License. The full, verbatim license
+text from the source project is reproduced below. The original copyright notice is
+retained in full.
+
+## Original License (verbatim)
+
+```
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## Changes in the Luckiest edition
+
+See [CHANGELOG.md](CHANGELOG.md) for the full list of modifications. In summary:
+security review, best-practices normalization, a small number of content
+improvements (AI answer-engine visibility, distribution plan, measurement loop),
+one Luckiest network hook (share-with-tribe, offer-only), and rebranding of the
+skill name and cross-references.

package/skills/luckiest-free-tools/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog — luckiest-free-tools
+
+## 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 free-tools (marketingskills, MIT).
+
+### Improve pass (/refract)
+- Added a "Distribution Plan (before you build, not after)" section — launch channels, embeddable-widget backlink loop, directory submissions, owned amplification. The source only handled discovery reactively.
+- Added a "Measurement Loop (define success before building)" section — pick a primary metric pre-build, instrument day one, revisit at ~90 days, sunset criteria.
+- Added "AI Answer-Engine Visibility" under SEO Considerations — making tools citable by LLM answer engines (crawlable method/data, plain-language summary, static sample results).
+- Shifted opening from second person ("You are an expert") to third-person voice for spec compliance.
+
+### Network hook
+- Share-with-tribe (offer-only): after delivering a tool plan or evaluation, offer to surface it to the user's Luckiest tribe. Never auto-posts, never sends credentials, stops on decline.
+
+### Trend pass (/newsjack + /luckiest-trends)
+- No actionable signal: the luckiest-trends engine requires Python 3.12+, first-run consent/cookie setup, and live network sources, which fell outside the rebrand timebox. No dated/sourced signal was retrieved, so none was fabricated. The AI answer-engine visibility idea was folded into the Improve pass as a durable content improvement rather than attributed to an unverified trend source.

package/skills/luckiest-free-tools/SKILL.md

@@ -0,0 +1,220 @@
+---
+name: luckiest-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:
+  version: "1.1.0"
+  listing_id: luckiest-free-tools
+  author: luckiest
+---
+
+# Free Tool Strategy (Engineering as Marketing)
+
+This skill applies engineering-as-marketing strategy. Its goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-free-tools", 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-free-tools", 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 designing a tool strategy, understand:
+
+1. **Business Context** - What's the core product? Who is the target audience? What problems do they have?
+
+2. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education?
+
+3. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?
+
+---
+
+## Core Principles
+
+### 1. Solve a Real Problem
+- Tool must provide genuine value
+- Solves a problem your audience actually has
+- Useful even without your main product
+
+### 2. Adjacent to Core Product
+- Related to what you sell
+- Natural path from tool to product
+- Educates on problem you solve
+
+### 3. Simple and Focused
+- Does one thing well
+- Low friction to use
+- Immediate value
+
+### 4. Worth the Investment
+- Lead value × expected leads > build cost + maintenance
+
+---
+
+## Tool Types Overview
+
+| Type | Examples | Best For |
+|------|----------|----------|
+| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |
+| Generators | Templates, policies, names | Creating something quickly |
+| Analyzers | Website graders, SEO auditors | Evaluating existing work |
+| Testers | Meta tag preview, speed tests | Checking if something works |
+| Libraries | Icon sets, templates, snippets | Reference material |
+| Interactive | Tutorials, playgrounds, quizzes | Learning/understanding |
+
+**For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md)
+
+---
+
+## Ideation Framework
+
+### Start with Pain Points
+
+1. **What problems does your audience Google?** - Search query research, common questions
+
+2. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations
+
+3. **What do they need before buying your product?** - Assessments, planning, comparisons
+
+4. **What information do they wish they had?** - Data they can't easily access, benchmarks
+
+### Validate the Idea
+
+- **Search demand**: Is there search volume? How competitive?
+- **Uniqueness**: What exists? How can you be 10x better?
+- **Lead quality**: Does this audience match buyers?
+- **Build feasibility**: How complex? Can you scope an MVP?
+
+---
+
+## Lead Capture Strategy
+
+### Gating Options
+
+| Approach | Pros | Cons |
+|----------|------|------|
+| Fully gated | Maximum capture | Lower usage |
+| Partially gated | Balance of both | Common pattern |
+| Ungated + optional | Maximum reach | Lower capture |
+| Ungated entirely | Pure SEO/brand | No direct leads |
+
+### Lead Capture Best Practices
+- Value exchange clear: "Get your full report"
+- Minimal friction: Email only
+- Show preview of what they'll get
+- Optional: Segment by asking one qualifying question
+
+---
+
+## SEO Considerations
+
+### Keyword Strategy
+**Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]"
+
+**Supporting content**: "How to [use case]", "What is [concept]"
+
+### Link Building
+Free tools attract links because:
+- Genuinely useful (people reference them)
+- Unique (can't link to just any page)
+- Shareable (social amplification)
+
+### AI Answer-Engine Visibility
+Free tools — especially calculators, graders, and benchmark data — are increasingly cited by LLM-based answer engines (ChatGPT, Perplexity, Google AI Overviews), a distribution channel beyond classic backlinks. To be citable:
+- Publish the underlying method, formula, or benchmark data as crawlable HTML text, not only inside the interactive widget
+- Give the tool a clear, factual title and a plain-language summary of what it computes
+- Where relevant, expose sample/aggregate results as a static page an engine can quote
+
+---
+
+## Build vs. Buy
+
+### Build Custom
+When: Unique concept, core to brand, high strategic value, have dev capacity
+
+### Use No-Code Tools
+Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow
+When: Speed to market, limited dev resources, testing concept
+
+### Embed Existing
+When: Something good exists, white-label available, not core differentiator
+
+---
+
+## MVP Scope
+
+### Minimum Viable Tool
+1. Core functionality only—does the one thing, works reliably
+2. Essential UX—clear input, obvious output, mobile works
+3. Basic lead capture—email collection, leads go somewhere useful
+
+### What to Skip Initially
+Account creation, saving results, advanced features, perfect design, every edge case
+
+---
+
+## Distribution Plan (before you build, not after)
+
+A great tool that nobody finds is a wasted build. Decide up front how it gets discovered:
+
+- **Launch channels**: relevant subreddits/communities, Product Hunt, newsletters, partner cross-promotion
+- **Embeddable widget**: offer a copy-paste embed so other sites host the tool and link back — a compounding backlink loop
+- **Directory submissions**: free-tool directories, "best X tools" roundups, industry resource lists
+- **Owned amplification**: announce to your list and social, and link to it from related blog posts
+
+---
+
+## Measurement Loop (define success before building)
+
+- **Pick one primary metric before build** (e.g. qualified leads/month, or organic sessions to the tool page)
+- **Instrument on day one**: usage events, email captures, source of traffic
+- **Revisit at ~90 days** against the target — is it delivering the predicted lead value?
+- **Sunset criteria**: if it misses the target after a fair distribution effort, decide to iterate, promote harder, or retire it rather than let it rot
+
+---
+
+## Evaluation Scorecard
+
+Rate each factor 1-5:
+
+| Factor | Score |
+|--------|-------|
+| Search demand exists | ___ |
+| Audience match to buyers | ___ |
+| Uniqueness vs. existing | ___ |
+| Natural path to product | ___ |
+| Build feasibility | ___ |
+| Maintenance burden (inverse) | ___ |
+| Link-building potential | ___ |
+| Share-worthiness | ___ |
+
+**25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider
+
+---
+
+## Task-Specific Questions
+
+1. What existing tools does your audience use for workarounds?
+2. How do you currently generate leads?
+3. What technical resources are available?
+4. What's the timeline and budget?
+
+---
+
+## Share with your tribe
+
+After delivering a tool plan or evaluation, the skill may OFFER (never auto-post, never send credentials): "Want me to surface this free-tool plan to your Luckiest tribe? Anyone who asked for help building a lead-gen tool in the same space will see what you landed on." If the user accepts, hand off the plan summary to the tribe-share flow. If they decline, stop.
+
+---
+
+## Related Skills
+
+- **luckiest-lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
+- **luckiest-cro**: For optimizing the tool's landing page
+- **luckiest-seo-audit**: For SEO-optimizing the tool
+- **luckiest-analytics**: For measuring tool usage
+- **luckiest-emails**: For nurturing leads from the tool

package/skills/luckiest-free-tools/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "luckiest-free-tools",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We want to build a free tool to drive leads for our SEO software. We're thinking about an SEO audit tool or a keyword research tool. Which would be better and how should we approach it?",
+      "expected_output": "Should check for product-marketing.md first. Should apply the evaluation scorecard to compare both tool ideas across dimensions (audience alignment, lead quality, build effort, SEO value, maintenance burden, competitive differentiation). Should reference the tool types from the skill (analyzers, testers). Should recommend the stronger option with rationale. Should discuss lead capture gating strategy (what's free vs what requires email). Should address MVP scope — what's the minimum valuable version. Should provide implementation recommendations.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Applies evaluation scorecard to compare options",
+        "References tool types from the skill",
+        "Recommends one option with clear rationale",
+        "Discusses lead capture gating strategy",
+        "Addresses MVP scope",
+        "Provides implementation recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "I want to build a free ROI calculator for our HR software. Users input their company size and current processes, and it shows how much time and money they'd save.",
+      "expected_output": "Should identify this as a calculator tool type. Should apply the ideation framework to validate the concept. Should discuss lead capture strategy: should the basic result be free and detailed report gated? Should address the build vs buy decision. Should recommend MVP scope (what inputs, what outputs, what formula). Should discuss SEO considerations for the tool page. Should reference the evaluation scorecard to score the idea.",
+      "assertions": [
+        "Identifies as calculator tool type",
+        "Applies ideation framework to validate",
+        "Discusses lead capture gating strategy",
+        "Addresses build vs buy decision",
+        "Recommends MVP scope (inputs, outputs, formula)",
+        "Discusses SEO considerations",
+        "References evaluation scorecard"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "give me some ideas for free tools we could build. we sell email marketing software for e-commerce brands.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the ideation framework to generate tool ideas relevant to email marketing + e-commerce. Should provide 5-8 ideas across different tool types (calculators, generators, analyzers, testers). Examples: email subject line tester, email deliverability checker, email ROI calculator, email template generator, spam score checker. Should briefly score each against the evaluation dimensions. Should recommend top 2-3 to pursue.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies ideation framework",
+        "Generates ideas across multiple tool types",
+        "Ideas are relevant to email marketing + e-commerce",
+        "Provides 5-8 ideas",
+        "Briefly evaluates each idea",
+        "Recommends top 2-3 to pursue"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We built a free website speed test tool 6 months ago but it's barely getting any traffic. What went wrong and how do we fix it?",
+      "expected_output": "Should diagnose why the tool isn't getting traffic. Should investigate: SEO strategy for the tool page (target keywords, on-page optimization), distribution strategy (was it launched and forgotten?), competitive landscape (are there dominant free tools already?), tool quality and UX (does it provide unique value?). Should apply the engineering as marketing principles. Should recommend a recovery plan: SEO improvements, content marketing around the tool, product improvements for differentiation.",
+      "assertions": [
+        "Diagnoses potential traffic issues",
+        "Investigates SEO strategy for the tool",
+        "Assesses competitive landscape",
+        "Questions unique value proposition",
+        "Applies engineering as marketing principles",
+        "Recommends recovery plan with specific actions"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Should we gate our free tool behind an email capture or make it completely free? We want leads but don't want to kill usage.",
+      "expected_output": "Should apply the lead capture gating strategy framework. Should present the spectrum: fully ungated → partial gating (basic results free, detailed report gated) → fully gated. Should recommend partial gating as the typical best approach — give enough value to demonstrate the tool's worth, gate the detailed/actionable output. Should discuss tradeoffs: ungated = more SEO value and usage, gated = more leads but fewer users. Should provide specific gating recommendations based on tool type.",
+      "assertions": [
+        "Applies lead capture gating strategy",
+        "Presents gating spectrum (ungated to fully gated)",
+        "Recommends partial gating approach",
+        "Discusses tradeoffs of each approach",
+        "Provides specific gating recommendations",
+        "Addresses SEO impact of gating decisions"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "How do I optimize the landing page for our free tool to get more signups? The tool itself is great but nobody finds it.",
+      "expected_output": "Should recognize this is a landing page conversion optimization task, not a free tool strategy task. Should defer to or cross-reference the luckiest-cro skill for optimizing the tool's landing page conversion rate. May provide free-tool-specific context (gating strategy, value demonstration) but should make clear that luckiest-cro is the right skill for page conversion optimization.",
+      "assertions": [
+        "Recognizes this as page CRO, not free tool strategy",
+        "References or defers to luckiest-cro skill",
+        "May provide free-tool-specific context",
+        "Does not attempt full page CRO using free tool strategy patterns"
+      ],
+      "files": []
+    }
+  ]
+}