CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

router-act

How to write end-to-end tests using createRouterAct and LinkAccordion. Use when writing or modifying tests that need to control the timing of internal Next.js requests (like prefetches) or assert on their responses. Covers the act API, fixture patterns, prefetch control via LinkAccordion, fake clocks, and avoiding flaky testing patterns.

Quality

88%

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

82%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 strong, highly actionable skill body with executable code for every pattern and clear anti-pattern guidance. The main improvement opportunities are modest tightening of verbose sections and moving deep-dive internals into reference files.

Suggestions

Trim the App Shell section's restatements (e.g., the 'no-requests' and 'block: reject' consequences are each stated twice) to improve token efficiency.

Move deep-dive internals (App Shell matching semantics, hub-page construction details) into a reference file, keeping SKILL.md as a leaner overview with pointers.

Add brief diagnostic guidance for what to check when a 'no-requests' or 'includes' assertion fails unexpectedly (beyond the BFCache/browser.back() cause).

DimensionReasoningScore

Conciseness

Assumes Claude's knowledge of Playwright and Next.js with no padding about basics, but sections like the App Shell explanation and the 'includes' matching rules restate points and could be trimmed slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript/TSX covers every common case: config options, the LinkAccordion component, the standard navigation pattern, hub pages, fake clock setup, and a complete 4-step test flow.

5 / 5

Workflow Clarity

Sequences are explicit and numbered (internal steps 1-6, the two-step navigation scope, the hub-page test flow), and flakiness sources pair failure modes with fixes, but there is no explicit error-recovery guidance for diagnosing a failed assertion.

4 / 5

Progressive Disclosure

Good structure with clear section headers and a Reference section pointing to real repo paths, but the ~290-line body keeps deep-dive material (App Shell internals, hub-page details) entirely inline with no content split into separate files.

4 / 5

Total

17

/

20

Passed

Description

92%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, complete, and explicit about both capabilities and trigger conditions, with concrete named utilities. Minor synonym coverage (e.g., 'e2e', 'Playwright', 'segment cache') keeps trigger term quality just short of perfect.

DimensionReasoningScore

Specificity

Names concrete utilities (createRouterAct, LinkAccordion) and multiple specific capabilities — 'act API, fixture patterns, prefetch control via LinkAccordion, fake clocks, and avoiding flaky testing patterns' — comprehensively covering what the skill does.

5 / 5

Completeness

Explicitly answers what ('How to write end-to-end tests using createRouterAct and LinkAccordion... Covers the act API, fixture patterns, prefetch control, fake clocks') and when ('Use when writing or modifying tests that need to control the timing of internal Next.js requests (like prefetches) or assert on their responses').

5 / 5

Trigger Term Quality

Natural trigger phrases like 'end-to-end tests', 'Next.js requests', 'prefetches', and 'flaky' are present and specific, but common synonyms such as 'e2e', 'Playwright', or 'segment cache' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Next.js client-router prefetch/navigation test instrumentation) with distinct triggers that would not plausibly fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

vercel/next.js

Path

.agents/skills/router-act/SKILL.md

Revision

ec8ddcd

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill