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

64%

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

63%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.

Highly actionable and well-sequenced content with strong executable commands and validation checkpoints, but it is over-long and monolithic, padding the context window with reflection and decorative sections instead of splitting detail into reference files.

Suggestions

Remove the 'Session Reflection: Testing Insights' section and the 'Perfect For' emoji list; these are journal/decorative content that does not earn its tokens.

Move the GitHub Actions CI example, the full command-reference table, and the detailed troubleshooting tables into a references/ file (e.g., CI.md, COMMANDS.md) and link to them from the body to improve progressive disclosure.

Add a mandatory validation gate before the destructive 'make db-reset' (e.g., require a pg_dump backup and an explicit confirmation step) so the destructive workflow clears the workflow_clarity cap.

Dimension	Reasoning	Score
Conciseness	The ~720-line body is noticeably verbose, with padded sections that assume Claude's competence less than they should: an ASCII architecture diagram, a 'Perfect For' emoji list, a 'Session Reflection: Testing Insights' journal section, and troubleshooting content duplicated across tables.	2 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: concrete make targets, curl/psql health checks, a readiness script, and a complete GitHub Actions YAML covering the common E2E cases.	5 / 5
Workflow Clarity	The E2E workflow is clearly sequenced with explicit validation (readiness script, 'make status' verification, backup/restore feedback loop); held below 5 because the destructive 'make db-reset' has a warning but no mandatory pre-reset validation gate or formal checklist.	4 / 5
Progressive Disclosure	No bundle files exist, so this is a monolithic 720-line document; header structure is good, but the CI/CD example, command reference table, and troubleshooting tables that belong in separate reference files are all inlined.	3 / 5
	Total	14 / 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, mostly concrete description that names the domain and several specific actions, but it lacks an explicit 'Use when...' trigger clause and has minor overlap with a related makefile skill.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when starting or stopping the EdgeQuake stack for E2E testing, verifying service health, or debugging test failures against a live backend and database').

Sharpen the opening beyond the generic 'Service management' framing to lead with the distinctive action and context.

Include natural synonyms/file markers users might say (e.g., 'Playwright tests', 'make dev', 'docker-compose') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the E2E-testing domain and lists several concrete actions ('Start, stop, and monitor PostgreSQL, backend API, and frontend services', 'health checks', 'logging utilities'); slightly below a 5 because the 'Service management' framing is somewhat generic.	4 / 5
Completeness	Clearly states the 'what', but 'when' is only weakly implied ('for E2E testing', 'for interactive testing workflows') with no explicit 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms users would say are present ('E2E testing', 'PostgreSQL', 'backend API', 'frontend services', 'health checks', 'logging'), with only a few synonyms/variations missing.	4 / 5
Distinctiveness Conflict Risk	Tied to the EdgeQuake E2E niche with distinct triggers, but overlaps with the related makefile-dev-workflow skill on make commands, giving minor conflict risk.	4 / 5
	Total	15 / 20 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: 4904960

Reviewed: about 20 hours 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.