CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pose-library-design

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

Quality

79%

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/pose-library-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exemplary lean skill file: concrete pose vocabulary, a copy-adaptable JSON data pattern, a genuine craft principle (holds over continuous animation), and a validation checklist, all in well-organized sections with no wasted tokens. The only gaps are minor: no example of a complete walk cycle and no enumeration of valid transition/easing values.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: compact pose-category lists, a four-beat acting pattern, one JSON example, a short checklist, and source links — no padding and no explanation of concepts Claude already knows ("Do not continuously animate every part. Holds make the acting readable" is craft knowledge, not filler). Matches the level-5 anchor: every token earns its place.

5 / 5

Actionability

Concrete, executable guidance: exact pose names per category ("walk_contact", "walk_passing", "small_o"), a copy-adaptable JSON pose example with real values (rotation -6, hold_frames 18, transition "back.out"), and the rule "Poses name only changed parts; defaults come from the rig". Not level 5 because examples don't cover common cases like a full contact/passing walk cycle, and valid `transition` values are never enumerated — minor gaps consistent with the level-4 anchor.

4 / 5

Workflow Clarity

A coherent implicit sequence exists — enumerate required emotions/actions into poses (categories), apply the pose data pattern, sequence with anticipation -> action -> hold -> settle, then validate via the Quality Checklist, which serves as explicit checkpoints. Not level 5 because the end-to-end process is never laid out as ordered steps and there is no error-recovery guidance; above level 3 because validation checkpoints (the checklist) are explicitly present, not implicit, and this is a design task with no destructive/batch operations to cap the score.

4 / 5

Progressive Disclosure

This is a small, single-purpose skill (~55-line body) with no bundle files (references/, scripts/, assets/ do not exist) and no need for external references; content is appropriately inlined in well-organized sections (Categories, Acting, Data Pattern, Checklist, Sources). The only external links (GSAP Timeline, Remotion interpolate/spring) are clearly labeled under Sources and one level deep — matching the simple-skill case where well-organized sections score 5.

5 / 5

Total

18

/

20

Passed

Description

61%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 is concise, in third person, and names a specific niche with concrete deliverables, but it omits any "Use when..." trigger clause, capping completeness at 3 and slightly weakening trigger discoverability. It is distinct from other skills and free of fluff or over-claims.

Suggestions

Add an explicit trigger clause, e.g., "Use when creating pose libraries, character animation assets, or expression sets for a 2D rig" — this would raise completeness from 3 to 4-5.

Include natural synonyms users might say, such as "walk cycles", "expressions", or "character poses", to improve trigger term coverage toward level 5.

Consider naming the artifact format or tool context (e.g., the rig/data format poses target) so the description better distinguishes itself from general animation-timing skills.

DimensionReasoningScore

Specificity

"Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation" names the domain and several concrete deliverables (pose libraries, action cycles, expression states) but relies on a single generic action verb ("Design"), unlike the level-4 anchor which lists several distinct actions ("Extracts text... fills forms, converts pages"). Not level 2 because it is far more concrete than "Processes PDF files"; not level 4 because there is only one action, not several specific actions with minor gaps.

3 / 5

Completeness

It clearly answers "what" (design pose libraries, action cycles, expression states) but has no "when" — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Matches the level-3 anchor (clear what, when missing) exactly; not level 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Contains natural keywords a user would say — "2D character", "pose libraries", "animation", "expression states" — matching the level-4 anchor of good keyword coverage with a few natural terms missing (e.g., "walk cycle", "expressions", "keyframes", "sprite animation"). Not level 5 because it lacks synonyms and common variations of the core terms; not level 3 because coverage goes beyond merely relevant keywords with several distinct natural phrases.

4 / 5

Distinctiveness Conflict Risk

The niche — 2D character pose data for data-driven animation — is quite distinct from typical file/document/code skills, giving minimal conflict risk with most skills. Not level 5 because adjacent creative/animation skills (general animation timing, character rigging, sprite tools) could plausibly overlap given no explicit triggers; clearly above level 3's "could still overlap with similar skills" since the domain is narrowly defined.

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

calesthio/OpenMontage

Path

.agents/skills/pose-library-design/SKILL.md

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.