Agent skill · Audited from source
cro
skill · coreyhaines31/marketingskillsMIT licenceAudited 13 Nov 2026 · source 7c790cf75f39
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 7c790cf75f39 and found no filesystem, network or shell access and no hard-coded secrets. What it does: When the user wants more conversions from a page or form, or asks why a page isn't converting, what to change first, or whether to add or remove a field or element: landing and pricing pages, lead forms, or a URL shared…
Cite
Cite this page
ModelsAtlas. “cro (coreyhaines31/marketingskills)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/coreyhaines31/cro
Trust audit
Audit 0.4.1 · source read 13 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 1 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (1)
LOWInventory / provenanceinv.symlink · CLAUDE.md
CLAUDE.md
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha 7c790cf75f39 · 13 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercoreyhaines31 GitHub userOwner of the repository this skill is read from
- Source foldercoreyhaines31/marketingskills/skills/croThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict7c790cf75f39A new audit runs when the source changes
- Repository statusNot archivedLast push 1 day ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: When the user wants more conversions from a page or form, or asks why a page isn't converting, what to change first, or whether to add or remove a field or element: landing and pricing pages, lead forms, or a URL shared…
--- name: cro description: "When the user wants more conversions from a page or form, or asks why a page isn't converting, what to change first, or whether to add or remove a field or element: landing and pricing pages, lead forms, or a URL shared for feedback. For signup flows, see signup. For activation, see onboarding. For popups, see popups. For running the test, see ab-testing." metadata: version: 2.0.6 --- # Conversion Rate Optimization (CRO) You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates. ## Reference Routing Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations. | User intent | Load | Covers | |---|---|---| | Lead, contact, demo, or quote form abandonment; fields, validation, mobile forms | [form.md](references/form.md) | Field decisions, form layouts, errors, trust, measurement, and form-specific experiments | | Experiment ideas for a homepage, pricing, demo, landing, feature, or resource page | [experiments.md](references/experiments.md) | Hypotheses organized by page type and cross-page tests; use **ab-testing** for test design and measurement | ## 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) --- ## 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 --- ## Output Format Structure your 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. --- ## 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.
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 7c790cf
git clone https://github.com/coreyhaines31/marketingskills git -C marketingskills checkout 7c790cf75f39
The author documents no install command, so this uses the repository directly. Our verdict covers commit 7c790cf75f39 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
7c790cf75f39
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/coreyhaines31/cro/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
coreyhaines31/marketingskills
When the user wants to run or synthesize customer research, or asks what customer quotes, reviews, or feedback really mean, what is safe to conclude, and what to ask next: interviews, surveys, voice of customer,…
coreyhaines31/marketingskills
When the user wants to write or rewrite page copy (homepage, landing, pricing, feature), or asks which headline, promise, or message to lead with. Diagnoses the input first (blank brief, real voice, or point edit) and…
coreyhaines31/marketingskills
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog…
coreyhaines31/marketingskills
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,'…
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,'…
coreyhaines31/marketingskills
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand…
Add this badge to your README
[](https://modelsatlas.com/skills/coreyhaines31/cro/)
<a href="https://modelsatlas.com/skills/coreyhaines31/cro/"><img src="https://modelsatlas.com/skills/coreyhaines31/cro/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about cro
What does the cro skill do?
Is cro safe to install?
What can cro access on my machine?
How current is this page?
Sources
- github.com/coreyhaines31/marketingskills/tree/main/skills/cro — the audited source at commit 7c790cf75f39 and every finding aboveObserved · 13 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the cro skill do?
- Is cro safe to install?
- What can cro access on my machine?