CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cro-expert-kit

Elite Conversion Rate Optimization Toolkit.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/cro-expert-kit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized but shallow checklist of standard CRO principles. Its main structural claims fail against the real bundle — the referenced knowledge module is missing and the bundled script is orphaned — and the execution protocol lacks the concrete steps, templates, and feedback loops needed to be genuinely actionable.

Suggestions

Fix the bundle mismatch: either create sub-skills/psychological_triggers.md or remove the 'Knowledge Modules' section, and add a reference to the actually-bundled scripts/conversion_calc.js (e.g. '## ROI calculator: node scripts/conversion_calc.js <spend> <conv%> <revenue-per-sale>') so the script is discoverable.

Make the Execution Protocol executable: add a worked example hypothesis, a concrete A/B test setup template (variants, primary metric, sample size/MDE, duration), and a feedback loop step for iterating on failed tests.

Add at least one concrete before/after example per section (e.g. actual micro-copy rewrites, a real decoy-priced tier table) so the principles translate into specific output rather than high-level hints.

DimensionReasoningScore

Conciseness

The body is compact one-line bullets rather than padded prose, but much of it restates CRO concepts Claude already knows (social proof, decoy effect, multi-step forms, micro-copy, empty states), and taglines like '*Turning visitors into leads.*' and 'Celebrate small wins to build dopamine and habit loops' are unnecessary padding. It could be tightened by cutting the known-concept restatements to focus on the kit's own frameworks and protocol.

3 / 5

Actionability

The guidance is instruction-only but stays at the level of high-level hints — 'Use the Decoy Effect (Anchor pricing)', 'Remove non-essential fields', 'Display SSL certificates' — with no concrete examples of application, no worked hypothesis, no sample test plan, and the only executable artifact (scripts/conversion_calc.js) is never referenced. This matches 'Minimal concrete guidance; high-level hints but missing the specific steps to execute' rather than score 3, which would require at least incomplete-but-present concrete steps or templates.

2 / 5

Workflow Clarity

The Execution Protocol gives a clear 4-phase sequence (Diagnosis, Hypothesis, Design, Validation) and Phase 4 does mention 'an A/B test setup with clear success criteria', so a sequence exists. But the phases are one-line abstractions with no checkpoints during execution and no feedback loop — nothing says what to do with failed test results or how to iterate, leaving it at 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Scored against the actual bundle: the body's only reference, './sub-skills/psychological_triggers.md', points to a file that does not exist (there is no sub-skills/ directory), while the one real bundle file, scripts/conversion_calc.js, is never mentioned anywhere in SKILL.md. So the on-paper structure (menu + sectioned bullets) is undermined by a broken link that strands the sole 'Knowledge Module' and leaves the actual bundled script undiscoverable — minimal effective structure for navigating the real bundle.

2 / 5

Total

10

/

20

Passed

Description

36%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a five-word marketing label rather than a capability statement. It names the CRO domain but omits all concrete actions, all trigger guidance ('Use when...'), and all natural synonyms, relying on the reader to guess what the toolkit contains.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when optimizing landing pages, signup funnels, checkout flows, or paywalls, or when the user mentions conversion rates, CRO, or A/B testing.'

Replace 'Toolkit' with the actual capabilities: e.g. 'Diagnoses conversion drop-offs, applies CRO frameworks (LIFT, progressive profiling, decoy pricing), and proposes A/B test hypotheses for landing pages, signup flows, forms, and paywalls.'

Include natural synonyms and variations users would say — 'CRO', 'conversion rate', 'A/B testing', 'landing page optimization' — to improve trigger matching.

Drop the subjective fluff word 'Elite', which adds no information and is penalized as buzzword padding.

DimensionReasoningScore

Specificity

The description 'Elite Conversion Rate Optimization Toolkit.' names the domain (conversion rate optimization) but lists zero concrete actions — 'Toolkit' is generic and 'Elite' is pure marketing fluff. It does not fall to score 1 because, unlike 'Helps with documents', it does name a specific domain rather than being entirely abstract.

2 / 5

Completeness

The 'what' is vague (a 'Toolkit' — it never says what it actually does) and the 'when' is entirely absent, matching the anchor 'Has a vague what and no when'. The judging guideline caps completeness at 3 for a missing 'Use when...' clause, and here even the 'what' fails to describe any action.

2 / 5

Trigger Term Quality

'Conversion Rate Optimization' is a relevant keyword a user might plausibly say, so it rises above generic one-word keywords. However, common variations and synonyms are missing: 'CRO', 'A/B testing', 'landing page optimization', 'increase conversions', 'checkout optimization'.

3 / 5

Distinctiveness Conflict Risk

The CRO domain itself is a recognizable niche, but the word 'Toolkit' adds breadth and it could overlap with general marketing, growth, analytics, or landing-page skills. It does not reach 4 because without any trigger phrases or listed capabilities there is nothing to distinguish it from closely related marketing skills.

3 / 5

Total

10

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI

Path

.agent/skills/cro-expert-kit/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.