skillshare-cli-e2e-test

Run isolated E2E tests in devcontainer from ai_docs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation. If you need to run a multi-step CLI validation sequence (init → install → sync → verify), this is the skill — it handles ssenv isolation, flag verification, and structured reporting. Prefer this over ad-hoc docker exec sequences for any test that follows a runbook or needs reproducible isolation.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%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 highly actionable, well-sequenced E2E testing skill with strong workflow validation and concrete commands throughout. Its weaknesses are repetition across sections (conciseness) and a monolithic structure with no bundle references (progressive disclosure) despite being well over 50 lines.

Suggestions

Consolidate the repeated 'lessons-learned', config-append idempotency, and '--init' guidance into a single canonical location and reference it elsewhere, to tighten conciseness.

Move the stable reference material (--json quick reference table, Runbook Assertion Types table, Container Command Templates, ssenv Quick Reference) into files under references/ and link to them from SKILL.md, improving progressive disclosure for a 400-line skill.

De-duplicate the Runbook Quality Checklist against the inline Phase 3 guidance so each gotcha appears once with a cross-reference.

Dimension	Reasoning	Score
Conciseness	Mostly task-specific knowledge Claude does not already know (ssenv semantics, CLI flag gotchas), but carries notable redundancy — 'lessons-learned' is referenced ~4 times, config-append idempotency ~3 times, and '--init' behavior is repeated across the checklist, Phase 3, and Rules. Not a 2 because the bulk is genuinely novel rather than padded explanation of known concepts; not a 4 because the repetition could be consolidated.	3 / 5
Actionability	Copy-paste-ready docker exec/ssenv commands, concrete jq assertion patterns, exact flag strings with explicit wrong/right examples ('uninstall --yes → wrong, use --force'), and a 19-item checklist each tied to a specific command or path — fully executable coverage of common cases.	5 / 5
Workflow Clarity	Clear Phase 0→4 sequence with explicit validation checkpoints (JSON summary analysis, pass/fail/skip branching, individual failure debugging), AskUserQuestion gates, ask-before-cleanup, and a retrospective feedback loop — satisfying the batch/destructive-operation validation requirement rather than triggering its cap.	5 / 5
Progressive Disclosure	Well-sectioned with clear headers, but no bundle files exist and the ~400-line body inlines material that could live in separate references (the --json quick reference table, assertion-types table, container command templates, ssenv reference). Not a 4 because content that should be separate is inline with no one-level-deep external references; not a 2 because section organization is solid rather than a monolithic wall.	3 / 5
	Total	16 / 20 Passed

Description

88%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 strong, specific description that clearly states what the skill does and when to use it, with concrete trigger phrases and third-person voice. Main gap is minor overlap with the sibling /mdproof skill and slightly limited synonym/extension coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'run isolated E2E tests', 'execute a test runbook', 'validate a feature end-to-end', 'create a new runbook', 'test CLI behavior in isolation' — plus concrete capabilities ('ssenv isolation, flag verification, and structured reporting'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers 'what' (run isolated E2E tests in devcontainer from runbooks, handling ssenv isolation/flag verification/structured reporting) and 'when' via the 'Use this skill whenever the user asks to:' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good coverage of natural phrases users would say ('run an E2E test', 'execute a test runbook', 'validate a feature end-to-end', 'test CLI behavior in isolation', 'multi-step CLI validation sequence'), but lacks the synonym/file-extension breadth of the 5 anchor. Not a 3 because it goes well beyond a couple of generic keywords with several natural trigger phrases.	4 / 5
Distinctiveness Conflict Risk	Clear niche (devcontainer + ssenv + runbook-driven E2E for the skillshare CLI) with distinct triggers, but the documented sibling '/mdproof' skill creates minor overlap risk for runbook-related requests. Not a 5 because of that adjacency; not a 3 because the devcontainer/ssenv isolation framing is clearly distinct.	4 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: runkids/skillshare
Path: .skillshare/skills/skillshare-cli-e2e-test/SKILL.md
Commit: e535e8f

Reviewed: 2 days 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.