CtrlK
BlogDocsLog inGet started
Tessl Logo

hyperframes-cli

Inspect, validate, preview, and render the active iPollo Video project with its bundled HyperFrames CLI.

58

Quality

66%

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/hyperframes-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 clear workflow and verification step, but it provides no concrete executable command syntax, relying on abstract directives that leave Claude to guess the actual CLI invocation.

Suggestions

Add at least one concrete example command line for the inspect/validate/preview/render actions (e.g. the actual CLI invocation with key flags).

Make the validation checkpoint explicit by naming the verify command Claude must run before reporting success.

Specify what 'bounded' validation/preview/render means in practice (e.g. flags or scope limits) so the guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is five tight numbered imperatives with no padding and no explanation of concepts Claude already knows — every token earns its place, matching the lean-and-efficient anchor 5.

5 / 5

Actionability

It only gives high-level directives ('Use bounded validation, preview, or render commands', 'Do not install global packages') with no concrete command syntax, flags, or examples, fitting anchor 2 rather than the pseudocode/incomplete anchor 3.

2 / 5

Workflow Clarity

A clear five-step sequence with an implicit validate-fix-retry loop (step 4) and an explicit verification report (step 5) avoids the destructive/batch cap, but checkpoints are loosely worded, matching anchor 4 rather than the explicit-validation anchor 5.

4 / 5

Progressive Disclosure

A simple single-purpose skill under 50 lines with a single heading and a well-organized numbered list and no external references needed, which per the simple-skills note scores 5.

5 / 5

Total

16

/

20

Passed

Description

62%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 clearly niche-scoped to the iPollo Video HyperFrames CLI, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and leaves trigger-term coverage incomplete.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when the user wants to inspect, validate, preview, or render an iPollo Video project.'

Include common synonyms or file extensions (e.g. .hyperframes, project file) to broaden natural keyword coverage.

Mirror one or two of the concrete actions as natural phrasings a user would actually say to improve trigger_term_quality.

DimensionReasoningScore

Specificity

Names the domain (iPollo Video / HyperFrames CLI) and lists several specific concrete actions — 'Inspect, validate, preview, and render' — with only minor gaps in coverage, fitting anchor 4 rather than the comprehensive-coverage anchor 5 or the 1-2-action anchor 3.

4 / 5

Completeness

It has a clear 'what' but no 'Use when...' trigger clause, so per the judging guideline a missing explicit trigger caps completeness at anchor 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ('inspect', 'validate', 'preview', 'render', 'project') but common synonyms and file extensions are missing and 'iPollo Video'/'HyperFrames CLI' are product-specific jargon, matching the some-keywords-but-missing-variations anchor 3.

3 / 5

Distinctiveness Conflict Risk

It targets a clear niche (the active iPollo Video project and its bundled HyperFrames CLI) with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Devin-AXIS/iPolloWork
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.