goodbye-world

A simple test skill to verify the updated footer

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/goodbye-world/SKILL.md

Quality

Content

65%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 exceptionally lean and well-structured for a simple test skill, but its steps are too vague to be actionable and the verification step lacks any concrete check. It works as a smoke test but offers little executable guidance.

Suggestions

Make the steps concrete and executable: specify what 'say goodbye politely' should produce and how to confirm the footer (e.g., 'Verify the Discord link href and the feedback section text render in the footer').

Add an explicit verification checkpoint for step 2 describing what a correct footer looks like, so the check is unambiguous rather than a vague 'looks correct'.

If real validation tooling exists, reference it; otherwise state plainly that the check is manual visual inspection.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and no over-explanation of concepts Claude already knows; every line earns its place, matching anchor 5. Not 4 because there is nothing to trim.	5 / 5
Actionability	Steps are imperative ('Say goodbye politely', 'Confirm the review footer looks correct') but provide only high-level hints with no concrete, executable guidance, matching anchor 2. Not 1 because it instructs rather than merely describes; not 3 because there is no concrete executable detail.	2 / 5
Workflow Clarity	A clear two-step sequence is present, but the 'confirm' checkpoint is implicit and vague with no real validation step, matching anchor 3. Not 2 because the steps are not poorly defined with many gaps; not 4 because there are no explicit checkpoints or commands.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections ('When to use', 'Steps'), qualifying for the simple-skill exception at anchor 5. Not 4 because the structure is already appropriately organized for a skill of this size.	5 / 5
	Total	15 / 20 Passed

Description

28%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 too vague to drive reliable activation: it names a meta-test purpose but provides no concrete capabilities and no explicit trigger ('Use when...') guidance. It would rarely be selected for the right reason by a user.

Suggestions

Add an explicit 'Use when...' trigger clause stating the concrete situations that should activate this skill (e.g., 'Use when verifying that the skill review action footer renders correctly').

Replace 'verify the updated footer' with concrete actions the skill performs (e.g., 'Render the skill review footer and check the Discord link and feedback section display correctly').

Include natural user-facing trigger terms and synonyms so the skill matches what a user would actually say.

Dimension	Reasoning	Score
Specificity	Names the domain ('test skill') with one minimal action ('verify the updated footer'), matching anchor 2 where the domain is named but actions are minimal or generic. Not 1 because it does name a domain and an action; not 3 because it lacks 1-2 concrete actions with any coverage.	2 / 5
Completeness	A vague 'what' ('verify the updated footer') is present but there is no 'when'/trigger clause at all, matching anchor 2 and capped at 3 by the missing-'Use when' guideline. Not 1 because a 'what' is stated.	2 / 5
Trigger Term Quality	Only generic keywords ('test skill', 'verify', 'footer') are present, missing the natural phrases a user would actually say to invoke this skill. Not 1 because it is not pure technical jargon; not 3 because there are no clearly relevant real-domain keywords or synonyms.	2 / 5
Distinctiveness Conflict Risk	A narrow stated niche (footer-verification test) makes it somewhat specific, but the vague wording means it could still overlap with other test/meta skills, matching anchor 3. Not 4 because the triggers are not distinct enough to minimize overlap risk.	3 / 5
	Total	9 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: popey/test-tessl-review-skill
Path: skills/goodbye-world/SKILL.md
Commit: d7b503a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.