CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pitch-landing

Use when asked to structure a landing page for positioning, plan a conversion-optimized page layout, or design a launch page. Examples: "landing page for product launch", "conversion-optimized layout for SaaS"

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/marketing-team/skills/pitch-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, well-structured instruction body with concrete commands and a precise output template. Its weaknesses are a dangling reference to the missing docs/output-kit.md, absent validation/feedback steps in the workflow, and abstract final workflow steps.

Suggestions

Fix the dangling reference: either bundle docs/output-kit.md or inline the essential output-format rules so the mandated format is fully resolvable.

Add a validation or fallback step for the search commands (e.g., what to do when a query returns zero results) to strengthen the workflow's feedback loop.

Make steps 4-5 concrete by specifying how to select CTA strategy, social proof placement, and objection handling from the search results rather than directing abstractly to "layer in positioning".

DimensionReasoningScore

Conciseness

The body is dense with no explanations of concepts Claude already knows, but the "When to use" section restates the frontmatter description and CTA/social-proof/objection handling appears redundantly in both workflow step 4 and the output template, leaving minor trimming opportunities short of anchor 5.

4 / 5

Actionability

Two executable search commands and a complete output template give mostly concrete guidance, but steps 4 ("Layer in positioning") and 5 remain abstract direction, so coverage is not the fully executable, common-case-complete guidance of anchor 5.

4 / 5

Workflow Clarity

A clear five-step sequence with commands embedded in order and no destructive/batch cap applying; however there are no validation checkpoints or feedback loops (e.g., no guidance when a search returns zero results), which anchor 5 requires.

4 / 5

Progressive Disclosure

Sections are well organized for a ~50-line skill, but the opening instruction "Follow the output format defined in docs/output-kit.md" references a file absent from the bundle, a dangling core reference that is more than the minor organization gap of anchor 4 and leaves the mandated format partly unresolvable.

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 focused, trigger-rich description with good natural phrasing and example prompts. Its main weakness is that the "what" is only implicit in restated trigger verbs and keyword coverage omits a few common synonyms.

Suggestions

Add a standalone third-person capability statement (e.g., "Structures launch landing pages with section ordering, CTA strategy, social proof placement, and objection handling") before the Use-when clause.

Broaden trigger synonyms to include terms users naturally say such as "homepage", "sales page", "marketing page", or "one-pager".

DimensionReasoningScore

Specificity

Names the landing-page domain with concrete verbs ("structure a landing page for positioning", "plan a conversion-optimized page layout", "design a launch page"), but the three actions are restatements of a single capability rather than the several distinct actions anchor 4 expects.

3 / 5

Completeness

Has an explicit "Use when" clause with concrete trigger phrases, but the "what" is only embedded in the trigger verbs with no standalone capability statement, falling short of anchor 5's clearly separated what-and-when structure.

4 / 5

Trigger Term Quality

Includes natural user phrasings — "landing page", "product launch", "conversion-optimized layout", "SaaS" — with quoted example prompts, but misses common synonyms like "homepage", "sales page", or "marketing page" that anchor 5's comprehensive coverage would require.

4 / 5

Distinctiveness Conflict Risk

The positioning/conversion landing-page niche with specific quoted triggers is mostly distinct, with only minor overlap risk against general web-design or copywriting 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/marketing-team/skills/pitch-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.