sora

Generate, remix, and manage short video clips via OpenAI's Sora API. Useful for cinematic shots, b-roll, and rapid concept video iteration.

Quality

66%

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

Quality

Content

58%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.

As a catalogue stub the body is admirably lean and well-organized, but it fails as actionable guidance: the entire "How to use" section defers to an external README with no concrete install command, path, or verification step. The structure is good; the executable substance is missing.

Suggestions

Replace `open https://github.com/openai/skills` with a concrete install command (e.g. a git clone of the upstream bundle and a copy into the agent's skills directory with the expected path).

Specify where the bundle's SKILL.md must land and what the skills directory looks like, instead of "install the upstream bundle into your active agent's skills directory".

Add a verification step, e.g. confirming the skill appears in the agent's skill list before invoking it by name.

Dimension	Reasoning	Score
Conciseness	The ~25-line body ("This catalogue entry advertises the skill in OpenDesign...") is lean with no concept explanations Claude already knows and no padding; every section serves the pointer-entry purpose. The only trim candidate is the "What it does" section repeating the frontmatter description verbatim, which falls short of anchor 4's "minor instances of over-explanation".	5 / 5
Actionability	The core instruction "install the upstream bundle into your active agent's skills directory" has no executable steps, and the only command, `open https://github.com/openai/skills`, merely opens a browser with the comment "Inspect the upstream README for exact paths" deferring all specifics to an external page. This matches anchor 2 ("minimal concrete guidance; high-level hints but missing the specific steps") — anchor 3 would require actual task instructions with key details, which are absent.	2 / 5
Workflow Clarity	A rough sequence exists (install the upstream bundle, then "ask the agent to invoke this skill by name (`sora`) or with one of the trigger phrases"), but the critical install step is undefined and there is no check that the skill is actually available. Anchor 2 ("rough sequence present but many gaps; steps poorly defined") fits; the simple-skill exception cannot apply because the single action is ambiguous, not unambiguous.	2 / 5
Progressive Disclosure	The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ are absent), and organizes content into clear sections ("What it does", "Source", "How to use") with a single one-level-deep external pointer (the upstream repo URL). Per the small-skill guideline, this earns anchor 5 with just well-organized sections.	5 / 5
	Total	14 / 20 Passed

Description

75%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.

A solid description: it names a specific product domain and several concrete actions with natural trigger vocabulary. Its main weaknesses are the generic "manage", a "Useful for..." clause that never becomes an explicit "Use when..." trigger statement, and missing common synonyms like "text-to-video" or "AI video".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Sora, AI video generation, text-to-video, or needs cinematic b-roll clips."

Replace the generic "manage" with the concrete operations offered (e.g. "list, download, and delete clips").

Include common synonyms such as "text-to-video" and "AI video" among the trigger terms.

Dimension	Reasoning	Score
Specificity	"Generate, remix, and manage short video clips via OpenAI's Sora API" lists several named actions on a concrete domain, though "manage" is generic and underlying API operations (list, download) are not enumerated. This sits above anchor 3's "1-2 concrete actions" but the generic "manage" and coverage gaps keep it below anchor 5's comprehensive action list.	4 / 5
Completeness	The "what" is clear ("Generate, remix, and manage short video clips via OpenAI's Sora API") and "Useful for cinematic shots, b-roll, and rapid concept video iteration" provides use-case guidance, but it is not an explicit "Use when..." trigger clause. This fits anchor 4 (both present, 'when' could be more explicit) rather than anchor 5's explicit trigger phrasing, and is above anchor 3 because a concrete use-case statement is present.	4 / 5
Trigger Term Quality	Natural phrases like "cinematic shots", "b-roll", and "rapid concept video iteration" appear, reinforced by the frontmatter triggers ("sora", "openai video", "short video"). Common variations such as "text-to-video", "AI video", or "video generation" are missing, matching anchor 4's "good keyword coverage; a few natural terms missing" rather than anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"OpenAI's Sora API" carves out a clear product niche with distinct triggers ("sora", "openai video"), but generic phrases like "short video" and "b roll" could overlap with other video-generation or video-editing skills. Anchor 4 ("mostly distinct; minor overlap risk with closely related skills") is the best fit; anchor 5 would require minimal conflict risk across the trigger set.	4 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/sora/SKILL.md
Commit: 1b47e60

Reviewed: 3 days 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.