CtrlK
BlogDocsLog inGet started
Tessl Logo

video-template-frame-pentagram-stat

Use this plugin when the user wants a "Pentagram Stat Frame" HyperFrames motion video — Swiss-grid statistic anchor — giant number, red accent, growing bars, black data bar. Rational and editorial.

54

Quality

61%

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 ./plugins/_official/video-templates/frame-pentagram-stat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 admirably concise and well-structured for a simple template skill, but actionability stops at file references without executable commands, and the workflow lacks explicit validation before rendering, which caps both dimensions.

Suggestions

Add a concrete, copy-paste render command (e.g., the html-video/HyperFrames CLI invocation with format/aspect flags) to make the render step executable.

Insert an explicit validation checkpoint before render (e.g., 'Open source/index.html in a headless browser and confirm layers animate; only then render to MP4') to lift workflow clarity.

List the bundled files under source/ (e.g., index.html, styles, gsap timeline) so the reference structure is explicitly navigable for progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it states the format, best-for uses, and a tight 4-step workflow with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Steps name concrete files and constraints ('Read source/index.html', 'Render to MP4 via the html-video / HyperFrames renderer'), but there is no executable command or code, and the render step lacks a specific invocation, leaving guidance high-level.

3 / 5

Workflow Clarity

A clear 4-step sequence is present, but there is no explicit validation or verification checkpoint before the destructive/headless render step, and the rubric caps render-style batch output without validation at 3.

3 / 5

Progressive Disclosure

The skill is short and well-sectioned, and it points to a bundled source/ directory, but the references are not explicitly signaled as navigable files (no paths listed beyond source/index.html) and no bundle file listing is provided to confirm structure, leaving organization only partially realized.

3 / 5

Total

14

/

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 distinctive for a niche video template, with an explicit 'when' trigger, but it leans on descriptive visual attributes rather than enumerated concrete actions and lacks the synonym/term breadth of stronger descriptions.

Suggestions

Add concrete actions a user would request (e.g., 'renders a statistic anchor video to MP4/WEBM at 16:9, 1:1') to lift specificity.

Broaden trigger terms with natural synonyms users might say (e.g., 'stat frame', 'data reveal video', 'metric animation') to improve trigger term quality.

Expand the 'when' clause with multiple concrete scenarios (editorial data slide, hero metric reveal) to push completeness toward 5.

DimensionReasoningScore

Specificity

It names the domain ('Pentagram Stat Frame' HyperFrames motion video) and a few concrete visual elements (giant number, red accent, growing bars, black data bar), but does not enumerate specific user-facing actions like extract or fill; coverage is domain-descriptive rather than action-comprehensive.

3 / 5

Completeness

There is a clear 'what' (a HyperFrames motion video composition with specified visual signature) and a 'when' clause ('Use this plugin when the user wants...'), but the 'when' is a single narrow scenario without elaborated trigger phrases, capping it at the lower end.

3 / 5

Trigger Term Quality

It includes a natural trigger ('when the user wants a ... video') and recognizable phrases (statistic frame, growing bars), but lacks common synonyms or file/format terms a user would naturally say, so keyword coverage is only partial.

3 / 5

Distinctiveness Conflict Risk

The highly specific template name and visual signature make it clearly distinguishable from generic skills, with only minor overlap risk against other HyperFrames video templates in the same family.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.