hyperframes-keyframes

Build seek-safe keyframe animation for the active iPollo Video timeline.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/hyperframes-keyframes/SKILL.md

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 lean and well-structured with a built-in verification step, fitting a compact single-purpose skill. Its weakness is actionability: the rules describe what to ensure but not how to implement it in iPollo Video specifically.

Suggestions

Add tool-specific execution detail for at least the first rule, e.g. which iPollo Video property/API sets a keyframe value at an explicit time.

Expand rule 5 into a brief validate-fix-retry loop (e.g. seek to each boundary; if a value is unstable, pin it and re-seek).

Optionally include one small copy-pasteable snippet or concrete value example to make the rules immediately executable.

Dimension	Reasoning	Score
Conciseness	The body is five terse rules with no padding and no explanation of concepts Claude already knows, matching the "lean and efficient; every token earns its place" anchor; it is tighter than the minor-over-explanation level (rule out 4).	5 / 5
Actionability	Directives like "Express animation from explicit timeline time or progress" and "Verify direct seeking at key boundaries" are concrete-ish guidance but lack the tool-specific execution detail (how to do this in iPollo Video, which API/property calls), matching the "some concrete guidance but incomplete; missing key details" anchor; it is not vague-only (rule out 2) but not mostly-executable (rule out 4).	3 / 5
Workflow Clarity	The numbered 1-5 list gives a clear sequence and rule 5 ("Verify direct seeking at key boundaries and the final frame") provides an explicit validation checkpoint, matching the 4 anchor; it is above steps-with-implicit-checkpoints (rule out 3) but lacks error-recovery feedback loops needed for a 5.	4 / 5
Progressive Disclosure	This is a sub-50-line single-purpose skill needing no external references, and it is well-organized with a clear heading and ordered list, so the simple-skill exception gives it a 5; no nested or buried references exist to pull it down.	5 / 5
	Total	17 / 20 Passed

Description

53%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 specific and product-distinct but stops short of completeness because it omits an explicit "Use when..." trigger clause. Trigger-term coverage is adequate but missing common synonyms. Adding a concrete when-to-use clause would lift the two capped dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when animating keyframes on an iPollo Video timeline or when the user mentions seek-safe animation."

Include natural synonym terms (e.g. "keyframes", "animating", "scrubbing") to broaden trigger-term coverage.

Mention 1-2 more concrete actions (e.g. set/interpolate property values, pin start/end states) to raise specificity.

Dimension	Reasoning	Score
Specificity	"Build seek-safe keyframe animation for the active iPollo Video timeline" names the domain (keyframe animation) plus the specific seek-safe property and timeline target, matching the anchor for 1-2 concrete actions; it is not minimal/generic (rule out 2) nor comprehensive in action coverage (rule out 4+).	3 / 5
Completeness	The description has a clear "what" (build seek-safe keyframe animation) but no "Use when..." trigger clause, so per the missing-trigger-guidance rule completeness is capped at 3; it is above a vague what-only level (rule out 2) but cannot reach 4 without explicit when guidance.	3 / 5
Trigger Term Quality	Natural terms like "keyframe", "animation", and "timeline" plus the product name "iPollo Video" give relevant keywords, but common variations/synonyms are missing, matching the "some relevant keywords but missing variations" anchor; it is above the one-or-two-generic-keywords level (rule out 2) but below good coverage (rule out 4).	3 / 5
Distinctiveness Conflict Risk	The product-specific "iPollo Video timeline" plus "seek-safe keyframe animation" carve a mostly-distinct niche with only minor overlap risk against generic animation skills, matching the 4 anchor; it is more distinct than "somewhat specific" (rule out 3) but lacks explicit trigger phrases that would push it to a clear-niche 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: .agents/skills/hyperframes-keyframes/SKILL.md
Commit: 98deb63

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.