CtrlK
BlogDocsLog inGet started
Tessl Logo

od-media-generation

Default reference pipeline for image, video, and audio projects — routes through media-image / media-video / media-audio atoms based on the project kind, wraps the output in a live artifact, and devloops on critique-theater until the score converges.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/scenarios/od-media-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a tight, well-structured scenario manifest with concrete atom-selection rules, a save/wrap sequence, and an explicit critique feedback loop. It is held at 4 across the board by minor over-explanation, the absence of a sample atom payload, implicit validation delegation, and a body just over the simple-skill line.

Suggestions

Add one concrete example of the media-atom call payload (prompt/aspect/provider) so the generate step is copy-paste ready.

Trim incidental over-explanation ('The preview is what the user sees in the right pane', 'whichever comes first').

Spell out the critique-recovery branch inline (what to change in the next prompt when critique.score < 4) rather than relying on the external critique-theater atom.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — a compact jsonc manifest, a terse atom-selection table, and focused prose — with only minor over-explanation such as 'The preview is what the user sees in the right pane' and 'whichever comes first' that could be trimmed, so it sits above the midpoint but short of fully lean.

4 / 5

Actionability

Guidance is concrete and executable for a config skill: explicit atom-selection rules ('metadata.kind === image → media-image'), enumerated aspect ratios, a save path '<cwd>/media/<timestamp>.<ext>', and provider-default guidance, with only minor gaps (no example of the actual media-atom call payload).

4 / 5

Workflow Clarity

Stages are clearly sequenced (discovery → plan → generate → critique) with an explicit repeat/until termination condition and a feedback loop ('Use the critique notes to drive the next media call's prompt'), but the validation/recovery branch is delegated to critique-theater rather than spelled out as an inline checkpoint, leaving it just below the explicit-validation anchor.

4 / 5

Progressive Disclosure

The body is well-organized into clearly signaled sections (Default pipeline, Atom call shape, Critique loop, Replace do not extend) and is self-contained with no nested references, but at ~65 lines it slightly exceeds the under-50-line simple-skill threshold that would let it score 5 on sectioning alone.

4 / 5

Total

16

/

20

Passed

Description

58%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 states a clear 'what' with several concrete (if jargon-heavy) actions, but lacks an explicit 'Use when...' trigger clause and leans on internal terminology rather than natural user phrases. Completeness is capped at 3 by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when generating images, video, or audio for a media-typed project.'

Surface user-facing synonyms (generate, render, make a picture/video, create audio) alongside the internal atom names.

Lead with the user-visible outcome before the routing/wrapping mechanics so the value is clear to a non-expert.

DimensionReasoningScore

Specificity

Names the domain ('image, video, and audio projects') and several concrete actions — 'routes through media-image / media-video / media-audio atoms', 'wraps the output in a live artifact', 'devloops on critique-theater' — but the actions lean on product jargon rather than user-facing verbs, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear (default pipeline that routes, wraps, and devloops), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'for image, video, and audio projects', which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The only natural terms are 'image', 'video', and 'audio projects'; the rest ('atoms', 'live artifact', 'critique-theater', 'devloops') is internal jargon a user would never say, and common variations like 'generate/make a picture', 'render', 'create audio' are missing.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (default media-generation pipeline scoped to image/video/audio with named atoms), so it is mostly distinct with only minor overlap risk against other media-handling skills; it is not a level-5 because the trigger phrasing is not uniquely distinctive.

4 / 5

Total

14

/

20

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.