CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e-conventions

When to write e2e tests, where to put them, and how to verify them. Apply to any task touching UI, filters, forms, or interactions.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, well-structured conventions skill that assumes Claude's competence and offloads spec internals to a clearly referenced companion skill. It is highly concise with good progressive disclosure; actionability and workflow clarity are strong but not maximal since concrete spec content and a feedback loop are deferred.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no over-explanation of concepts Claude already knows; every section (when required, where, what to verify, red flags, checklist) earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Concrete guidance throughout — the `e2e/<feature-name>.spec.ts` pattern, a real example filename, an explicit trigger list, and a verification checklist — but spec internals are deferred to playwright-testing, leaving minor gaps versus copy-paste-ready 5.

4 / 5

Workflow Clarity

Clear guidance with an explicit verification checklist and a stated CI-runs-it handoff; it is a conventions reference rather than a sequenced multi-step workflow, so it sits below the feedback-loop/checklist-driven 5.

4 / 5

Progressive Disclosure

Well-organized sections with a single clearly signaled one-level reference (`Skill({skill: "playwright-testing"})`) for assertion/locator detail, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

18

/

20

Passed

Description

75%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 solid, concise description that explicitly states both what the skill covers and when to apply it, with natural trigger terms. It is strong but not exceptional: the 'what' is framed as topics rather than performed actions and the trigger surface is fairly broad.

DimensionReasoningScore

Specificity

Names the e2e-test domain and three concrete concerns (when to write, where to put, how to verify), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Both what (guidance on when/where/how for e2e tests) and when ('Apply to any task touching UI, filters, forms, or interactions') are explicit; the what is topic-framed rather than crisp performed actions, keeping it below 5.

4 / 5

Trigger Term Quality

Natural user-facing terms 'UI, filters, forms, interactions' plus 'e2e tests' give good coverage, but synonyms like 'end-to-end' are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The e2e-conventions niche is distinct with clear triggers, but 'any task touching UI, filters, forms, or interactions' is a broad surface with minor overlap risk against general UI-testing skills.

4 / 5

Total

16

/

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
marmelab/atomic-crm
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.