CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

e2e-test-service-management

Service management for E2E testing in EdgeQuake. Start, stop, and monitor PostgreSQL, backend API, and frontend services. Includes health checks and logging utilities for interactive testing workflows.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/e2e-test-service-management/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.

An unusually actionable reference — every section gives exact, runnable commands — but it is bloated with session-reflection padding and meta content, and the destructive db-reset operation lacks a validation/snapshot checkpoint, capping workflow clarity. The 737-line monolith also ignores progressive disclosure entirely; CI, troubleshooting, and env-var material belong in separate reference files.

Suggestions

Delete the 'Session Reflection: Testing Insights' section and the 'Last Updated / Tested in Session / Verified with' footer — this is session-log metadata, not skill guidance.

Attach an explicit validation step to the destructive `make db-reset` workflow (e.g. snapshot first with the pg_dump command already shown under 'Use Database Snapshots', and confirm services re-healthy with `make status` after reset).

Move the CI/CD example, troubleshooting tables, environment-variable reference, and E2E test patterns into separate files under references/ and link to them from short summary sections, trimming SKILL.md toward an overview plus quick-start.

DimensionReasoningScore

Conciseness

The 737-line body includes several padded sections Claude does not need: an ASCII architecture diagram, a 'Session Reflection: Testing Insights' section with 'What Worked Well' and 'Challenges & Solutions', duplicated When-to-Use/Perfect-For lists, and session-specific metadata ('Last Updated: December 27, 2025', 'Tested in Session: E2E Testing New Query Button Fix'). This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor; it is not 1 because the command reference itself is dense and largely un-padded.

2 / 5

Actionability

Guidance is fully executable and copy-paste ready throughout: exact make targets per service, a complete bash readiness-wait script, curl/psql health checks, concrete env-var blocks, a troubleshooting table with specific commands, and a CI/CD yaml example covering the common cases. Nothing is pseudocode or hand-wavy.

5 / 5

Workflow Clarity

Sequences are clear (reverse-dependency start order, the numbered start → status → test → stop workflow) and validation exists via `make status` and health-check wait loops. However the destructive `make db-reset` workflow carries only a WARNING with no attached validation or snapshot step — per the rubric guideline, a destructive operation without validation caps workflow clarity at 3, so it cannot score 4 despite otherwise good sequencing.

3 / 5

Progressive Disclosure

Section headers and the command quick-lookup table give real structure, but the skill is a single 737-line monolith with no bundle files at all — content that clearly belongs in separate references (CI/CD config, troubleshooting, environment-variable reference, E2E test patterns) is inlined in SKILL.md. This matches the 'some structure but content that should be separate is inline' anchor; it is not 2 because the in-file organization is genuinely good, not minimal.

3 / 5

Total

13

/

20

Passed

Description

66%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, concrete description that names specific actions on specific services, but it never tells Claude when to reach for the skill — the missing 'Use when...' clause is the single biggest gap and caps completeness. Trigger coverage is good though incomplete on synonyms.

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when running E2E or integration tests in the EdgeQuake repo, starting or stopping the dev stack, checking service health, or debugging test failures against a live backend/database."

Broaden trigger terms with natural synonyms users would say, such as "Playwright tests", "docker services", "dev environment", and "integration testing".

Mention one or two more concrete capabilities (e.g. view service logs, reset the test database) to round out the action coverage toward comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Start, stop, and monitor PostgreSQL, backend API, and frontend services", "health checks and logging utilities") on named services, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because coverage is not comprehensive (no log-tailing, reset, or status verbs).

4 / 5

Completeness

The 'what' is clear (start/stop/monitor services plus health-check and logging utilities), but there is no 'Use when...' clause — the 'when' is only weakly implied by "for E2E testing ... for interactive testing workflows", which per the rubric caps completeness at 3. It is not 2 because the 'what' is concrete, and not 4 because 'when' guidance is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural phrases like "E2E testing", "service management", "health checks", and "PostgreSQL" give good keyword coverage, but common variations users would say ("integration testing", "docker", "dev environment", "Playwright") are missing, so it does not reach the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

Naming "EdgeQuake" and E2E-specific service lifecycle creates a mostly distinct niche with minimal conflict risk, though it overlaps with the closely related makefile-dev-workflow skill (which owns the general make-command reference). It is not 5 because that overlap with a sibling skill is real.

4 / 5

Total

15

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (738 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

12

/

16

Passed

Repository

raphaelmansuy/edgequake

Path

.github/skills/e2e-test-service-management/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.