CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-test-browser

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

68

Quality

83%

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

85%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 tightly written, well-structured skill body with a clear numbered workflow, explicit validation gates, and disciplined use of one-level-deep reference files. The only room for improvement is minor tightening of a few dense sentences.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence throughout with no beginner-concept padding, though a few dense passages (e.g. the port-resolution step and driver-policy rationale) could be trimmed slightly.

4 / 5

Actionability

Concrete, executable commands are given directly (gh pr view, git diff --name-only, resolve-port.sh, port resolution logic) with only minor gaps where the actual driver commands are delegated to reference files.

4 / 5

Workflow Clarity

A 10-step sequence with explicit validation checkpoints (verify server before asking, verify root before iterating) and feedback loops for failures and human-verification flows, including skip-with-reason handling in pipeline mode.

5 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references to real bundle files (pipeline-orchestration.md, agent-browser-driver.md, route-and-report.md, resolve-port.sh) each introduced with explicit 'Read ... before ...' guidance.

5 / 5

Total

18

/

20

Passed

Description

82%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 well-formed description that cleanly states its purpose and trigger condition with natural user phrasing. It is slightly light on the breadth of concrete actions it names, which keeps specificity from the top tier.

DimensionReasoningScore

Specificity

Names the domain and a single concrete action ('Run browser tests for pages affected by the current branch or PR') but offers no broader action coverage, matching the anchor for 1-2 concrete actions without comprehensiveness.

3 / 5

Completeness

Explicitly answers both what ('Run browser tests for pages affected by the current branch or PR') and when ('Use when asked to run or check browser tests for the current change') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural phrases a user would say ('run or check browser tests', 'current change', 'branch or PR') are present with good coverage, though a few natural synonyms like 'E2E' or 'end-to-end' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — branch/PR-scoped browser testing with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

Validation15 / 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
EveryInc/compound-engineering-plugin
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.