CtrlK
BlogDocsLog inGet started
Tessl Logo

smart-router-skill

Movie character personality skill with configurable missions - choose your character and watch themed workflows unfold

48

Quality

50%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/smart-router-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The skill body is highly actionable with concrete commands, but it is padded with redundant marketing-style sections, large inline example dumps, and references to files that do not exist in the bundle. Workflow sequencing is clear but lacks validation, and progressive disclosure is undermined by inlined detail and inconsistent paths.

Suggestions

Cut the redundant "What This Demonstrates", "Key Concepts", and "Why This Matters" sections, which restate the same config-driven point three times, and trim the large example-output dumps to a single representative block.

Add a validation/error-recovery step to the workflow (e.g., what to do if the character or mission is invalid, or if router.sh exits non-zero).

Reconcile referenced paths with the actual bundle: either add the missing router.sh and config/personality-config.json, or correct the paths so navigation is trustworthy; consider moving the full example outputs into a separate reference file.

DimensionReasoningScore

Conciseness

The body is padded with repeated restatements of the same idea ("Simple config = different behavior" appears in "What This Demonstrates", "Key Concepts", and "Why This Matters"), large example-output dumps, and explanations of concepts Claude already knows (how config files and scripts work). Not score 2 because the verbosity is pervasive, not a few stray lines; clearly above the efficiency bar the rubric rewards.

1 / 3

Actionability

It provides concrete, copy-paste-ready commands (`bash router.sh --character yoda --mission 2`) and a specific edit instruction ("Change `"mission": 1` to `"mission": 2`") plus a numbered "How it works" breakdown. Not score 2 because the guidance is executable and specific rather than pseudocode; stays at 3 as the commands are fully actionable.

3 / 3

Workflow Clarity

The interactive flow (ask character -> present options -> run router.sh -> display output) and a numbered "How it works" list are sequenced, but there are no validation checkpoints or error-recovery feedback loops. Not score 3 because checkpoints/feedback loops are missing; not score 1 because the sequence is clearly present and unambiguous for this simple skill.

2 / 3

Progressive Disclosure

The actual bundle has three one-level-deep workflow scripts, but the body inlines large example-output blocks and full architecture that could be separate, and it references router.sh and config/personality-config.json which are missing from the bundle. Not score 3 because inlined detail and missing referenced paths break clean navigation; not score 1 because there is real structure rather than a monolithic wall of nested references.

2 / 3

Total

8

/

12

Passed

Description

50%

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 conveys a distinct, fun niche but reads as marketing copy rather than a precise capability statement, and it omits any explicit "when to use" trigger guidance. It sits firmly at the middle of the scale across all dimensions.

Suggestions

Rewrite the description in third-person imperative voice listing concrete actions (e.g., "Embodies movie characters and runs character-specific themed workflow scripts based on a config file").

Add an explicit trigger clause, e.g., "Use when the user wants to roleplay as a movie character or see a demo of config-driven skill routing."

Replace marketing fluff ("watch themed workflows unfold", "watch the magic happen") with concrete, natural keywords users would actually say.

DimensionReasoningScore

Specificity

It names the domain ("Movie character personality skill") and some actions ("choose your character", "configurable missions"), but the actions are weak and padded with marketing phrasing ("watch themed workflows unfold") rather than concrete capabilities. Not score 3 because no multiple specific concrete actions are listed; not score 1 because a domain and some actions are named.

2 / 3

Completeness

The "what" is partially stated (a movie character personality skill) but the "when" is only implied, with no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2. Not score 3 because explicit triggers are absent; not score 1 because the what is present.

2 / 3

Trigger Term Quality

Terms like "movie character", "personality", and "character" are somewhat natural, but "configurable missions" and "themed workflows" are skill-internal jargon rather than phrasing a user would naturally say. Not score 3 because common user variations are missing; not score 1 because some relevant natural keywords are present.

2 / 3

Distinctiveness Conflict Risk

The "movie character personality" niche is somewhat distinct, but with no explicit triggers it could still overlap with other personality/demo skills. Not score 3 because distinct triggers are missing; not score 1 because the niche is not generically broad like "code and documents".

2 / 3

Total

8

/

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
darrenhinde/OpenAgentsControl
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.