CtrlK
BlogDocsLog inGet started
Tessl Logo

testing

Skill: testing

40

Quality

40%

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 ./templates/plate-playground-template/.agents/skills/testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 a concise, well-structured set of testing rules that assumes Claude's competence and gives specific actionable directives. Its main weakness is that it is a principles document rather than a sequenced workflow, so it lacks explicit validation checkpoints.

DimensionReasoningScore

Conciseness

The body is a lean set of terse bullets under clear headers (e.g. 'Assert public behavior, not implementation detail', 'Use `it.each` for small behavior matrices') with no padding or explanation of concepts Claude already knows, matching the score-5 'every token earns its place' anchor.

5 / 5

Actionability

Directives are concrete and specific (keep tests in '*.spec.ts[x]', prefer render-returned queries over 'screen', use direct style-property assertions instead of 'toHaveStyle'), but as an instruction-only rules skill it lacks copy-paste executable code, fitting score-4 'mostly executable guidance with minor gaps' rather than 5.

4 / 5

Workflow Clarity

The content is organized into topical sections but presents principles rather than a sequenced multi-step workflow, and there are no validation checkpoints for the mildly destructive rule 'Delete skipped, commented, or placeholder tests', matching the score-3 anchor of structure present but checkpoints missing.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is organized into clear well-labeled sections (Testing Goal, Core Rules, Seam Selection, Fixtures And Assertions, Quick Reference), meeting the guideline that simple skills with no external references can score 5 on well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

0%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 a placeholder label rather than a real skill description: it states no concrete capabilities and gives no usage trigger. It would neither help a user find the skill nor distinguish it from others.

Suggestions

Replace 'Skill: testing' with concrete actions the skill performs, e.g. 'Selects test seams, keeps suites fast, and structures fixtures for Bun + React'.

Add an explicit 'Use when...' clause naming natural trigger phrases (writing tests, choosing a test seam, speeding up the suite, structuring fixtures).

Avoid the generic word 'testing' alone; include specific terms like unit tests, component contract tests, golden tests, Bun, Testing Library so it is distinguishable from other testing skills.

DimensionReasoningScore

Specificity

The description is the literal label 'Skill: testing', which names no concrete actions and uses pure abstract language, matching the score-1 anchor 'Helps with documents'.

1 / 5

Completeness

It provides only an extremely vague 'what' (testing) and no 'when' trigger guidance at all, matching the score-1 anchor where both what and when are extremely vague or missing.

1 / 5

Trigger Term Quality

Only the single generic word 'testing' appears; there are no natural trigger phrases a user would say, so it fits the score-1 anchor of entirely generic language with no natural keywords.

1 / 5

Distinctiveness Conflict Risk

'Skill: testing' is entirely generic and would overlap with virtually any testing-related skill, matching the score-1 anchor for conflict with virtually any skill.

1 / 5

Total

4

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (14 chars), consider making it more detailed

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.