CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification against canonical docs, and Vercel technical writing style.

Quality

87%

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

81%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 highly actionable with concrete file paths, verbatim canonical blocks, and a strong audit checklist, but it carries notable redundancy between the Rules and Audit-checklist sections that hurts token efficiency. Progressive disclosure is good despite no bundle files because structure and external references are clear.

Suggestions

Collapse the Audit checklist into a short cross-reference to the Rules section (or vice versa) instead of restating every rule as a checkbox, to remove the largest source of redundancy.

Extract the verbatim canonical blocks (opt-out mdx, Allow blocking route shape, terminology table) into a reference file under references/ and link to them, reducing SKILL.md length and improving progressive disclosure.

Consolidate the repeated 'the page is for the user, not the agent' / 'never Confirm with the user' guidance into a single stated rule rather than restating it across Rules, Allow-blocking-route, and Audit sections.

DimensionReasoningScore

Conciseness

Mostly efficient and full of genuine domain knowledge Claude would not know, but the Audit checklist section substantially duplicates the Rules section and the 'the page is for the user, not the agent' guidance repeats across sections, so it could be tightened.

3 / 5

Actionability

Provides fully executable guidance: exact framework file paths, a verbatim canonical opt-out mdx block to copy, concrete FixCard prop rules (self-closing, no prompt prop, href = #auto-slug), and code-snippet rules with the filename= attribute.

5 / 5

Workflow Clarity

Sequences the work clearly via the numbered 'Before you start' steps and closes with an explicit validation checklist (audit items) that acts as a feedback loop for catching errors before publishing.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and explicit references to real external sources (instant-guidance-data.ts, the canonical reference page, the vercel-technical-writing skill), but a large amount of canonical content (verbatim blocks, terminology list, Allow-blocking-route shape) is inlined with no bundle files to offload it.

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 clear, concrete, and complete, answering both what the skill does and when to invoke it with domain-specific trigger phrases. Voice is imperative/infinitive (no first/second person), avoiding the voice penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (write/audit an insight-kind error page, create errors/<slug>.mdx pages, check pages against framework fix cards) and enumerates covered concerns (page structure, title alignment, FixCard cards, code snippets, terminology verification, Vercel style), giving comprehensive coverage rather than minimal generic actions.

5 / 5

Completeness

Explicitly answers both what ('Write or audit an insight-kind error page for the Next.js dev overlay') and when ('Use when creating a new errors/<slug>.mdx page, auditing an existing one, or checking that a page matches the framework fix cards') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('error page', 'Next.js dev overlay', 'fix cards', 'audit') plus the .mdx file extension, but omits some synonyms used in the body (e.g. 'insight page') so a few natural variations are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a sharply specific niche (insight-kind Next.js dev overlay error pages with FixCard cards) with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 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

relative_links

Relative link issues: 6 suspicious

Warning

Total

13

/

16

Passed

Repository

vercel/next.js

Path

.agents/skills/insight-error-page/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.