CtrlK
BlogDocsLog inGet started
Tessl Logo

efficiency-test-authoring

Author or convert Fenix Android UI tests onto the ui/efficiency framework. Use this whenever the task involves writing a new efficiency UI test, converting/porting a legacy ui/ (robot-based) test onto the efficiency framework, or building what a test needs — page objects, selectors, navigation-graph nodes/edges, or BasePage primitives. Trigger even when the user doesn't name the framework: "convert this smoke test", "add a page object for the bookmarks screen", "wire up navigation to Settings", "write an efficiency test for X" all qualify. Do NOT use for edits to legacy robot-based tests that are staying on the old framework, or for non-Android test work.

75

Quality

92%

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

85%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 dense, highly actionable workflow skill with explicit gates, validation checkpoints, and well-signaled references to in-tree guides. Its main weakness is length — several meta and inline-gotcha passages could be trimmed or deferred to the referenced docs.

Suggestions

Tighten the intro and 'Status: v0' section — the framing about dogfooding and updating logs can be shortened without losing the flag-and-update guidance.

Move the four inline trap explanations in gate 2 to a one-line summary each with a pointer to HARNESS-GOTCHAS, keeping only the trap name and the rule in the body.

Collapse repeated JSON-verdict guidance (gates 6 and the tools table both restate 'read effverify --json, not the raw log') into a single authoritative statement to reclaim tokens.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the intro, the v0 Status section, and the inline four-trap explanations in gate 2 could be tightened or pushed to the referenced gotchas docs; the body is long even for a routing skill.

3 / 5

Actionability

Concrete executable commands with exact flags throughout (effnext --json, effscaffold <Class.method> --json, effcheck/effbuild/effverify --json) plus a copy-paste-ready @Converted Kotlin snippet and named verdict fields to read.

5 / 5

Workflow Clarity

A clearly sequenced 10-gate loop (0–9) with explicit validation checkpoints (effcheck pre-flight, effverify done-gate, parity diff), feedback loops (efftriage on failure), and a close-out checklist — validation is present for this batch/conversion operation.

5 / 5

Progressive Disclosure

Acts as an overview that routes to one-level-deep in-tree guides via a clear reference table and a tools table; no bundle files ship locally, but the structure is well-signaled and navigable rather than monolithic.

5 / 5

Total

18

/

20

Passed

Description

100%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 states concrete capabilities, natural trigger phrases, and explicit when-to-use/when-not-to-use guidance in third person. It is comprehensive yet free of fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — writing efficiency UI tests, converting/porting legacy robot-based tests, and building page objects, selectors, navigation-graph nodes/edges, and BasePage primitives — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what (author/convert Fenix Android UI tests onto the efficiency framework plus its building blocks) and when ("Use this whenever the task involves…" plus a Trigger clause), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes natural phrases a user would actually say — "convert this smoke test", "add a page object for the bookmarks screen", "wire up navigation to Settings", "write an efficiency test for X" — alongside the framework's own terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Fenix Android UI tests on the efficiency framework) and adds an explicit negative boundary ("Do NOT use for edits to legacy robot-based tests… or for non-Android test work"), minimizing wrong-skill triggering.

5 / 5

Total

20

/

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
mozilla/firefox-aidev-plugins
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.