CtrlK
BlogDocsLog inGet started
Tessl Logo

cta-generator

Deprecated compatibility entry for Call to Action construction. This component is now maintained in Bricks; install and use component-builder to build a new Call to Action.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/components/conversion/cta/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

As a deprecation stub, the body does its one job flawlessly: it is a lean, fully executable redirect with an exact install command, a link to the successor, and an explicit statement that no component rules remain here. Judged against what is written, it is exemplary for its size and purpose.

DimensionReasoningScore

Conciseness

Every sentence earns its place: where the content moved, a copy-paste install command, and what to ask the agent. There is zero padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

The install command 'npx skills add kostja94/bricks --skill component-builder' is fully executable and copy-paste ready, and it covers the sole use case of this stub — redirecting to the maintained skill.

5 / 5

Workflow Clarity

This is a simple single-purpose skill and its single action is unambiguous: install the new skill, then ask the agent to use component-builder. Per the simple-skill guideline this scores 5; there is no destructive or batch operation requiring validation.

5 / 5

Progressive Disclosure

The body is under 50 lines, needs no external reference files (none exist in the bundle), is organized under a clear heading, and signals exactly one link to the successor reference — matching the guideline for short self-contained skills.

5 / 5

Total

20

/

20

Passed

Description

53%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 honest and specific about its deprecation status and the migration path, but it functions as a tombstone rather than a discoverable skill description: no trigger guidance and no 'CTA' synonym, so it would rarely be selected when a user needs it. It cannot answer 'when should Claude use this' at all.

Suggestions

Add a 'Use when...' trigger clause (e.g., 'Use when the user asks to build a Call to Action/CTA button') so the entry remains discoverable for the task it redirects.

Include the common abbreviation 'CTA' and related natural terms (button, banner) in the description to cover the phrases users actually say.

State upfront what the skill does today (redirects to component-builder) rather than only what it no longer does, so the 'what' is fully explicit.

DimensionReasoningScore

Specificity

The description names the domain ('Call to Action construction') and 1-2 concrete actions ('install and use component-builder to build a new Call to Action'), matching the anchor for domain plus a couple of concrete actions but not a comprehensive capability list.

3 / 5

Completeness

It clearly answers 'what' (a deprecated compatibility entry; CTAs are now built with component-builder) but contains no 'when to use' trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Call to Action construction' is a relevant natural term, but common variations users would actually say — 'CTA', 'button', 'Use when...' phrasing — are absent, matching the anchor for some relevant keywords missing common synonyms.

3 / 5

Distinctiveness Conflict Risk

'Call to Action construction' is a distinct niche and the description explicitly names its successor, so mis-triggers resolve correctly; not 5 because it intentionally overlaps the successor skill's own trigger space.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
kostja94/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.