signal-end-to-end

Implements end-to-end signal changes spanning router config, signal extraction, CLI schema, optional bindings, router-owned metadata headers, and E2E test coverage. Use when adding a new signal type, changing signal configuration or extraction logic, updating CLI schema for signal parameters, or modifying router-owned signal metadata contracts.

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 coordination skill with concrete make commands and a clear validated workflow. The main gaps are the absence of an explicit error-recovery feedback loop and high-level ("as needed") guidance in a couple of workflow steps.

Suggestions

Add an explicit feedback loop after the agent-ci-gate step, e.g. "If the gate reports contract mismatches, fix the flagged surfaces and re-run agent-ci-gate until it passes."

Tighten the high-level workflow steps (e.g. step 2 "Modify... as needed") by naming the specific files or surfaces to edit, or by linking to the relevant Must Read doc per step.

Confirm the Must Read doc paths resolve from the skill location, or move them into a local references/ bundle so the progressive-disclosure references are self-contained and verifiable.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout: short Trigger bullets, a compact numbered Workflow, dense Gotchas packed with concrete identifiers, and no padding or explanations of concepts Claude already knows, matching the 5 anchor for token efficiency.	5 / 5
Actionability	Concrete copy-paste commands ("make agent-report ENV=cpu CHANGED_FILES=\"...\"", "make agent-ci-gate CHANGED_FILES=\"...\"") anchor the skill, but several workflow steps stay high-level ("Modify signal config, extraction, CLI schema, and dashboard surfaces as needed"), leaving minor gaps versus the 5 anchor.	4 / 5
Workflow Clarity	A clear six-step sequence includes an explicit validation checkpoint ("Run make agent-ci-gate... to validate signal contract alignment") and verification steps (5, 6), but there is no explicit error-recovery feedback loop (e.g. "if the gate fails, fix and re-run"), keeping it below 5.	4 / 5
Progressive Disclosure	Sections (Trigger, Workflow, Gotchas, Must Read, Standard Commands, Acceptance) are well organized and the "Must Read" references are clearly signaled and one level deep, but the referenced paths point outside the skill bundle (no references/scripts/assets exist) and cannot be verified, a minor organization gap below 5.	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, explicit description with clear what/when structure and a distinct technical niche. It could be improved by converting the abstract "Implements changes spanning" framing into discrete verbs and adding a couple of natural-language trigger synonyms.

Dimension	Reasoning	Score
Specificity	"Implements end-to-end signal changes spanning router config, signal extraction, CLI schema, optional bindings, router-owned metadata headers, and E2E test coverage" lists six concrete surfaces with comprehensive coverage, but the governing verb ("Implements changes spanning") is somewhat abstract rather than enumerating discrete actions, so it sits below the 5 anchor.	4 / 5
Completeness	It explicitly answers both "what" (the spanning change surfaces) and "when" via a concrete "Use when..." clause with multiple trigger phrases, matching the 5 anchor; it is not a 4 because the when-guidance is specific rather than merely present.	5 / 5
Trigger Term Quality	"Use when adding a new signal type, changing signal configuration or extraction logic, updating CLI schema for signal parameters, or modifying router-owned signal metadata contracts" gives good multi-scenario keyword coverage, but the terms are uniformly technical with no natural synonyms or simpler phrasings, falling short of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear niche (end-to-end signal changes across router config, extraction, CLI schema, metadata headers) with triggers specific to that domain, giving minimal overlap with other 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/signal-end-to-end/SKILL.md
Commit: adc7455

Reviewed: 5 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.