CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 落地页优化/达人流量转化提升

68

Quality

85%

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

71%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-structured, actionable workflow with strong progressive disclosure and clear validation gates. The main weakness is conciseness: the compliance reuse-gate is repeated verbatim across many sections rather than defined once and referenced.

Suggestions

Define the creator-reuse gate once (e.g., in the Skill Contract) and reference it from each step instead of restating the full conditions five times.

Make the NEEDS_INPUT feedback loop explicit as a labeled checkpoint (e.g., a short "On blocked reuse" sub-step) rather than embedding it in prose.

Move the duplicated opaque-ref persistence rules (Skill Contract Writes vs. the return paragraph) into a single canonical statement to trim the closing sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explaining what a landing page is), but the creator-reuse gate is restated near-verbatim across the Skill Contract, Instructions intro, Steps 2/4/6/7, and the return paragraph — repetition that could be tightened to a single referenced definition.

3 / 5

Actionability

Concrete specifics throughout — the named layout (hero → social proof → product → more proof → FAQ → final CTA), promo mechanics (auto-apply via URL param, prominent display, confirmation), and target/UTM lists — with fill-in templates offloaded to references/templates.md; minor gaps as the executable templates live in the bundle.

4 / 5

Workflow Clarity

Eight numbered steps are clearly sequenced with explicit checkpoints (the reuse gate, NEEDS_INPUT gates, and a "Done when" checklist); the feedback loop on blocked reuse (return NEEDS_INPUT, do not copy/publish/test, still audit non-creator elements) is present but somewhat implicit.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled one-level-deep references (references/templates.md keyed by step number, plus skill-contract.md, state-model.md, CONNECTORS.md, and sibling skills), and the bulky templates are appropriately split into the bundle file.

5 / 5

Total

16

/

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.

The description is exemplary: concrete deliverables, natural quoted trigger phrases, explicit what/when structure, and a clear conflict boundary. It is concise without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "produces a message-match audit, page-structure and social-proof recommendations, a promo-code/CTA conversion plan, and an A/B test roadmap" — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (the four deliverables) and when ("Use when the user asks to ..." with three concrete trigger phrases), plus an explicit not-for boundary.

5 / 5

Trigger Term Quality

Quotes natural user phrases ("optimize our landing page for influencer traffic", "fix our promo-code landing page", "improve conversion from a creator campaign") with strong coverage of how users actually request this.

5 / 5

Distinctiveness Conflict Risk

Niche is clearly scoped to influencer/creator landing pages with distinct triggers and an explicit hand-off boundary ("Not for measuring campaign results after launch — use performance-analyzer"), minimizing conflict risk.

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.

Validation13 / 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
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.