agentleFS
admdanielpaulinoadmdanielpaulino/claude-codes/conversion-ops/SKILL.md

conversion-ops

Skill1 starsChanged 7 months agoMITView on GitHub

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md. AI-powered conversion rate optimization: landing page audits, CRO scoring, survey segmentation, and lead magnet generation. Fetches a landing page and scores it across 8 conversion dimensions. No headless browser needed. Scoring dimensions (each 0–100): 1. Headline Clarity — Is the value prop obvious in <5 seconds? 2. CTA Visibility — Are CTAs prominent, contrasting, above…

  • Installs packages

3 other projects use a version of this, 1 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before/after suggestions for each issue

    line 69
  2. Distinctive:

    No API keys required. Both tools work with local analysis only.

    line 110
  3. Very specific:

    Weekly: Run cro_audit.py on your top landing pages to track CRO scores over time

    line 121
  4. Very specific:

    Post-survey: Run survey_lead_magnet.py to turn survey data into content strategy

    line 122

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Conversion Ops

Preamble (runs on skill start)

# Version check (silent if up to date)
python3 telemetry/version_check.py 2>/dev/null || true

# Telemetry opt-in (first run only, then remembers your choice)
python3 telemetry/telemetry_init.py 2>/dev/null || true

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md.


AI-powered conversion rate optimization: landing page audits, CRO scoring, survey segmentation, and lead magnet generation.

When to Use

  • User asks for a landing page audit or CRO analysis
  • User wants to score a page across conversion dimensions
  • User needs to identify conversion bottlenecks on a URL
  • User has survey data and wants to segment respondents by pain point
  • User wants lead magnet ideas generated from survey responses
  • User needs batch CRO analysis across multiple URLs

Tools

CRO Audit (cro_audit.py)

Fetches a landing page and scores it across 8 conversion dimensions. No headless browser needed.

# Single URL audit
python cro_audit.py --url https://example.com/landing-page

# Batch mode — multiple URLs
python cro_audit.py --urls https://example.com/page1 https://example.com/page2

# URLs from a file (one per line)
python cro_audit.py --file urls.txt

# Specify industry for benchmark comparison
python cro_audit.py --url https://example.com --industry saas

# JSON output
python cro_audit.py --url https://example.com --json

# Save report to file
python cro_audit.py --url https://example.com --output report.json

Scoring dimensions (each 0–100):

  1. Headline Clarity — Is the value prop obvious in <5 seconds?
  2. CTA Visibility — Are CTAs prominent, contrasting, above the fold?
  3. Social Proof — Testimonials, logos, case studies, numbers?
  4. Urgency — Scarcity, deadlines, limited offers?
  5. Trust Signals — Security badges, guarantees, privacy, certifications?
  6. Form Friction — How many fields? Is the form intimidating?
  7. Mobile Responsiveness — Viewport meta, responsive patterns, touch targets?
  8. Page Speed Indicators — Image optimization, script count, resource size?

Overall CRO Score = Weighted average across all 8 dimensions.

Output includes:

  • Per-dimension score with specific findings
  • Priority fixes ranked by impact
  • Before/after suggestions for each issue
  • Industry benchmark comparison
  • Overall letter grade (A+ through F)

Supported industries: saas, ecommerce, agency, finance, healthcare, education, b2b, general

Survey-to-Lead-Magnet Engine (survey_lead_magnet.py)

Ingests survey CSV data, clusters respondents by pain point, and generates lead magnet briefs for each segment.

# Basic usage — analyze survey CSV
python survey_lead_magnet.py --csv survey_responses.csv

# Specify which columns contain pain points / challenges
python survey_lead_magnet.py --csv survey.csv --pain-columns "biggest_challenge" "top_frustration"

# Limit number of segments
python survey_lead_magnet.py --csv survey.csv --top-segments 5

# JSON output
python survey_lead_magnet.py --csv survey.csv --json

# Save output
python survey_lead_magnet.py --csv survey.csv --output lead_magnets.json

What it produces:

  • Pain point clusters with respondent counts
  • Segments ranked by size and commercial potential
  • For each top segment, a lead magnet brief:
    • Title, format (guide/checklist/template/calculator), hook
    • Content outline (5–7 sections)
    • Target CTA and distribution channel
    • Viral potential score + conversion potential score
  • Prioritized implementation roadmap

CSV format: Questions as column headers, one respondent per row. Works with any survey tool export (Typeform, Google Forms, SurveyMonkey, etc.)

Configuration

No API keys required. Both tools work with local analysis only.

Optional environment variables:

VariableRequiredDescription
USER_AGENTNoCustom user agent for page fetching (default provided)
REQUEST_TIMEOUTNoHTTP timeout in seconds (default: 15)

Recommended Workflow

  1. Weekly: Run cro_audit.py on your top landing pages to track CRO scores over time
  2. Post-survey: Run survey_lead_magnet.py to turn survey data into content strategy
  3. Pre-launch: Audit new landing pages before driving paid traffic
  4. Monthly: Batch audit competitor landing pages to benchmark against

Dependencies

pip install -r requirements.txt

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.