CtrlK
BlogDocsLog inGet started
Tessl Logo

tester

Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/tester/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, highly actionable skill body with executable commands and an explicit per-package decision table organized under clear headers. The only real gap is the absence of an explicit verify-results / on-failure checkpoint in the test-running workflow.

DimensionReasoningScore

Conciseness

The body is lean — short commands, minimal prose, no padding about what tests are — and the package lists earn their place as decision data; a few lists could be tightened or externalized, matching the 'efficient; minor instances that could be trimmed' 4-anchor rather than the perfectly lean 5-anchor.

4 / 5

Actionability

It gives copy-paste-ready commands ('yarn test packages/<package-name>', 'yarn test:os ...', a grep re-derivation command) plus an explicit per-package decision table, fully covering the common cases as the 5-anchor requires.

5 / 5

Workflow Clarity

The decision flow (identify package → check storageOps category → run the matching command) is clearly sequenced with a stated source of truth, but there is no explicit checkpoint for verifying test results or handling failures, matching the 4-anchor's 'clear sequence with minor validation gaps' rather than the feedback-loop 5-anchor.

4 / 5

Progressive Disclosure

Content is well-organized under clear ## sections with no nested references, and for a small single-purpose skill this is good structure; the inlined package lists are borderline material that could live in a reference file, keeping it at 'good structure, minor organization gaps' rather than the cleanly-split 5-anchor.

4 / 5

Total

17

/

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 concise, third-person description that covers both what the skill does and when to use it, with a natural trigger phrase. Its main limitation is narrow action coverage — it states the scope but lists few discrete capabilities.

Suggestions

Add one or two more concrete actions (e.g., 'selects the correct test command per package', 're-derives the package list from ci.config.json') to lift specificity toward the 5-anchor.

Broaden the trigger phrasing to include common variants users might say, such as 'running the test suite' or 'running unit/integration tests for a package'.

Tighten the 'when' clause to a more specific trigger, e.g. 'Use when the user asks to run tests for a single package in this repo'.

DimensionReasoningScore

Specificity

The description names the domain ('running tests') and two concrete scopes ('a single package', 'OpenSearch (ddb-os) tests'), but stops short of listing several specific actions, fitting the '1-2 concrete actions, not comprehensive' anchor rather than the 4-anchor's 'several specific actions'.

3 / 5

Completeness

It has an explicit 'Use when running tests' trigger (the 'when') and a clear 'what' ('Shows how to run tests for a single package, including OpenSearch (ddb-os) tests'), satisfying both halves; the 'when' is somewhat generic, matching the 4-anchor where the trigger could be more specific rather than the fully concrete 5-anchor.

4 / 5

Trigger Term Quality

'Use when running tests' supplies the natural phrase a user would actually say, giving good keyword coverage; a few natural variants (e.g. 'test suite', 'unit tests') are absent, which keeps it just below the comprehensive 5-anchor.

4 / 5

Distinctiveness Conflict Risk

The qualifiers 'single package' and 'OpenSearch (ddb-os)' carve a fairly distinct niche with only minor overlap risk against a generic run-tests skill, placing it at 'mostly distinct' rather than the broad 3-anchor or the minimal-conflict 5-anchor.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
webiny/webiny-js
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.