CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-e2e-test

Scaffold e2e tests for MCP tools in this repo's e2e/ harness. Accepts a single tool name (e.g. `insertText`) or a freeform scope phrase that expands to many tools ("make tests for the whole google docs service", "all read tools", "everything for sheets except batchUpdateSpreadsheet"). Use this skill whenever the user wants to add, write, generate, or scaffold e2e tests, smoke tests, integration tests, or live-client tests for the MCP tools in this repo — even when phrased indirectly ("cover the new endpoint", "test the sheets tools"). Also use when invoked as `/add-e2e-test <args>`.

Quality

94%

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

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

The body is an exemplar of repo-specific procedural writing: exact commands, paths, and handler strings make it fully executable, the seven-step workflow carries explicit validation and confirmation checkpoints with enumerated failure-mode handling, and detail is properly pushed into real, well-signaled reference files. Only a handful of justificatory asides keep conciseness at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is dense with harness-specific, non-inferable knowledge (tier cost arithmetic, per-shape accounts, "`handleListGoogleDocs` returns `\"Found N Google Document(s):\"`") and almost never explains concepts Claude already knows. A few sentences are pure justification prose that could be trimmed — "That is the arithmetic behind the split.", "They are listed above so the tier is visible when you are deciding" — matching 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Quotes: "cd e2e && npm run typecheck && npm run test:unit", "npm run check:auth -- fixture", "grep `src/<service>/server.ts` for `addTool({ name: '`", the template-to-destination table ("`assets/read.check.ts.tmpl` → `e2e/tests/tools/<shape>/<tool>.check.ts`"), and the fill-in report template. Everything is copy-paste ready with exact paths, commands, and real return strings; specific examples cover the common single-tool and bulk cases, matching the 'fully executable' anchor.

5 / 5

Workflow Clarity

Seven numbered steps (resolve → read source → choose shapes → ask once → generate → verify → report) with explicit validation: typecheck and unit tests in step 6, per-shape auth preflight commands, and confirmation checkpoints ("Print the plan and confirm when N > 1. Confirm explicitly when N > 30"). Error recovery is enumerated per failure mode ("bulk runs soft-skip and surface it in the report", "Required params underderived — write with `<TODO:>` and report") and the report format acts as a checklist. The batch-operation validation cap does not apply because validation is present and explicit, fitting the 'explicit validation steps; feedback loops; checklists' anchor.

5 / 5

Progressive Disclosure

The body signals one-level-deep references exactly at the point of need ("See `references/task-tests.md`; the bar is high", "`references/shapes.md` covers what to assert in each", "See `references/special-cases.md`"), all of which exist in the bundle, and the Layout section gives a tree with one-line descriptions of every file plus pointers to repo background docs. Decision logic stays in SKILL.md while per-case detail is split out, matching 'clear overview with well-signaled one-level-deep references; content appropriately split'.

5 / 5

Total

19

/

20

Passed

Description

95%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 description: it states exactly what the skill does, enumerates natural trigger synonyms including indirect phrasings, and pins everything to a specific repo niche. The only soft spot is that the capability list is one scaffolding action with input variants rather than multiple distinct actions, which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Quotes: "Scaffold e2e tests for MCP tools in this repo's e2e/ harness", "Accepts a single tool name (e.g. `insertText`) or a freeform scope phrase that expands to many tools". The description names the domain and gives concrete, exampled input handling, matching the 'lists several specific actions; minor gaps' anchor. It is not a 5 because the capability is a single scaffolding action plus input variants rather than a comprehensive list of multiple distinct actions; it is above 3 because it is far more concrete than 'names domain and 1-2 concrete actions'.

4 / 5

Completeness

Quotes: what — "Scaffold e2e tests for MCP tools in this repo's e2e/ harness"; when — "Use this skill whenever the user wants to add, write, generate, or scaffold e2e tests... even when phrased indirectly... Also use when invoked as `/add-e2e-test <args>`". Both 'what' and 'when' are answered explicitly with concrete trigger phrases, matching the top anchor; the 'when' clause is present and specific, so the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

Quotes: "add, write, generate, or scaffold e2e tests, smoke tests, integration tests, or live-client tests", "even when phrased indirectly ('cover the new endpoint', 'test the sheets tools')". This is comprehensive synonym coverage (e2e/smoke/integration/live-client, add/write/generate/scaffold) including indirect natural phrasings and the slash-command invocation, exactly matching the 'comprehensive coverage of natural terms including synonyms' anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

Quotes: "for the MCP tools in this repo", "in this repo's e2e/ harness". Every capability and trigger is pinned to MCP tools in this specific repo's e2e harness, establishing a clear niche with distinct triggers and minimal conflict risk. It fits the 'clear niche with distinct triggers; minimal conflict risk' anchor rather than 4, because even the broadest terms (smoke/integration tests) are qualified by the MCP-tool/repo scope.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

boarlabsxyz/awesome-mcp

Path

.claude/skills/add-e2e-test/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.