Skills

cro-methodology

cro-methodology is a skill in wondelai/skills, last changed 30 Jun 2026. It can name web addresses. Our pattern check flagged nothing at commit c172996 on 27 Oct 2026.

Pattern check: nothing flagged · commit c172996 · 27 Oct 2026

Install
From the author
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "conversion funnel", "increase signups", or "people add to cart but dont buy". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Licence
MIT
Repo stars
2.5k
Folder last changed
30 Jun 2026 (opens in a new tab)
Publisher
wondelai
Files
7 files
Checked
c172996 (opens in a new tab) · 27 Oct 2026

Install

Each tab says whether it installs commit c172996, the one we checked, or the latest version.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.

Pinned to commit c172996, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/wondelai/skills.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin c172996495bed0fcd26896a9416b2093fd7073f0 &&
  git -C "$tmp" sparse-checkout set -- cro-methodology &&
  git -C "$tmp" checkout -q c172996495bed0fcd26896a9416b2093fd7073f0 &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/cro-methodology &&
  cp -R "$tmp"/cro-methodology/. .claude/skills/cro-methodology/ &&
  rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Or install the marketing-cro plugin it ships in. Installs the latest version, not the one we checked. Installs everything in the plugin, including any hooks, MCP servers and scripts our check doesn't cover.

claude plugin marketplace add wondelai/skills --scope project &&
  claude plugin install marketing-cro@wondelai-skills --scope project
Claude Code docs (opens in a new tab)

What it can touch

From the files and frontmatter at commit c172996. This is how much a skill can do, not whether it is risky.

What it can touch: Scripts or outside hosts

  • Names web addresses

    It mentions outside web addresses the agent may visit. We list them but don't follow them.

Pattern check

Pattern check: nothing flagged · commit c172996 · 27 Oct 2026

We checked every text file in this skill, at commit c172996 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Outside links we did not follow

  • https://www.amazon.com/Making-Websites-Win-Customer-Centric-Methodology/dp/1544500513?tag=wondelai00-20

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specPasses

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Note

      Reference files over 100 lines with no table of contents at the top: references/COPYWRITING.md (179 lines), references/OBJECTIONS.md (136 lines), references/PERSUASION.md (159 lines) and references/RESEARCH.md (221 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • Claude CodePasses

    Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

    • Note

      Reference files over 100 lines with no table of contents at the top: references/COPYWRITING.md (179 lines), references/OBJECTIONS.md (136 lines), references/PERSUASION.md (159 lines) and references/RESEARCH.md (221 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • Claude apps & API uploadPasses

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Note

      The description is 633 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

    • Note

      Reference files over 100 lines with no table of contents at the top: references/COPYWRITING.md (179 lines), references/OBJECTIONS.md (136 lines), references/PERSUASION.md (159 lines) and references/RESEARCH.md (221 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • OpenAI (Codex & API)Passes
  • VS Code & CopilotPasses

SKILL.md

Files

7 files

PathSize
SKILL.md (opens in a new tab)16.7 KB
references/COPYWRITING.md (opens in a new tab)3.9 KB
references/OBJECTIONS.md (opens in a new tab)3.9 KB
references/PERSUASION.md (opens in a new tab)3.8 KB
references/RESEARCH.md (opens in a new tab)5.2 KB
references/funnel-analysis.md (opens in a new tab)11 KB
references/testing-methodology.md (opens in a new tab)10 KB

More from wondelai/skills

  • 37signals-way

    wondelai/skills

    Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

    • Names web addresses
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 10 Sept 2026

  • architecture-optimization

    wondelai/skills

    Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 28 Aug 2026

  • blue-ocean-strategy

    wondelai/skills

    Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

    • Names web addresses
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 30 Jun 2026

  • clean-architecture

    wondelai/skills

    Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

    • Names web addresses
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 30 Jun 2026

  • clean-code

    wondelai/skills

    Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.

    • Runs shell commands
    • Names web addresses
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 30 Jun 2026

  • cold-start-problem

    wondelai/skills

    Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.

    • Names web addresses
    Pattern check: Nothing flagged

    MIT · 2.5k repo stars · Updated 30 Jun 2026

All skills in wondelai/skills