CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

signup

When the user wants better signup, registration, and trial start flows, or asks which fields or steps to cut or whether to require a card: SSO and drop-off before an account exists. For what happens after signup, see onboarding. For lead forms that don't create an account, see cro.

Quality

75%

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/signup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured advisory skill with genuinely actionable per-field guidance, pattern libraries, and a clear assess-then-recommend workflow gated on context gathering. Its weaknesses are length — duplicated sections and generic UX knowledge Claude already has — and the absence of any progressive disclosure, with reference-worthy material inlined in SKILL.md.

Suggestions

Merge 'Task-Specific Questions' into 'Initial Assessment' — the two sections ask nearly identical questions — and drop the 'Related Skills' section since the frontmatter description already states the onboarding/cro boundaries.

Move the Experiment Ideas section (~80 lines) to references/experiments.md and keep a one-line pointer in SKILL.md, shortening the always-loaded body.

Trim widely-known UX best practices (e.g., 'Use smart defaults', 'Pre-fill when possible', 'Allow paste (don't disable)') down to the non-obvious guidance specific to signup flows, so every remaining token earns its place.

DimensionReasoningScore

Conciseness

The body is dense operational bullets with no conceptual padding, but it could be tightened significantly: 'Task-Specific Questions' nearly duplicates 'Initial Assessment', 'Related Skills' repeats the description's boundaries, and long stretches restate widely-known UX best practices ('Use smart defaults', 'Allow paste').

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: a field-priority taxonomy, a worked typo example ('gmial.com → gmail.com'), named pattern flows per business type, defined metrics, and a structured Output Format (Issue/Impact/Fix/Priority). It falls short of 5 only in lacking worked examples or benchmark numbers.

4 / 5

Workflow Clarity

A clear gated sequence exists — check product-marketing context first, 'Before providing recommendations, understand:' flow type/current state/constraints, then emit a defined deliverable format — with the assessment questions acting as an explicit checkpoint. Minor gap: no feedback or verification loop after recommendations are produced.

4 / 5

Progressive Disclosure

No bundle files exist and all ~360 lines are inline. Section headers keep it navigable, but the ~80-line Experiment Ideas section and Common Patterns are natural candidates for separate reference files, and the only reference is an external GitHub URL rather than bundled material.

3 / 5

Total

14

/

20

Passed

Description

73%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 strong trigger-focused description with explicit boundary guidance against onboarding and cro. Its main weakness is that the 'what' — what the skill actually does — is only implicit in the when-clause, with no stated capabilities like auditing fields or recommending flow changes.

DimensionReasoningScore

Specificity

Concrete trigger scenarios are present ('which fields or steps to cut', 'whether to require a card', 'SSO', 'drop-off before an account exists'), but they describe when the skill applies rather than actions it performs, so coverage of capabilities is incomplete.

3 / 5

Completeness

The 'when' is explicit and specific ('When the user wants better signup... or asks which fields or steps to cut'), and a 'what' is inferable from 'better signup, registration, and trial start flows', but the skill's actual actions are never explicitly stated, holding it below a 5.

4 / 5

Trigger Term Quality

Natural phrases a user would say are well covered ('signup', 'registration', 'trial start', 'require a card', 'SSO', 'drop-off') with synonyms, though a few common variants like 'account creation' or 'sign-up form' are missing.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear pre-account-creation niche and explicitly disambiguates the two most likely collisions ('For what happens after signup, see onboarding. For lead forms that don't create an account, see cro.'), giving minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/signup/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.