CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-e2e

Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./internal/template/templates/.agents/skills/moai-e2e/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 exceptionally lean, unambiguous dispatcher with concrete per-harness instructions. Its only weakness is that all substantive content is delegated to an external mirrored file with no in-bundle detail or fallback guidance.

DimensionReasoningScore

Conciseness

Three lean lines with zero padding and no explanation of concepts Claude already knows; every token earns its place for a dispatcher skill.

5 / 5

Actionability

Gives an exact executable command (invoke Skill("moai") with arguments e2e) and a concrete fallback path (~/.agents/skills/moai/SKILL.md), but the mirror file's availability is never verified and no error handling is offered if it is absent.

4 / 5

Workflow Clarity

A single unambiguous dispatch action with a clearly stated two-branch conditional (harness with vs. without a skill loader); per the simple-skill exception this merits a 5.

5 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled one-level-deep reference, but the entire capability content lives in a file outside the bundle (no references/, scripts/, or assets/ exist), a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

53%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 communicates a clear capability domain with two concrete actions, but lacks any trigger guidance ("Use when...") and misses common synonyms such as "end-to-end". Distinctiveness is reasonably good thanks to the specific E2E/platform framing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for end-to-end/E2E tests, test scaffolding, or running the existing E2E suite."

Include natural synonyms and keywords such as "end-to-end", "integration tests", and common tool names (Playwright, Appium) users are likely to mention.

Enumerate a few more concrete actions (e.g., detect the project's test framework, generate configs, launch browsers/devices) to raise specificity beyond two generic actions.

DimensionReasoningScore

Specificity

"Create and run E2E tests" names the domain with two concrete actions, and "auto-detection and CLI-first toolchains" are feature descriptors rather than additional actions, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (create and run E2E tests across platforms), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"E2E tests" and "web, mobile, and desktop" are natural user phrases, but common variations like "end-to-end", "testing", and specific tool names (Playwright, Appium) are missing.

3 / 5

Distinctiveness Conflict Risk

"E2E tests across web, mobile, and desktop" carves out a fairly distinct niche with minor overlap risk against general testing or platform-specific test skills, fitting mostly-distinct rather than fully distinct.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

modu-ai/moai-adk

Path

internal/template/templates/.agents/skills/moai-e2e/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.