plugin-end-to-end

Implements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.

Quality

85%

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

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 tight, well-structured process skill with concrete validation commands and clear sequencing. Weakest spots are the abstract core-modification step, the missing error-recovery loop, and Must Read references that point to non-existent paths.

Suggestions

Add a brief feedback loop after `make agent-ci-gate` describing what to do when it fails (e.g., read the report, fix the flagged surface, re-run the gate) to lift workflow_clarity toward 5.

Make the core modification step more actionable by pointing to where plugin config schema and execution semantics live, or by linking a concrete editing reference.

Fix or verify the Must Read links under tools/agent/docs/ so the referenced files actually resolve, improving navigation reliability for progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows; every section (Trigger, Workflow, Gotchas, Must Read, Standard Commands, Acceptance) is purposeful and every token earns its place.	5 / 5
Actionability	Provides concrete executable commands ("make agent-report ENV=cpu CHANGED_FILES=...", "make agent-ci-gate", "make agent-feature-gate"), but the core modification step ("Modify plugin config schema, execution semantics, or chain behavior") stays abstract, leaving a minor gap below the copy-paste 5-anchor.	4 / 5
Workflow Clarity	A clear 5-step sequence with explicit validation checkpoints (agent-report identifies impacted surfaces, agent-ci-gate validates constraints), but it lacks an explicit error-recovery feedback loop (what to do when the gate fails), so it does not reach the 5-anchor.	4 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled one-level-deep "Must Read" reference list, but the referenced paths (../../../../tools/agent/docs/*.md) do not resolve to real files, a minor navigation gap below the 5-anchor.	4 / 5
	Total	17 / 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, well-scoped description that explicitly covers both capabilities and trigger conditions for plugin end-to-end work. Slight room to convert enumerated surfaces into distinct active verbs and add a couple of natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete surfaces ("router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage"), but the actions are enumerated as areas under one verb ("Implements... spanning") rather than multiple distinct verbs, so it sits just below the comprehensive 5-anchor.	4 / 5
Completeness	Clearly states what it does ("Implements end-to-end plugin changes spanning...") and gives an explicit "Use when..." clause with concrete trigger phrases, matching the 5-anchor for both what and when.	5 / 5
Trigger Term Quality	The "Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata" clause covers multiple natural trigger phrases a plugin developer would say, but leans technical with no synonyms or file extensions, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear plugin end-to-end niche with distinct, specific triggers (plugin type/schema/semantics/chain/metadata), giving minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 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/plugin-end-to-end/SKILL.md
Commit: d8b03e3

Reviewed: ~1 hour 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.