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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/e2e-test-service-management/SKILL.md

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 skill is highly actionable with clear, validated workflows, but it is verbose and monolithic — redundant reflective/decorative sections and the absence of any referenced bundle files leave progressive disclosure and conciseness short of ideal.

Suggestions

Move CI/CD integration, troubleshooting, and the Session Reflection into reference files (e.g. TROUBLESHOOTING.md, CI.md) and link them one level deep from SKILL.md.

Cut the emoji "Perfect For" checklists, the repeated command-reference table, and the dated footer to reduce token overhead.

Treat TESTING_SERVICES.sh as an actual bundle file in ./scripts/ and reference it, rather than only naming it in frontmatter metadata.

Dimension	Reasoning	Score
Conciseness	The body is largely actionable, but ~738 lines include redundant decoration (emoji "Perfect For" checklists, a Session Reflection section, repeated command tables, and a dated "Last Updated: December 27, 2025" footer) that could be trimmed.	2 / 3
Actionability	Provides copy-paste-ready executable commands throughout — make dev/stop/status, curl/psql health checks, Playwright invocations, a readiness script, and a full GitHub Actions YAML.	3 / 3
Workflow Clarity	The E2E flow is numbered with an explicit make status checkpoint, and the readiness script uses until-loops as validation feedback; the destructive db-reset is flagged with a WARNING.	3 / 3
Progressive Disclosure	Content is well-sectioned but monolithic in a single SKILL.md with no bundle references, and material that could be separate (CI/CD, troubleshooting, reflection) is inlined.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 clearly states concrete capabilities but lacks an explicit use-when trigger clause and uses single phrasings of trigger terms, leaving it distinguishable yet somewhat overlapping with a sibling skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting, stopping, or health-checking EdgeQuake services for E2E/Playwright testing."

Broaden trigger terms with natural user phrasings ("start the backend", "run the test environment", "docker services", "service health").

Sharpen distinctiveness from makefile-dev-workflow by framing this skill around service lifecycle/health rather than general make commands.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Start, stop, and monitor PostgreSQL, backend API, and frontend services" plus "health checks and logging utilities" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	The "what" is clear, but there is no explicit "Use when..." trigger clause — the "when" is only implied by "for E2E testing in EdgeQuake", which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Relevant terms like "E2E testing", "PostgreSQL", and "health checks" appear, but each concept has only one phrasing and common user variations (e.g. "run the backend", "start docker", "test environment") are missing.	2 / 3
Distinctiveness Conflict Risk	It targets a specific EdgeQuake E2E niche, but the make-command focus overlaps with the related makefile-dev-workflow skill, so it is not fully distinct.	2 / 3
	Total	9 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 62e6adb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.