CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing-watchlist-ui

Guidance for testing the watchlist UI - covers test patterns, setup, and common issues.

Quality

65%

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 ./.agents/skills/testing-watchlist-ui/SKILL.md
SKILL.md
Quality
Evals
Security

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 a lean, well-organized checklist of testing guidance with a concrete tool choice and named test flows. Its weakness is executability: no commands, file locations, or examples for running tests and seeding data, and the test workflow is only implied rather than sequenced.

Suggestions

Add the concrete commands to run the test suite and seed test data (e.g. the Playwright invocation and the seed script/command) so the guidance is executable rather than descriptive.

Replace the redundant Overview sentence (which repeats the frontmatter description) with actionable detail, such as where test files live or how to target a single flow.

DimensionReasoningScore

Conciseness

The body is lean with no re-teaching of concepts Claude already knows; the only trimmable part is the Overview sentence ('This skill provides guidance for testing the Netrunner watchlist user interface.'), which mostly duplicates the frontmatter description. This matches anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than 5's 'every token earns its place'.

4 / 5

Actionability

There is concrete guidance — 'Use Playwright for end-to-end browser tests', 'Test watchlist creation, editing, and deletion flows', 'Ensure test data is seeded before running' — but no commands, file paths, or example code showing how to run the suite or seed data. This fits anchor 3 ('Some concrete guidance but incomplete; missing key details') and not 4, which requires concrete code or commands.

3 / 5

Workflow Clarity

A testing sequence is only implicit (seed data before running, then verify indicators/behavior), with no explicit step ordering or validation checkpoints. This matches anchor 3 ('sequence present but checkpoints missing or implicit'); it is above 2 because the bullets do convey rough ordering and what to verify, and no destructive/batch cap applies.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (no references/, scripts/, or assets/ directories exist), and its content is organized into clear sections (Overview, Test Patterns, Common Issues). Per the judging guideline for simple skills under 50 lines with no need for external references, this scores 5.

5 / 5

Total

15

/

20

Passed

Description

48%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 names a specific domain and its coverage areas but reads as a table of contents rather than an actionable, trigger-rich summary. Its main gaps are the absence of any 'when to use' guidance and of concrete action verbs describing what the skill actually does.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or running tests for the watchlist UI, or when the user mentions watchlist testing, E2E tests, or Playwright.'

Replace generic category nouns ('test patterns, setup, and common issues') with concrete actions, e.g. 'Run Playwright E2E tests for watchlist creation, editing, and deletion; seed test data; diagnose async timing issues.'

Include natural synonyms users might say (E2E, browser tests, frontend tests, Playwright) to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("testing the watchlist UI") and lists topical categories ("test patterns, setup, and common issues") but contains no concrete action verbs, matching the anchor 'Names the domain but actions are minimal or generic'. It falls below anchor 3, which requires 1-2 concrete actions like 'extracts content'.

2 / 5

Completeness

The 'what' is reasonably clear (guidance covering test patterns, setup, and common issues for the watchlist UI), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It does not fall to 2 because the 'what' is not vague.

3 / 5

Trigger Term Quality

'testing' and 'watchlist UI' are natural phrases a user would say, but common variations and synonyms ('E2E', 'Playwright', 'frontend tests', 'browser tests') are absent. This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'watchlist UI' is a distinct niche unlikely to trigger the wrong skill, with only minor overlap risk against generic testing skills — anchor 4. Not 5 because the description lacks explicit, concrete trigger phrases that would make the niche boundary unambiguous.

4 / 5

Total

12

/

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

pvnkmnk/djinn-netrunner

Path

.agents/skills/testing-watchlist-ui/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.