CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-runner

Execução e análise de testes automatizados

Quality

60%

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 ./skills/workflow/test-runner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 content is strong on executable commands and concrete templates, but it is bloated by duplicated sections and basic-concept explanations, lacks an explicitly sequenced workflow with feedback loops, and mandates template files that are absent from the bundle. Consolidating duplicates and restructuring as a run→analyze→fix→re-run workflow would raise most dimensions.

Suggestions

De-duplicate the repeated sections: merge "Estrutura de Teste" / "Estrutura de Teste (AAA Pattern)", "Naming" / "Nomenclatura", and the coverage rules repeated in the checklist, and cut basics Claude already knows (test naming examples, isolation principles, unit-vs-integration definitions).

Restructure the core guidance as an explicit workflow with feedback loops — run tests → parse failures → diagnose by failure type → fix and re-run → report — instead of relying on implicit section ordering and an end checklist.

Resolve the dangling "Templates obrigatórios" references: either ship core/templates/django/pytest.ini and conftest.py in the skill bundle or inline their contents, and move the flag tables and failure taxonomy to a reference file to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body duplicates content — the AAA pattern appears twice ("Estrutura de Teste" and "Estrutura de Teste (AAA Pattern)"), naming conventions twice ("Naming" and "Nomenclatura"), and coverage mandates twice ("Regras Obrigatórias" and the checklist) — and teaches basics Claude already knows (test naming good/bad, isolation, unit vs integration). This is several unnecessary explanations and padded sections, matching anchor 2 rather than the mostly-efficient anchor 3.

2 / 5

Actionability

Concrete executable guidance dominates: real pytest/jest/go commands, flag tables, a coverage grep/awk pipeline, runnable fixture examples, and a complete report template. Held below anchor 5 by the comment-only pseudocode blocks in "Análise de Falhas" and the mandatory templates (core/templates/django/pytest.ini, conftest.py) that are not present in the bundle.

4 / 5

Workflow Clarity

A sequence (detect framework → run → analyze failures → report) is only implicit in the section ordering, and verification exists only as an end-of-document checklist with no explicit feedback loop (fail → investigate → fix → re-run). This matches anchor 3: sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

The file is well-sectioned with headers, but 330+ lines of reference material (flag tables, failure taxonomy, best-practices detail) are all inlined where a leaner SKILL.md plus reference files would serve better, and the "Templates obrigatórios" section references core/templates/django/pytest.ini and conftest.py that do not exist in the bundle. This fits anchor 3: some structure, but content that should be separate is inline and references are not backed by real files.

3 / 5

Total

12

/

20

Passed

Description

53%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 concise and names a clear domain with two actions, but it is thin: it lacks an explicit "when to use" clause, omits concrete capabilities like coverage analysis and failure diagnosis, and underuses natural trigger terms. Expanding it to two sentences covering what and when would lift most dimensions.

Suggestions

Add a "Use when..." ("Usar quando...") clause with concrete trigger phrases, e.g. "Usar quando o usuário pedir para rodar testes, verificar cobertura ou investigar testes falhando".

List the concrete capabilities in the description itself — running tests across frameworks (pytest, Jest, Go), measuring per-file coverage, and diagnosing failures — instead of the generic "execução e análise".

Include natural trigger keywords users actually say (testes, cobertura, testes falhando, rodar testes, pytest, jest) in the description rather than relying solely on the separate triggers field.

DimensionReasoningScore

Specificity

The description "Execução e análise de testes automatizados" names the domain and two concrete actions (execute, analyze), matching the 1-2-actions anchor. It falls short of anchor 4 because it omits specific capabilities like coverage measurement, failure diagnosis, or framework detection.

3 / 5

Completeness

It clearly answers "what" (execute and analyze automated tests) but contains no "Use when..." clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines. The separate triggers field is not part of the description text.

3 / 5

Trigger Term Quality

"testes automatizados" is a relevant natural keyword, but the description misses common variations users would say such as coverage, failing tests, pytest, or run tests. It has some relevant keywords but lacks synonyms and variations, fitting anchor 3 rather than the good-coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The automated-testing domain is mostly distinct with only minor overlap risk against closely related skills (CI/CD pipelines, debugging). It is not anchor 5 because the description itself carries no distinct trigger phrases to minimize conflict further.

4 / 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

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/test-runner/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.