CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e-tests

Run, monitor, and fix frontend Cypress E2E tests. Handles local execution, CI monitoring, failure diagnosis, flaky test detection, and accessibility regression checks. Use this skill whenever the user mentions Cypress, E2E tests, end-to-end tests, test failures, CI failures, "CI is red", flaky tests, accessibility testing, or wants to run/debug/fix any frontend integration test — even if they don't say "e2e" explicitly.

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 with clear, validated workflows, but it is a long monolithic file with some redundant repeated blocks and no progressive disclosure of detail into bundle files. Tightening repetition and splitting out reference material would lift the weaker dimensions.

Suggestions

De-duplicate the gh CLI pre-flight check: state it once and reference it from the monitor/fix/flaky sections instead of repeating the verbatim block three times.

Move the Custom Cypress Commands reference and the Local-vs-CI config table into a reference file under references/ (e.g. commands.md) and link to it from SKILL.md to apply progressive disclosure.

Trim the default help-text block since it restates commands already detailed in their own sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient command/path content with little conceptual padding, but the identical gh CLI pre-flight check is repeated verbatim across sections 2, 3, and 4, and the help-text block duplicates content already stated, so it could be tightened.

2 / 3

Actionability

It provides concrete, copy-paste-ready bash commands with exact file paths and flags (e.g., "npx cypress run --config-file ./cypress.config.js --headless --spec ..."), matching the fully-executable score-3 anchor.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced (fix workflow Steps 1-7) with pre-flight validation checkpoints and a verify-the-fix retry loop, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Content is well-sectioned but monolithic: a single ~330-line SKILL.md with all detail inline and no bundle files in references/scripts/assets, so material like the command reference and config-diff table that could be split out is not, matching the score-2 anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, trigger-rich, and explicitly pairs capabilities with use-when guidance in third person. It is a strong model description with no notable weaknesses.

DimensionReasoningScore

Specificity

"Run, monitor, and fix frontend Cypress E2E tests. Handles local execution, CI monitoring, failure diagnosis, flaky test detection, and accessibility regression checks" lists multiple specific concrete actions, matching the score-3 anchor.

3 / 3

Completeness

It clearly answers both what (run/monitor/fix E2E tests with enumerated capabilities) and when via an explicit "Use this skill whenever the user mentions..." clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user terms are well covered: "Cypress, E2E tests, end-to-end tests, test failures, CI failures, 'CI is red', flaky tests, accessibility testing," plus the colloquial "CI is red" and the note about triggering even when 'e2e' is not said explicitly.

3 / 3

Distinctiveness Conflict Risk

The niche is distinct (frontend Cypress E2E for OPRE OPS) with specific triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
HHS/OPRE-OPS
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.