CtrlK
BlogDocsLog inGet started
Tessl Logo

character-animation-qa

Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.

60

Quality

70%

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/character-animation-qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A concise, well-organized QA skill with a clear review sequence and decision framework, but several review layers describe checks rather than providing executable commands or schemas, which limits actionability and per-step validation clarity.

Suggestions

Make each review layer actionable: add an ffprobe command template for the MP4 check and a concrete frame-comparison method (e.g. sampled frame diff threshold or an ffmpeg select/extract command) for the motion check.

Specify what 'schema validation' means concretely — name the expected schema files or fields for character design, rig plan, pose library, and action timeline, or point to where they are defined.

Insert explicit per-layer pass/fail checkpoints so the reviewer validates each layer before advancing, rather than only applying Pass/Revise/Fail at the end.

DimensionReasoningScore

Conciseness

The body is lean — numbered review layers, a short Playwright snippet, and a Pass/Revise/Fail table with no padding or explanation of concepts Claude already knows — so every token earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

The Playwright block is executable, but the other layers only describe checks ("compare sampled frames for non-trivial differences", "ffprobe metadata, duration, resolution") without giving concrete commands or schemas, leaving key details missing.

2 / 3

Workflow Clarity

The six review layers give a clear sequence and the Pass/Revise/Fail section provides an end-of-flow decision, but per-layer validation checkpoints are implicit rather than explicit, matching the 'steps listed but checkpoints missing' anchor.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no bundle files and is organized into clearly labeled sections (Review Layers, Playwright Pattern, Pass/Revise/Fail, Sources), so per the simple-skills note it scores 3 on organization alone.

3 / 3

Total

10

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, distinctive description that names concrete QA actions, but it omits an explicit 'Use when...' trigger clause and leans on technical jargon over the natural terms a user would actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing or validating a character animation render, preview, or final MP4 before presenting it to the user.'

Broaden trigger coverage with natural user terms such as 'animation render', 'video preview', 'MP4', or 'motion review' alongside the technical tool names.

Drop or soften jargon like 'schema checks' and 'ffprobe' in favor of plain-language equivalents (e.g. 'validate rig and timeline data', 'probe final video metadata').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks" — matching the anchor for several specific concrete actions rather than the vague single-domain anchor at 2.

3 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"character animation" is a natural user term, but most triggers are technical jargon ("schema checks", "Playwright", "ffprobe") and common variations like "render", "preview", "video", or "MP4" are missing, so it falls short of the full coverage anchor at 3.

2 / 3

Distinctiveness Conflict Risk

The niche — local character-animation QA combining schema validation, browser preview, and FFmpeg probing — is distinctive and unlikely to trigger for unrelated skills, matching the clear-niche anchor.

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
calesthio/OpenMontage
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.