CtrlK
BlogDocsLog inGet started
Tessl Logo

od-default

Hidden fallback scenario for free-form Home prompts. Ask the task type first, then continue through the matching Open Design flow.

58

Quality

67%

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 ./plugins/_official/scenarios/od-default/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 tight, actionable router: a concrete prefilled question form plus an explicit task-type routing table with clear turn boundaries and guardrails. It assumes Claude's competence, avoids concept padding, and is well-organized with no nested references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; the surrounding prose is tight and the large HTML/JSON block is the actual artifact to emit rather than explanatory padding, matching the 'lean and efficient; every token earns its place' anchor. It does not explain concepts Claude already knows, so it is above the 2 anchor.

3 / 3

Actionability

It provides a complete, copy-paste-ready question form and a concrete per-taskType routing decision table, which is fully executable guidance rather than vague direction, matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The two-turn sequence is explicit with a hard checkpoint ('then stop. Do not write files, use tools, or start planning until the user answers') and clear guardrails (do not emit a second discovery form); since this routing involves no destructive or batch operation, the missing retry loop does not cap the score.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and clear sections ('Turn 1', 'After the answer'); references to other workflows are delegate-by-name rather than nested file chains, so organization is clean and one-level-deep, matching the well-organized anchor.

3 / 3

Total

12

/

12

Passed

Description

35%Weight 40%Scale 1-3

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 what the fallback router does but relies on internal jargon rather than natural user trigger terms and lacks an explicit 'Use when...' clause, capping completeness and trigger quality. It is reasonably specific to its niche but overlaps with the Open Design workflows it delegates to.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user submits a free-form Home prompt without selecting a category chip', to lift completeness and trigger_term_quality.

Replace internal jargon ('Open Design flow', 'free-form Home prompts') with phrasing closer to what a user would actually say so trigger_term_quality can reach 3.

List a couple more concrete routing actions (e.g. 'routes to prototype, live artifact, deck, image, or video workflows') to move specificity from 2 to 3.

DimensionReasoningScore

Specificity

Names the domain ('free-form Home prompts', 'Open Design flow') and a couple of actions ('Ask the task type first', 'continue through the matching Open Design flow'), but does not list multiple specific concrete actions, so it sits at the 'names domain and some actions' anchor rather than the comprehensive 3.

2 / 3

Completeness

It clearly states what the skill does (fallback router that asks the task type and routes), but the 'when' is only implied by 'for free-form Home prompts' with no explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

Terms like 'free-form Home prompts' and 'Open Design flow' are internal plugin/system jargon rather than natural phrases a user would say, and there is no 'Use when...' trigger clause, matching the 'no natural keywords; technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

'Hidden fallback scenario for free-form Home prompts' carves out a fairly specific niche, but because it routes into the same Open Design workflows other skills handle, it could still overlap with similar skills, matching the 'somewhat specific but could overlap' anchor.

2 / 3

Total

7

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.