CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-chain-change

Modifies the local startup chain including image build, container serve/bootstrap logic, and canonical smoke test behavior. Use when changing `vllm-sr serve` behavior, image selection or pull policy, container startup sequences, local Docker/Make bootstrap, or canonical smoke config.

71

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 tight, actionable skill body with concrete commands, a clear sequenced workflow, and clean reference signaling. The main improvement would be adding an explicit failure-handling feedback loop in the workflow for startup-chain changes.

Suggestions

Add an explicit feedback loop after the validate step (e.g. 'If agent-feature-gate fails, fix the startup change and re-run agent-feature-gate before proceeding').

Show at least one concrete CHANGED_FILES example value so the command form is unambiguous on first use.

Clarify how the 'Must Read' docs relate to each workflow step (e.g. note which step consumes environments.md vs testing-strategy.md) to strengthen navigation.

DimensionReasoningScore

Conciseness

Lean bullet structure with no over-explanation of concepts Claude already knows (Docker, Make, smoke tests); every section earns its place.

5 / 5

Actionability

Provides copy-paste-ready commands with concrete parameters ('make agent-report ENV=cpu|amd CHANGED_FILES="..."', 'make agent-feature-gate ENV=cpu|amd CHANGED_FILES="..."') covering the common cases.

5 / 5

Workflow Clarity

Clear 5-step sequence with validation checkpoints (agent-feature-gate 'validate', step 5 verify, plus Acceptance criteria), but lacks an explicit 'if validation fails, fix and re-run' feedback loop for an infra/startup change skill.

4 / 5

Progressive Disclosure

Well under 50 lines with well-organized sections and clearly signaled one-level-deep references in 'Must Read'; no bundle files exist, so structure is appropriate with only minor organization gaps.

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, well-scoped description that clearly states what it does and when to use it with concrete trigger phrases. It is third-person and largely free of fluff; minor gains are possible by varying the action verbs and adding a couple of plainer trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete sub-areas ('image build, container serve/bootstrap logic, and canonical smoke test behavior'), but uses a single verb 'Modifies' rather than enumerating distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Modifies the local startup chain including...') and when ('Use when changing...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when changing' clause covers natural triggers ('image selection or pull policy', 'container startup sequences', 'local Docker/Make bootstrap', 'canonical smoke config') with good synonym coverage, though some terms like 'vllm-sr serve' lean technical and a few plain variations are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (local startup chain) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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