CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-native-escalation-routing

Use when choosing native or multi-LLM handling for init, review, or security requests

72

Quality

87%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized routing policy with concrete decision criteria and examples, scoring top marks across all content dimensions. It appropriately assumes Claude's competence without padding.

DimensionReasoningScore

Conciseness

The body is lean and sectioned into short bullet lists with concrete example phrases, with no padding explaining concepts Claude already knows.

3 / 3

Actionability

Provides a concrete all-true checklist for Claude-native routing, explicit escalation triggers, and example user phrases; as an instruction-only skill the absence of code is not penalized since the policy guidance is specific and actionable.

3 / 3

Workflow Clarity

A clear two-branch routing decision with explicit tie-breaking rules for ambiguity and explicit /octo:* invocations; no destructive or batch operations require validation checkpoints.

3 / 3

Progressive Disclosure

A self-contained, well-organized sub-skill with clear sections and no bundle files; the only reference (codex-host-adapter.md) is an external host path rather than a nested bundle reference.

3 / 3

Total

12

/

12

Passed

Description

75%

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 has an explicit 'Use when...' trigger and a clear niche, satisfying completeness and distinctiveness. It is slightly weak on specificity and trigger-term coverage because it frames the skill as a choice and omits common escalation phrasings.

Suggestions

Add concrete verbs (e.g., 'route', 'escalate', 'select between') to raise specificity beyond the current decision framing.

Include natural escalation trigger variations such as 'multiple model opinions', 'adversarial review', or named providers (Codex, Gemini) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('native or multi-LLM handling') and the request types ('init, review, or security'), but frames the skill as a decision ('choosing') rather than enumerating multiple concrete actions.

2 / 3

Completeness

Explicitly answers both what (native vs multi-LLM handling for init/review/security) and when via a direct 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('init, review, or security requests'), but misses common escalation variations like 'multiple model opinions', 'adversarial review', or named providers.

2 / 3

Distinctiveness Conflict Risk

The native-vs-multi-LLM routing niche for init/review/security is a clear, scoped trigger unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.