CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

surge-landing

Use when asked to design growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures. Examples: "growth-optimized landing", "activation funnel layout", "A/B testable page"

Quality

75%

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 ./plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-landing/SKILL.md
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.

A lean, actionable body with exact search commands, a concrete output template, and a clear five-step sequence. Its one real defect is a broken progressive-disclosure chain: the referenced docs/output-kit.md and /atlas-report are absent from the bundle, so the output-format and delivery instructions cannot be followed as written.

Suggestions

Fix the dangling reference: either include docs/output-kit.md in the bundle (with the 40-line CLI budget, box-drawing skeleton, and severity indicators it promises) or inline that format spec directly and drop the reference.

Document or inline the '/atlas-report' delivery mechanism — as written, the Delivery section depends on a skill that is neither bundled nor explained, leaving the overflow path unusable.

Add a brief failure-handling note to the workflow (e.g., what to do when a surge_agent search returns no results) to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

The body is tight — three exact commands, a terse output template, and four one-line anti-patterns with no explanations of concepts Claude already knows — though the 'When to use' section restates the frontmatter description and the box-drawing template spends tokens on alignment characters.

4 / 5

Actionability

Commands like 'python3 -m surge_agent.uiux search --domain landing --query "{product_type}" --limit 3' are copy-paste ready and the output skeleton is concrete, but there is no worked example of a filled-in output and step 5 ('Output experiment-friendly structure...') gestures at the template rather than demonstrating it.

4 / 5

Workflow Clarity

Five clearly sequenced steps each carry a concrete command, and the workflow is non-destructive so heavy validation is unwarranted; the minor gap is no handling of failure cases such as empty search results, which keeps it below anchor 5.

4 / 5

Progressive Disclosure

Sections are well-organized, but the pivotal reference 'Follow the output format defined in docs/output-kit.md' points to a file that does not exist in the bundle, and the '/atlas-report' dependency is similarly undocumented, leaving the navigation chain broken.

3 / 5

Total

15

/

20

Passed

Description

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

A solid description with an explicit 'Use when' clause and quoted trigger examples that anchor both timing and distinctiveness. Its main weakness is a thin capability statement — a single 'design' verb — that undersells what the skill actually produces.

DimensionReasoningScore

Specificity

The description names the domain and concrete objects ('growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures') but rests on a single action verb ('design'), so it does not list several specific actions as anchor 4 requires.

3 / 5

Completeness

The 'when' is explicit ('Use when asked to...') with concrete trigger examples, but the 'what' is thin — only 'design' is stated, with no mention of the skill's actual outputs (funnel structure, friction audit, experiment surfaces) that anchor 5's comprehensive what-plus-when requires.

4 / 5

Trigger Term Quality

Explicit quoted triggers ('growth-optimized landing', 'activation funnel layout', 'A/B testable page') give good, plausible keyword coverage, though common variations like 'landing page design', 'conversion', or 'A/B testing' are missing and 'A/B testable page' is phrasing users would not naturally say verbatim.

4 / 5

Distinctiveness Conflict Risk

Growth-optimized landing pages with 'activation funnel' and 'A/B testable' triggers form a clear niche distinct from general skills, with only minor overlap risk against generic web-design or frontend page-design skills.

4 / 5

Total

15

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-landing/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.