CtrlK
BlogDocsLog inGet started
Tessl Logo

media-use

Find, generate, process, and reuse media through the active iPollo Video session's media services.

60

Quality

68%

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 ./.agents/skills/media-use/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a concise, well-structured overview with a clear sequenced workflow and an explicit verification step, scoring well on conciseness and progressive disclosure. Its main weakness is actionability: the steps describe what to do in general terms without naming the specific providers, tools, commands, or APIs Claude should use.

Suggestions

Add concrete specifics to the action steps — name the actual media providers/tools exposed by the session and example commands or API calls for generating and importing media.

Add a brief feedback loop after the verification step describing what to do when format, duration, dimensions, or timeline placement checks fail (e.g., re-encode, re-time, or regenerate).

DimensionReasoningScore

Conciseness

The body is six lean lines with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor; not 4 because there are no instances of over-explanation to trim.

5 / 5

Actionability

It provides a clear sequenced directive list with one concrete verification checklist ("Verify format, duration, dimensions, and timeline placement"), but the steps are high-level hints ("Use the media providers and credentials exposed by the active session") with no specific tools, commands, or APIs named, matching the 'some concrete guidance but incomplete; missing key details' anchor; not 4 because no executable specifics are given, and not 2 because the guidance is more than minimal hints.

3 / 5

Workflow Clarity

Five numbered steps form a clear sequence and step 5 is an explicit verification checkpoint before completion, matching the 'clear sequence with most checkpoints present' anchor; not 5 because there is no feedback loop describing what to do if verification fails, and not capped at 3 because a validation step is present.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (no bundle files exist), and is well-organized with a heading, an intro trigger sentence, and a numbered list, satisfying the simple-skill exception for a top score; not 4 because there are no organization gaps to flag.

5 / 5

Total

17

/

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 gives a clear, moderately specific statement of what the skill does and ties it to a distinct product context, but it lacks an explicit 'Use when...' trigger clause in the description field itself and has limited keyword coverage. Adding natural trigger terms and a usage clause would raise completeness and trigger quality.

Suggestions

Append a 'Use when...' clause to the description naming concrete trigger situations (e.g., 'Use when the current video needs images, footage, audio, narration, or captions').

Expand keyword coverage in the description to include natural synonyms users would say (images, footage, audio, narration, captions) rather than only the generic term 'media'.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Find, generate, process, and reuse media") scoped to a specific service, matching the 'several specific actions; minor gaps' anchor; not 5 because the domain 'media' is broad and no specific formats/operations are enumerated, and not 3 because it does name multiple distinct actions.

4 / 5

Completeness

It states a clear 'what' ("Find, generate, process, and reuse media through the active iPollo Video session's media services") but the description field itself lacks any 'Use when...' trigger clause, so per the boundary guidance a missing explicit trigger caps completeness at 3; not 2 because the 'what' is clearly articulated rather than vague.

3 / 5

Trigger Term Quality

The description contains the relevant keyword 'media' plus the product context 'iPollo Video session' but omits the natural variations (images, footage, audio, narration, captions) that appear only in the body, matching the 'some relevant keywords but missing common variations' anchor; not 4 because keyword coverage is essentially limited to the single term 'media'.

3 / 5

Distinctiveness Conflict Risk

Scoping to 'the active iPollo Video session's media services' gives it a clear product-specific niche with only minor overlap risk against general media skills, matching the 'mostly distinct' anchor; not 5 because the broad term 'media' still invites some overlap with other media-related skills.

4 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Devin-AXIS/iPolloWork
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.