skill-invocation-router

Design and test explicit human, implicit model or agent, programmatic application, bounded skill-composition, and harness activation policies for an Agent Skill catalog.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./phases/13-tools-and-protocols/25-skill-invocation-and-routing/outputs/skill-invocation-router/SKILL.md

Quality

Content

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

The body is an exemplary lean, actionable overview: an executable command, concrete decision rules, real one-level-deep references, and a crisp boundary note. The only gap is the absence of an explicit validation/retry feedback loop in the workflow, though the skill is non-destructive so this is minor.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~15 lines with no padding and no explanation of concepts Claude already knows; every line is actionable or a sharp boundary statement, matching the 'every token earns its place' anchor.	5 / 5
Actionability	Step 3 gives a fully specified, copy-paste-ready command with every flag enumerated, and steps 4–8 provide concrete per-channel decision rules, satisfying the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	An explicit 8-step sequence with a decision/abstain checkpoint at step 7 is clear, but there is no explicit validate-then-retry feedback loop; because the operation is non-destructive the destructive cap does not apply, placing this just below anchor 5.	4 / 5
Progressive Disclosure	The body is a concise overview with well-signaled, one-level-deep references to real bundle files (references/invocation-model.md, assets/host-policy.json, scripts/simulate_invocation.py), with content appropriately split across model, config, and script — matching the top anchor.	5 / 5
	Total	19 / 20 Passed

Description

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

The description clearly conveys a specialized domain and two concrete actions but is jargon-dense and omits any 'Use when...' trigger guidance, capping completeness and trigger-term quality at the midpoint. It is distinctive but would benefit from explicit activation phrasing.

Suggestions

Add a 'Use when...' clause with natural trigger phrases (e.g., 'Use when a host needs to route skill activations across human, model, agent, application, composition, or harness channels').

Soften jargon by introducing user-natural synonyms such as 'invocation' or 'routing' alongside 'activation policies'.

Broaden the action verbs beyond 'Design and test' (e.g., classify, route, score, abstain) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('activation policies for an Agent Skill catalog') and two concrete actions ('Design and test') but enumerates channel types rather than additional actions, so coverage is not comprehensive — matching anchor 3.	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant niche keywords ('activation policies', 'Agent Skill catalog', human/model/agent/harness) are present, but the language is jargon-heavy and missing natural synonyms a user might say (e.g., 'invocation', 'routing', 'triggering'), fitting anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The skill occupies a clear specialized niche (auditable activation policies for skill catalogs) with minimal conflict risk, though the absence of an explicit trigger phrase keeps it just below anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rohitg00/ai-engineering-from-scratch
Path: phases/13-tools-and-protocols/25-skill-invocation-and-routing/outputs/skill-invocation-router/SKILL.md
Commit: c02ca08

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