CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-science-case-demo-video

Author the existing video.json screenplay and JavaScript animation bodies for Open-Science Research film. The application provides the session snapshot, model calls, English narration, dynamic HTML playback and optional desktop MP4 export.

Quality

73%

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 ./packages/research-film/resources/authoring/SKILL.md
SKILL.md
Quality
Evals
Security

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 an exceptionally lean, highly actionable constraint set with concrete field names, cue formats, and numeric limits, plus a defined correction loop and clear host/model responsibility split. Its main weaknesses are the absence of any worked example and references to README.md and KIT.md that are not present in the evaluated bundle.

Suggestions

Include README.md and KIT.md in the skill bundle (or inline the essential kit API surface), since the body directs the model to read them for the supported application subset and drawing APIs.

Add one minimal worked example — a single complete scene object with a caption cue and one small matching animation body — so the screenplay and animation rules have a concrete template to follow.

DimensionReasoningScore

Conciseness

The body is dense, imperative constraint prose with zero padding — e.g. "Preserve source quantities and uncertainty; do not invent figures, files or measurements" and "Do not use imports, exports, `require`, filesystem APIs, network calls, wall-clock timers..." — and it never explains concepts Claude already knows. Every token carries a rule, matching the lean anchor 5 rather than anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

Concrete guidance is strong: exact field values ("`version: 1`", "`session: \"session.json\"`"), exact cue formats ("`\"0\"`, `\"0:word\"`, `\"0.end\"`, `\"1+0.4\"` or `\"end-1\"`"), and hard numeric bounds (5–8 scenes, 130–180 words, at most 16 files, 65,536 bytes per file). It falls short of fully copy-paste-ready because no worked example of a scene object or animation body is included, and the actual drawing API and schema are deferred to external attachments.

4 / 5

Workflow Clarity

The pipeline is sequenced in section order (inputs → screenplay → "The application requests shared helpers first and then individual scene scripts" → validation) and includes an explicit correction loop ("If a correction is supplied, return the whole corrected file") with validation checkpoints delegated to and described for the host. It is not 5 because the steps are distributed across constraint bullets rather than an explicit ordered workflow, leaving some sequencing implicit.

4 / 5

Progressive Disclosure

In-file structure is good and the two references are clearly signaled and one level deep ("Read [README.md](README.md) for the supported application subset and [KIT.md](KIT.md) for drawing APIs"), but neither README.md nor KIT.md exists in the bundle (no references/, scripts/, or assets/ directories), so the disclosure chain breaks at the first hop. Scoring against the actual bundle structure, this lands at anchor 3 rather than 4, since following the clearly-signaled references leads to missing files.

3 / 5

Total

16

/

20

Passed

Description

57%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 states a clear, distinctive, narrowly-scoped capability in third person with concrete artifacts, but it omits any "when to use" trigger guidance and leans on application-internal jargon rather than natural user phrases. It is functional but sits at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user requests a research film, video screenplay, or scene animations from a saved research session."

Include natural user-facing terms and synonyms ("research video", "video generation", "animate a session") alongside the application jargon so the skill triggers on how users actually phrase the request.

Frame the host-provided pipeline features (narration, playback, MP4 export) as outcome context only after stating the skill's own actions, so the capability list reads as what the skill does.

DimensionReasoningScore

Specificity

"Author the existing video.json screenplay and JavaScript animation bodies" names the domain and two concrete authoring actions with specific artifacts (video.json, JS animation files). The second sentence ("The application provides the session snapshot, model calls, English narration, dynamic HTML playback and optional desktop MP4 export") describes host capabilities, not skill actions, so coverage stays at the 1–2-concrete-actions level rather than the several-actions level of anchor 4.

3 / 5

Completeness

The "what" is clear (author the video.json screenplay and animation JS bodies), but there is no "Use when..." clause or equivalent trigger guidance — the second sentence describes what the application provides, not when to invoke the skill. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; it is not 2 because the "what" is concrete and specific.

3 / 5

Trigger Term Quality

Relevant keywords are present ("screenplay", "JavaScript animation", "English narration", "MP4 export"), but the phrasing is application-centric jargon ("the existing video.json screenplay", "Open-Science Research film", "model calls") rather than phrases a user would naturally say. Missing natural variations such as "create a research video" or "video generation" keeps this at anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"video.json screenplay", "JavaScript animation bodies" and "Open-Science Research film" define a narrow, application-specific niche with distinct triggers, so overlap with other skills is minimal. This clearly matches anchor 5 (clear niche with distinct triggers) rather than anchor 4's minor-overlap case.

5 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

aipoch/open-science

Path

packages/research-film/resources/authoring/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.