dashboard-platform-change

Modifies dashboard frontend or backend surfaces that present, configure, or manage router behavior through the console UI. Use when changing dashboard pages or components, backend handlers, console persistence, auth or session flows, or user-visible routing metadata in the dashboard.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

Concise and highly actionable with concrete commands and a clear workflow, but the skill is weakened by broken 'Must Read' references and an implicit rather than explicit validation feedback loop.

Suggestions

Restore or create the three referenced 'Must Read' files (change-surfaces.md, module-boundaries.md, dashboard/backend/handlers/AGENTS.md) so the references resolve.

Add an explicit validate->fix->retry feedback loop in the workflow (e.g., 'If agent-ci-gate fails, fix the reported constraints and re-run before proceeding').

Confirm the relative paths in 'Must Read' are correct from the skill's installed location; the current ../../../../ paths resolve outside the bundle.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; no padding or explanation of concepts Claude already knows, and every section earns its place.	5 / 5
Actionability	Provides concrete, copy-paste-ready `make` commands with exact arguments plus concrete acceptance criteria covering common cases.	5 / 5
Workflow Clarity	Clear numbered 5-step sequence with validation commands (agent-report, agent-ci-gate), but lacks an explicit validate->fix->retry feedback loop for potentially destructive config/backend/auth changes.	4 / 5
Progressive Disclosure	Good section structure with one-level-deep 'Must Read' references, but all three referenced files are missing from the bundle, so navigation is broken in practice.	3 / 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.

A strong, specific description with explicit what-and-when guidance and a well-scoped niche. Slight room to soften internal jargon into more user-natural trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates multiple concrete surfaces (pages/components, backend handlers, console persistence, auth/session flows, user-visible routing metadata) with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Modifies dashboard frontend or backend surfaces...') and when via a concrete 'Use when changing...' clause with specific triggers.	5 / 5
Trigger Term Quality	Good natural-term coverage ('dashboard pages or components', 'backend handlers', 'auth or session flows'), but leans on internal jargon ('console persistence', 'router behavior') and misses some common synonyms.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (dashboard platform surfaces for router console UI) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: vllm-project/semantic-router
Path: tools/agent/skills/dashboard-platform-change/SKILL.md
Commit: e73c772

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.