CtrlK
BlogDocsLog inGet started
Tessl Logo

evm-wallet-docker-e2e

Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures).

70

Quality

85%

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

96%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 content is an excellent, executable runbook with strong validation checkpoints and a failure-diagnosis feedback loop. It is self-contained and well-structured; only its length keeps progressive disclosure from a top score.

DimensionReasoningScore

Conciseness

The body is lean: concrete commands with only task-specific notes (e.g. why to tear down first), no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Every step provides copy-paste ready, executable commands (docker info, yarn workspace ..., the polling loop, tail logs) covering the common cases including failure diagnosis.

5 / 5

Workflow Clarity

A clear 6-step sequence with explicit validation checkpoints (Docker running, 8 services healthy before proceeding, timeout halt) and a feedback loop for diagnosing failures in order.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections as a self-contained workflow with no external references needed, but at ~95 lines it slightly exceeds the under-50-line simple-skill exception for a top score.

4 / 5

Total

19

/

20

Passed

Description

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

The description is specific and distinctive, listing concrete actions for a well-scoped niche, but lacks an explicit 'when to use' trigger clause. Adding a 'Use when...' phrase would raise completeness.

Suggestions

Add an explicit trigger clause such as 'Use when running or debugging the evm-wallet Docker e2e suite' to satisfy the 'when' half of completeness.

Include a natural synonym like 'end-to-end tests' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures)" lists multiple concrete actions (build, start stack, wait for healthy, test, diagnose) with comprehensive coverage.

5 / 5

Completeness

The description clearly answers "what" but has no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"Docker e2e tests" includes natural terms a user would say, but misses common synonyms like "end-to-end tests" or "integration tests".

4 / 5

Distinctiveness Conflict Risk

"evm-wallet Docker e2e tests" carves out a clear, narrow niche tied to a specific package's Docker e2e tests, with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Consensys-Incorporated/ocap-kernel
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.