CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard-chat-best-practices

Apply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components/PPR behavior, static shell layout, Suspense bootstrap boundaries, theme hydration, auth display hydration, signed-in/signed-out static shell behavior, optimistic messages, streaming row identity, composer/sidebar interactions, thinking/tool rendering, responsive styling, visual polish, or Vercel dashboard chat comparisons.

72

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

90%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 well-crafted, lean instruction-only skill with highly actionable, template-specific guidance and a solid verification checklist. Its only limitation is that it is a broad pattern catalog rather than a single sequenced workflow with explicit feedback loops.

DimensionReasoningScore

Conciseness

The body is lean bullet directives naming exact identifiers and commands without explaining concepts Claude already knows; the few rationale lines are purposeful rather than padding, so every token earns its place.

5 / 5

Actionability

It gives concrete executable guidance — exact component names, full prop contracts, exact cookies/attributes, and exact commands — so Claude knows precisely what to use, satisfying the instruction-only skill bar without code.

5 / 5

Workflow Clarity

Concerns progress logically from shell to verification, ending in an explicit manual-check checklist and pnpm typecheck/build gates, but it is a pattern catalog rather than a strict sequenced workflow and lacks a validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

With no bundle files present, the ~90-line body is cleanly split into ten well-labeled sections with no nested references; it earns good structure but exceeds the 50-line simple-skill exception that would auto-grant a 5.

4 / 5

Total

18

/

20

Passed

Description

87%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, niche description that answers both what and when with concrete trigger phrases. The only soft spot is that the headline action ('apply patterns') is abstract, with the specificity carried mostly by the Use-when list rather than discrete named actions.

DimensionReasoningScore

Specificity

The primary verb 'Apply dashboard-grade chat UX patterns' is somewhat abstract, but the Use-when list enumerates many concrete change-areas (Suspense bootstrap boundaries, streaming row identity, composer/sidebar interactions), giving broad and specific coverage rather than discrete atomic actions.

4 / 5

Completeness

It states a clear 'what' ('Apply dashboard-grade chat UX patterns in the Eve chat template') and an explicit 'Use when...' clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural developer terms like 'theme hydration', 'optimistic messages', 'composer/sidebar', and 'Vercel dashboard chat' give good coverage, though a few natural variations are missing and some phrases lean toward internal jargon ('streaming row identity').

4 / 5

Distinctiveness Conflict Risk

The description is niche to the Eve chat template with highly specific triggers (Cache Components/PPR, Suspense bootstrap, Vercel dashboard chat), giving it a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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
vercel/eve
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.