hyperframes-core

Apply the core composition, timing, media, and determinism contract used by iPollo Video.

Quality

59%

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-core/SKILL.md

Quality

Content

65%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 content is exceptionally lean and well-structured for a simple, single-purpose skill, earning top marks for conciseness and progressive disclosure. Its weakness is actionability and workflow clarity: the rules are abstract directives without concrete executable steps or an explicit validation feedback loop.

Suggestions

Add concrete, executable guidance for each rule (e.g., specific commands or APIs for validating determinism, or how to check timing consistency) to raise actionability.

Expand step 5 into an explicit validation procedure with a validate -> fix -> retry feedback loop, since editing project structure is a potentially destructive operation.

Reframe the numbered items as a sequenced workflow (inspect composition -> synchronize timing -> verify media references -> render-check determinism -> validate) so the sequence and checkpoints are explicit rather than implicit.

Dimension	Reasoning	Score
Conciseness	The body is five short numbered rules with no padding and no over-explanation of concepts Claude already knows (composition, timeline, rendering), so every token earns its place.	5 / 5
Actionability	The rules are high-level directives ("Keep one authoritative composition", "Maintain consistent...timing", "validate before completion") that state what to preserve but lack concrete executable steps, commands, or specific mechanisms, fitting the minimal-guidance anchor.	2 / 5
Workflow Clarity	The five numbered items are listed but read as principles rather than a sequenced process, and step 5 mentions validation without specifying how to validate or any error-recovery loop; since the skill edits project structure (potentially destructive), the missing validation detail caps this at 3.	3 / 5
Progressive Disclosure	This is a sub-50-line, single-purpose skill with no need for external references (no bundle files present), and its single header plus numbered list is well-organized, so the simple-skill exception allows a top score.	5 / 5
	Total	15 / 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 concise and names a specific product niche with concrete domain aspects, giving it reasonable distinctiveness. However, it lacks an explicit "Use when..." trigger clause and uses a single generic action verb, capping completeness and limiting specificity.

Suggestions

Add an explicit trigger clause such as "Use when editing the structure of an active iPollo Video project" to lift completeness above 3.

Replace the generic verb "Apply" with 2-3 concrete actions (e.g., "compose timelines, synchronize media, and validate deterministic rendering") to raise specificity.

Include natural synonyms or phrasings users actually say (e.g., "iPollo Video project", "timeline editing", "render validation") alongside the technical terms to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	The phrase "Apply the core composition, timing, media, and determinism contract" names the domain and enumerates several concrete aspects (composition, timing, media, determinism), but the single action verb "Apply" is generic rather than a list of concrete actions, fitting the 1-2 concrete actions anchor.	3 / 5
Completeness	The description gives a clear "what" (apply the core composition/timing/media/determinism contract) but includes no "Use when..." clause or explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Terms like "composition", "timing", "media", and the product name "iPollo Video" are relevant domain keywords a user might say, but "determinism contract" is jargon and common synonyms or variations are absent.	3 / 5
Distinctiveness Conflict Risk	The explicit product name "iPollo Video" carves out a clear niche with low overlap risk, but the trigger phrasing is less crisp than the anchor-5 example that pairs the niche with explicit "Use when" triggers, placing it just below 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-core/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.