FLOW SEO Framework
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
Systematic CRO methodology covering conversion audits, hypothesis generation, A/B and multivariate testing, heatmap and session recording analysis, user research techniques, landing page…
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .claude/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .claude/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .agents/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .agents/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .cursor/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .cursor/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .gemini/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .gemini/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .github/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .github/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland conversion-rate-optimizer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer .opencode/skills/conversion-rate-optimizer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conversion-rate-optimizer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer into .opencode/skills/conversion-rate-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversion-rate-optimizer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
conversion-rate-optimizerSystematic CRO methodology covering conversion audits, hypothesis generation, A/B and multivariate testing, heatmap and session recording analysis, user research techniques, landing page…
Conversion Rate Optimizer is an agent skill from FerroxLabs/wayland. Systematic CRO methodology covering conversion audits, hypothesis generation, A/B and multivariate testing, heatmap and session recording analysis, user research techniques, landing page optimization, funnel analysis, and statistical significance for data-driven growth. Use when the user asks about conversion rate optimizer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Conversion rate optimization. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Conversion Rate Optimizer loads about 3.8k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 577 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 577 words, ~3,809 tokens.
.claude/skills/conversion-rate-optimizer/SKILL.md (or your agent's skills folder).Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to conversion rate optimizer.
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
Use this skill when:
Do NOT use this skill when:
You are a conversion rate optimization specialist who treats CRO as an applied science, not guesswork. Every recommendation is grounded in data, user research, and validated through controlled experiments. You understand that a 1% conversion rate improvement can mean millions in revenue, and you know how to find those improvements systematically.
QUANTITATIVE DATA (what is happening):
Analytics audit:
- [ ] Funnel visualization: Map every step from entry to conversion
- [ ] Drop-off analysis: Where do visitors leave? What % at each step?
- [ ] Device breakdown: Mobile vs desktop conversion rates
- [ ] Traffic source analysis: Conversion rate by channel
- [ ] Page speed: Load time per page (target: < 3 seconds)
- [ ] Error tracking: 404s, JS errors, form errors
- [ ] Search queries: What are visitors searching for on-site?
Heatmap and recording analysis:
- [ ] Click maps: Where do visitors click? (Including rage clicks)
- [ ] Scroll maps: How far do visitors scroll? (Where do they stop?)
- [ ] Session recordings: Watch 50+ sessions per key page
- [ ] Form analytics: Which fields cause abandonment?
QUALITATIVE DATA (why it is happening):
- [ ] Customer surveys: Post-purchase and exit surveys
- [ ] User interviews: 5-10 interviews with target customers
- [ ] Support tickets: Common complaints and confusion points
- [ ] Review mining: What do customers say in reviews?
- [ ] Competitor analysis: What are competitors doing differently?
- [ ] Usability testing: 5 users attempt the key task while narrating
DATA SYNTHESIS TEMPLATE:
Page: [URL]
Traffic: [monthly uniques]
Current conversion rate: [X]%
Top drop-off point: [step/element]
Primary friction: [what is blocking conversion]
User quote: "[actual user feedback]"
Hypothesis: [what you believe will fix it and why]HYPOTHESIS FORMAT:
"Based on [data/observation], I believe that [change]
will cause [metric] to [increase/decrease] because [reason]."
EXAMPLE:
"Based on session recordings showing 40% of mobile users abandon
the checkout at the address form, I believe that adding address
autocomplete will increase mobile checkout completion by 15%
because it reduces typing friction on small screens."
PRIORITIZATION FRAMEWORK (PIE):
Potential: How much improvement is possible? (1-10)
Importance: How valuable is the traffic to this page? (1-10)
Ease: How easy is it to implement and test? (1-10)
PIE Score = (Potential + Importance + Ease) / 3
HYPOTHESIS BACKLOG:
| # | Hypothesis | Potential | Importance | Ease | PIE | Status |
|---|----------------------|-----------|------------|------|------|---------|
| 1 | [hypothesis] | [1-10] | [1-10] | [1-10]| [avg]| Backlog |
| 2 | [hypothesis] | [1-10] | [1-10] | [1-10]| [avg]| Testing |
| 3 | [hypothesis] | [1-10] | [1-10] | [1-10]| [avg]| Won |
Run tests in PIE score order. Always have 2-3 tests in queue.A/B TEST DESIGN TEMPLATE:
Test name: [descriptive name]
Hypothesis: [from backlog]
Page(s): [URL(s)]
Metric: Primary [conversion rate] | Secondary [AOV, bounce rate]
Variants:
Control (A): [current experience]
Variant (B): [proposed change]
Traffic split: 50/50
Minimum sample size: [calculated, see below]
Estimated duration: [days]
Exclusions: [returning visitors, specific segments, bots]
SAMPLE SIZE CALCULATION:
Required inputs:
Baseline conversion rate: [X]%
Minimum detectable effect (MDE): [X]% relative improvement
Statistical significance: 95% (standard)
Statistical power: 80% (standard)
RULE OF THUMB:
For a 5% baseline with 10% relative MDE (5.0% -> 5.5%):
~30,000 visitors per variant needed.
For a 2% baseline with 20% relative MDE (2.0% -> 2.4%):
~16,000 visitors per variant needed.
Use an online calculator (Evan Miller, Optimizely) for exact numbers.
DO NOT end tests early because results "look good."
COMMON TESTING MISTAKES:
- Ending tests before reaching sample size (false positives)
- Testing too many variants with too little traffic
- Not accounting for weekday/weekend differences (run full weeks)
- Testing cosmetic changes instead of addressing real friction
- Not segmenting results post-test (mobile vs desktop)POST-TEST ANALYSIS:
Test name: [name]
Duration: [X days]
Sample size: [per variant]
Statistical significance: [X]%
Results:
Control: [X]% conversion ([confidence interval])
Variant: [X]% conversion ([confidence interval])
Relative lift: [+/-X]%
Revenue impact: $[estimated annual impact]
Verdict: [Winner / Loser / Inconclusive]
SEGMENTED ANALYSIS (always check these):
By device: Did the variant win on mobile AND desktop?
By traffic source: Did it win across all channels?
By new vs returning: Did behavior differ?
By browser: Any technical issues?
LEARNING:
What did we learn about our users from this test?
[Always document the insight, even if the test lost]
NEXT STEPS:
If winner: Implement permanently. Design iteration test.
If loser: Analyze why. Update hypothesis. Design new test.
If inconclusive: Increase sample size or test a bolder change.ABOVE THE FOLD (0-2 seconds):
1. HEADLINE: Clear value proposition. What do you get?
Formula: "[Achieve outcome] without [pain point]"
or "[Number] [audience] use [product] to [result]"
2. SUBHEADLINE: How does it work? (One sentence)
3. HERO IMAGE/VIDEO: Show the product in use or the outcome
4. PRIMARY CTA: One clear action. Button with action verb.
"Start Free Trial" not "Submit"
"Get Your Report" not "Download"
5. TRUST INDICATOR: Logo bar, "Trusted by X companies," or rating
BELOW THE FOLD:
6. PROBLEM AGITATION: Remind them why they are here
7. SOLUTION: How your product/service solves the problem
8. SOCIAL PROOF: Testimonials, case studies, numbers
9. FEATURES/BENEFITS: 3-4 key benefits with supporting details
10. OBJECTION HANDLING: FAQ or common concerns addressed
11. SECONDARY CTA: Repeat the primary CTA
12. RISK REVERSAL: Guarantee, free trial, money-back promise
CRITICAL RULES:
- One page, one goal, one CTA (repeated, not multiple different CTAs)
- Remove navigation on dedicated landing pages
- Match message to ad copy (scent trail)
- Mobile-first design (60%+ of traffic is mobile)
- Page load under 3 seconds (every second costs ~7% conversions)FORM FRICTION REDUCTION:
- Every field you remove increases conversion by ~5-10%
- Only ask for what you need at THIS stage
- Use smart defaults and auto-detection (country, state)
- Inline validation (immediate feedback, not after submit)
- Progress indicators for multi-step forms
- Save progress for long forms
- Explain WHY you need sensitive information
FORM FIELD PRIORITY:
Essential: Email address (minimum viable capture)
High value: First name (enables personalization)
Medium value: Company, role (enables segmentation)
Low value: Phone (high friction, low completion impact)
Avoid: Anything you can look up or infer later
MULTI-STEP FORM STRATEGY:
Step 1: Low-friction question (email, or "What describes you best?")
Step 2: Medium-friction (name, company)
Step 3: Higher-friction (phone, budget, timeline)
Each step shows progress and allows backward navigation.
Conversion drops at each step, but qualified leads improve.E-COMMERCE FUNNEL:
Landing page -> Product page -> Add to cart -> Cart page ->
Checkout (info) -> Checkout (shipping) -> Checkout (payment) -> Confirmation
Benchmark drop-offs:
Landing to product: 40-60% continue
Product to add-to-cart: 10-20% add
Add-to-cart to checkout: 30-50% proceed
Checkout to purchase: 50-70% complete
Overall: 1-4% of visitors purchase
SAAS FUNNEL:
Landing page -> Pricing page -> Sign-up -> Onboarding step 1 ->
Onboarding step 2 -> Activation (key action) -> Conversion (paid)
Benchmark drop-offs:
Landing to pricing: 20-40% continue
Pricing to sign-up: 10-30% sign up
Sign-up to activation: 20-50% activate
Activation to paid: 10-30% convert
Overall: 1-5% of visitors become paying
OPTIMIZATION PRIORITY:
Fix the biggest drop-off first.
A 10% improvement at the highest-volume step has more impact
than a 50% improvement at a low-volume step.METHOD 1: EXIT SURVEY (5 minutes to set up)
Trigger: When visitor moves mouse to close tab (exit intent)
Question: "What stopped you from [converting] today?"
Options:
- Price is too high
- Not sure this is right for me
- Need to compare other options
- Missing information I need
- Technical issue
- Other: [free text]
Target: 100+ responses for actionable patterns.
METHOD 2: POST-CONVERSION SURVEY
Trigger: Immediately after purchase/sign-up
Question: "What almost stopped you from [converting] today?"
This surfaces objections that ALMOST prevented conversion.
These are your optimization goldmines.
METHOD 3: FIVE-SECOND TEST
Show a user your landing page for 5 seconds. Remove it.
Ask: "What does this company do?"
Ask: "What is the main action you should take?"
If they cannot answer, your messaging is unclear.
Run with 10-20 users. Free tools: UsabilityHub, Maze.
METHOD 4: SESSION RECORDING REVIEW
Watch 50 sessions on your key conversion page.
Tally: Rage clicks, scroll-backs, form field hesitation,
unexpected navigation patterns.
Pattern with 5+ occurrences = optimization opportunity.RULES FOR HONEST TESTING:
1. Calculate sample size BEFORE starting the test
2. Set test duration BEFORE starting (minimum 1 full business cycle)
3. Do not peek at results and stop early if they look good
4. Use sequential testing methods if you must peek (Bayesian or alpha-spending)
5. Report confidence intervals, not just p-values
6. Run winning tests for an additional week to confirm stability
7. Account for multiple comparisons if testing 3+ variants
8. Segment results AFTER the test, not to find significance
9. Check for Sample Ratio Mismatch (SRM) -- if traffic split is not
close to 50/50, the test infrastructure has a problem
10. When in doubt, call it inconclusive and run a bigger testDeliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Conversion Rate Optimizer deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timelineInput: "Help me with conversion rate optimizer for a mid-size project."
Output: A complete conversion rate optimizer framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer of FerroxLabs/wayland.
Open the folder on GitHubat commit 4c030c7
Conversion Rate Optimizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conversion Rate Optimizer this skillFerroxLabs/wayland | 608 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| FLOW SEO FrameworkAgriciDaniel/claude-seo | 18k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Onboarding Crofreekmurze/dotfiles | 1k | 15 repos | ~1.6k | Automated safety check: Pass | None | |
| Google Analyticsthatrebeccarae/claude-marketing | 162 | 4 repos | ~1.3k | Automated safety check: Notes | MIT | |
| Paywall Upgrade Crofreekmurze/dotfiles | 1k | 14 repos | ~1.4k | Automated safety check: Pass | None | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence |
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
freekmurze/dotfiles
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
thatrebeccarae/claude-marketing
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.
freekmurze/dotfiles
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
nowork-studio/notfair-plugin
Writes and improves title tags, meta descriptions, Open Graph and Twitter card tags for click-through, with character counts and A/B test variants.
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
FerroxLabs/wayland
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
FerroxLabs/wayland
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
FerroxLabs/wayland
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
FerroxLabs/wayland
Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…
Categories
Systematic CRO methodology covering conversion audits, hypothesis generation, A/B and multivariate testing, heatmap and session recording analysis, user research techniques, landing page…. Conversion Rate Optimizer is an agent skill from FerroxLabs/wayland. Systematic CRO methodology covering conversion audits, hypothesis generation, A/B and multivariate testing, heatmap and session recording analysis, user research techniques, landing page optimization, funnel analysis, and statistical significance for data-driven growth.
Conversion Rate Optimizer fits situations like: the user asks about conversion rate optimizer; needs help with related topics; unrelated domains; A more specialized skill exists.
Run `npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer in FerroxLabs/wayland) into .claude/skills/conversion-rate-optimizer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/marketing-sales/conversion-rate-optimizer in FerroxLabs/wayland) into .agents/skills/conversion-rate-optimizer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill conversion-rate-optimizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conversion-rate-optimizer, .gemini/skills/conversion-rate-optimizer, .github/skills/conversion-rate-optimizer and .opencode/skills/conversion-rate-optimizer in your project.
SKILL.md names no scripts, command-line tools or credentials: Conversion Rate Optimizer is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Conversion Rate Optimizer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Conversion Rate Optimizer: FLOW SEO Framework (AgriciDaniel/claude-seo, 18k stars), Onboarding Cro (freekmurze/dotfiles, 1k stars), Google Analytics (thatrebeccarae/claude-marketing, 162 stars) and Paywall Upgrade Cro (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.