CtrlK
BlogDocsLog inGet started
Tessl Logo

pose-library-design

Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 single-purpose skill with concrete data patterns and a useful checklist. It is already strong; no bundle files exist and none are needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanation of what animation or rigging is, and the single JSON example earns its tokens, matching the score-3 anchor.

3 / 3

Actionability

It gives concrete pose categories, an explicit pose-data JSON schema with real fields, and a defined acting sequence pattern — fully actionable guidance rather than abstraction.

3 / 3

Workflow Clarity

The 'anticipation -> action -> hold -> settle' sequence plus a Quality Checklist acting as validation checkpoints give a clear process; the simple-skill note allows 3 here.

3 / 3

Progressive Disclosure

A self-contained, well-organized skill under 50 lines with clearly labeled sections and only one-level external source links, satisfying the simple-skill allowance for a score of 3.

3 / 3

Total

12

/

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.

The description is specific and distinctive but lacks any 'Use when...' trigger guidance, leaving the user with no explicit signal for when to invoke it. Adding a trigger clause would lift completeness and trigger_term_quality.

Suggestions

Append a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user asks for character pose libraries, action cycles, or expression states for data-driven animation.'

Add common user-facing terms (e.g. 'character poses', 'animation cycle', 'expression set') alongside the technical vocabulary.

Keep the current concrete capability list but pair it with explicit invocation triggers to satisfy the 'what AND when' requirement.

DimensionReasoningScore

Specificity

Lists multiple concrete targets — '2D character pose libraries, action cycles, and expression states' — rather than vague actions, matching the score-3 anchor.

3 / 3

Completeness

It clearly answers 'what' (design pose libraries/cycles/states) but omits any 'when to use it' trigger; the rubric caps this at 2 when trigger guidance is missing.

2 / 3

Trigger Term Quality

Domain terms like 'pose libraries', 'action cycles', and 'expression states' are relevant, but no 'Use when...' clause or natural phrasings a user would actually say are present, matching 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The narrow niche of '2D character pose libraries... for data-driven animation' is highly specific and unlikely to overlap with unrelated skills.

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.