CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

landing-optimizer

Use when the user asks to "optimize our landing page for influencer traffic", "fix our promo-code landing page", or "improve conversion from a creator campaign"; produces a message-match audit, page-structure and social-proof recommendations, a promo-code/CTA conversion plan, and an A/B test roadmap. Not for measuring campaign results after launch — use performance-analyzer. 落地页优化/达人流量转化提升

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A mature, highly operational skill body: an 8-step sequenced workflow with genuine validation checkpoints and failure paths, concrete per-step tactics, a worked example, and clean one-level-deep delegation of templates to a verified reference file. The only real weakness is token efficiency — the rights-gate compliance language is restated several times across the contract and steps.

Suggestions

State the creator-reuse gate requirements once (in the gate paragraph or a referenced block) and have steps 2, 4, 6, and 7 cite it with a one-line summary instead of re-enumerating the field list each time.

Trim the Skill Contract 'Reads'/'Done when' entries that duplicate the gate paragraph verbatim (e.g., the full rights-field list appears in both) — keep the contract to the read/write/promote/done shape and link to the gate for field-level detail.

Collapse the cross-discipline paid-ads note and the connectors list into the references section or templates.md so the body opens with the workflow rather than governance context.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is mostly operational, but the creator-reuse rights gate is enumerated in full or near-full detail at least three times (the gate paragraph, Skill Contract 'Reads'/'Done when', and again in steps 2, 4, 6, and 7), which could be consolidated into one referenced block. This fits 'mostly efficient but could be tightened' rather than level 2, since the repetition is safety-critical procedural content rather than padded explanations.

3 / 5

Actionability

Guidance is concrete and executable throughout: a fixed layout sequence ("hero → social proof → product → more proof → FAQ → final CTA"), specific promo-code mechanics ("auto-apply via URL param, prominent display, confirmation"), a Message Match Score (X/10) rubric, per-step UTM/event and metric definitions, and a full worked example covering a common case — with fill-in templates and HTML snippets one reference away. This matches the fully-executable anchor for an instruction-only skill; it is not level 4 because there are no meaningful gaps in the common-case coverage.

5 / 5

Workflow Clarity

Eight steps are clearly sequenced (assess → message match → structure → proof → conversion → testing → dedicated pages → tracking) with explicit validation checkpoints and feedback loops: the reuse gate is a literal checklist whose failure path returns NEEDS_INPUT and blocks copying/testing, step 2 defines Unknown/NEEDS_INPUT handling for missing approvals, and 'Done when' criteria gate completion. This matches the anchor with explicit validation steps and error-recovery loops, not merely 'most checkpoints' at level 4.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview that delegates all fill-in templates, ASCII layouts, HTML snippets, and the full worked example to references/templates.md — verified to exist (491 lines) with sections keyed by the same step numbers as promised — one level deep and clearly signaled. Cross-links (skill-contract.md, CONNECTORS.md, sibling skills) are also one level and clearly labeled, matching the clear-overview anchor rather than the minor-gaps anchor at 4.

5 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: explicit third-person 'what' and 'when', quoted natural trigger phrases with synonyms (including a Chinese variant), concrete deliverables, and an explicit not-for boundary pointing to the sibling skill. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

The description enumerates four concrete deliverables — "produces a message-match audit, page-structure and social-proof recommendations, a promo-code/CTA conversion plan, and an A/B test roadmap" — which comprehensively covers the skill's output surface, matching the anchor for multiple specific concrete actions with comprehensive coverage. It is not score 4 because there are no noticeable gaps in the action list for this domain.

5 / 5

Completeness

It explicitly answers 'what' (the audit, recommendations, conversion plan, and test roadmap it produces) and 'when' with an explicit "Use when the user asks to..." clause carrying three concrete trigger phrases, plus a negative boundary ("Not for measuring campaign results after launch — use performance-analyzer"). This matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases, not the merely-adequate level 4.

5 / 5

Trigger Term Quality

It quotes three literal natural-language user requests ("optimize our landing page for influencer traffic", "fix our promo-code landing page", "improve conversion from a creator campaign") plus synonyms (landing page, promo code, creator campaign, influencer traffic, conversion) and Chinese equivalents (落地页优化/达人流量转化提升), giving comprehensive natural-term coverage. It exceeds the 'good coverage, a few terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — influencer/creator-traffic landing page conversion — with triggers distinct from adjacent skills, and it explicitly disambiguates against performance-analyzer for post-launch measurement. Overlap risk is minimal, matching the clear-niche anchor rather than the minor-overlap anchor at 4.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 15 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/report/landing-optimizer/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.