kinetic-studio

Use whenever you are running inside the Kinetic Studio desktop editor (KINETIC_STUDIO=1, or CWD contains a story.json next to a .kinetic-studio/ folder). Edits a single story.json in the project root; the studio watches it and refreshes preview + timeline automatically. Do NOT write standalone Remotion .tsx files — they will not show up in the preview.

Quality

75%

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 ./src-tauri/skills/kinetic/SKILL.md

Quality

Content

80%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 a strong, highly actionable operating manual with excellent progressive disclosure via clearly signaled sibling references. Its main gap is the absence of an explicit validation/feedback loop for the destructive replace and splice operations, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint after writing story.json for destructive modes (e.g. re-read the file / confirm Zod parsed cleanly and surface errors before declaring done) to lift workflow_clarity above the destructive-op cap.

Trim minor over-explanatory passages (e.g. the "You do not have to read all five" paragraph could be one line) to push conciseness toward anchor 5.

Optionally include one short annotated story.json beat snippet so the field-level rules have a concrete copy-paste exemplar.

Dimension	Reasoning	Score
Conciseness	The manual is mostly efficient and assumes competence (exact file paths, field rules, formulas), with only minor trimmable passages such as the explanatory "You do not have to read all five" routing, fitting anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Provides fully executable, field-level guidance — exact paths ("./.kinetic-studio/prompt-mode", "./.kinetic-studio/selection"), concrete splice rules, explicit formulas ("beats[i].startSeconds + beats[i].durationInSeconds"), and named commands (cp, yt-dlp) covering the common replace/append/insert cases, matching anchor 5.	5 / 5
Workflow Clarity	The turn workflow is clearly sequenced (read prompt-mode + selection first, combine to choose mode, apply rules, write story.json, one-line summary), but destructive operations ("replace" wipes story.beats entirely; splice deletes beats[i]) lack an explicit agent-side validate→fix→retry checkpoint, which the rubric caps at 3 for destructive/batch workflows.	3 / 5
Progressive Disclosure	Acts as a routing overview pointing to five well-signaled one-level-deep sibling references (typography-system.md, motion-design.md, color-system.md, render-pipeline.md, layer-composition.md), each described by topic with explicit guidance on which to load per request, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Description

70%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 highly complete and distinctive with an explicit when-clause and concrete environment triggers, but it is held back by second-person voice and a narrow action set (essentially one operation plus a prohibition). Tightening to third person and stating the action set more comprehensively would raise specificity.

Suggestions

Rewrite in third person (e.g. "Edits the project's story.json ... Use when running inside the Kinetic Studio editor") to avoid the second-person specificity penalty.

Broaden the stated action set beyond the single "edits story.json" verb (e.g. add, replace, splice, and insert beats) to lift specificity toward anchor 4-5.

Add one or two natural-language synonyms (e.g. "kinetic typography", "text animation") alongside the technical env-var/folder triggers to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ("Edits a single story.json in the project root") plus a negative constraint ("Do NOT write standalone Remotion .tsx files"), which fits anchor 3; reduced to 2 because the description uses second-person voice ("you are running", "Do NOT write") which the rubric penalizes by -1.	2 / 5
Completeness	Explicitly answers both what ("Edits a single story.json ... refreshes preview + timeline automatically") and when ("Use whenever you are running inside the Kinetic Studio desktop editor (KINETIC_STUDIO=1, or CWD contains a story.json next to a .kinetic-studio/ folder)") with concrete trigger conditions, matching anchor 5.	5 / 5
Trigger Term Quality	Trigger keywords are present ("Kinetic Studio desktop editor", "KINETIC_STUDIO=1", "story.json", ".kinetic-studio/ folder") but skew technical/internal rather than natural user phrasings, with few synonyms or variations, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Kinetic Studio kinetic-typography, story.json editing) with environment-specific triggers unlikely to fire for other skills, matching anchor 5.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: tombrewsviews/BYOA
Path: src-tauri/skills/kinetic/SKILL.md
Commit: e2ffa8f

Reviewed: ~22 hours 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.