CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing

Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or fixing linting issues.

Quality

66%

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

Quality

Content

57%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 highly actionable for this repo, with copy-paste commands and concrete, repo-specific test patterns that Claude could not infer. Its weaknesses are dated free-floating notes, padding with basic Jest/RTL/ESLint knowledge Claude already has, no validation/error-recovery checkpoints in the test workflows, and a monolithic structure that inlines pattern libraries instead of splitting them into reference files.

Suggestions

Add validation checkpoints to the test workflows, e.g. 'Before integration tests: verify services with `./dev.sh up` then check `docker compose ps`; if unit tests fail, run `npm run lint:fix` before re-running.'

Move the E2E/multi-agent pattern library and 'Current Repo Notes' into a reference file (e.g. references/e2e-patterns.md) and keep SKILL.md as a concise overview with clearly signaled links.

Trim content Claude already knows — the 'Mock Axios' snippet, the basic component-test example, and the generic .eslintrc.js sample — and relocate dated notes to a clearly marked 'Deprecated/old patterns' section.

DimensionReasoningScore

Conciseness

Mostly efficient repo-specific facts (env-var switching, file paths, endpoints), but it includes basics Claude already knows (the 'Mock Axios' snippet, a standard RTL component test, a generic .eslintrc.js sample) and a dated 'Current Repo Notes (2026-02-08)' section that is not placed in a deprecated/old-patterns section. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than score 4 because of the known-concept padding and time-sensitive dated content.

3 / 5

Actionability

Provides exact executable commands ('cd backend && npm test', './dev.sh test:integration', 'INTEGRATION_TEST=true npm --prefix backend test -- --forceExit') and complete patterns like the ingest-token and runtime-token flows. It stops short of score 5 because some snippets contain placeholders ('scopes: [...]', 'payload: {...}') and reference undefined context (token, testUser), matching 'Mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

Prerequisites are sequenced ('start mongo + postgres first', 'Requires ./dev.sh up to be running first') but there are no validation checkpoints or error-recovery guidance, e.g. what to verify before running integration tests or how to respond to failures. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than score 4, which requires most checkpoints to be present.

3 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers and a docs table, but ~230 lines of inlined pattern libraries (E2E patterns, multi-agent patterns, repo notes) that belong in separate reference files, with no bundle reference files present. This matches 'Some structure but could be better organized; content that should be separate is inline' — above score 2 thanks to the good headers, below score 4 because bulk detail is inlined rather than split out.

3 / 5

Total

13

/

20

Passed

Description

61%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 has an explicit and natural 'Use when...' trigger clause and names specific technologies, but the capability statement is generic — it provides 'context' without stating concrete actions. Broad phrasing like 'Testing and code quality' also creates moderate overlap risk with other development skills.

Suggestions

Replace 'Testing and code quality context for...' with concrete actions, e.g. 'Write Jest unit and API tests with in-memory databases, run React Testing Library component tests, and configure/fix ESLint issues.'

Add natural trigger variations such as 'unit tests', 'test coverage', or 'flaky tests' to broaden keyword coverage.

Sharpen distinctiveness by scoping the trigger to this repo's stack, e.g. 'Use when writing or debugging tests for this repository's backend/frontend, or when lint errors need fixing.'

DimensionReasoningScore

Specificity

The description names the domain and technologies ('Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns') but provides no concrete actions — it offers 'context' rather than saying what it does, matching the anchor 'Names the domain but actions are minimal or generic'. It is not score 3 because no concrete actions are listed, and not score 1 because the domain is explicitly named with specific tools.

2 / 5

Completeness

Both parts are present: the 'what' ('Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns') and an explicit 'when' ('Use when writing tests or fixing linting issues'). It does not reach 5 because the 'what' is generic ('context for') rather than concrete capabilities, and it is above 3 because the 'when' is explicit rather than implied.

4 / 5

Trigger Term Quality

Includes natural phrases users would say — 'writing tests', 'fixing linting issues', 'Jest', 'ESLint', 'React Testing Library' — giving good keyword coverage. It falls short of score 5 because common variations like 'unit tests', 'test coverage', or 'flaky tests' are missing.

4 / 5

Distinctiveness Conflict Risk

The named stack (Jest, React Testing Library, ESLint) narrows the niche, but 'Testing and code quality' is broad and 'writing tests' could overlap with general development or code-review skills — matching 'Somewhat specific but could still overlap with similar skills'. Not 4 because the trigger surface remains broad rather than a clear distinct niche.

3 / 5

Total

13

/

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.

Validation — 15 / 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

Team-Commonly/commonly

Path

fleet-skills/testing/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.