brag

Project launch video via Hyperframes, upstream-maintained.

Quality

51%

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 ./optional-skills/creative/brag/SKILL.md

Quality

Content

53%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 a well-organized catalog stub that is honest about its upstream-maintenance model and gives concrete install/prerequisite commands. However, it instructs almost nothing about executing the skill's own workflow — the pipeline is narrated rather than prescribed — and it spends tokens on catalog and install-status meta-commentary. It functions acceptably as a pointer to the real skill but not as a standalone SKILL.md.

Suggestions

Trim the catalog-maintenance meta-commentary (the stub blockquote and the skills-guard status aside) to a one-line pointer, keeping only the install command and docs URL.

Prescribe the actual workflow as numbered steps (read project → pick tone → storyboard → composition brief → render → verify output) with a validation checkpoint that brag-output/brag.mp4 and the poster were produced.

Move the time-sensitive install-status details ("hyperframes-creative scores dangerous, which --force cannot override") into the upstream README or a separate status file, since they will go stale.

Dimension	Reasoning	Score
Conciseness	The prerequisites section is dense and useful ("Node.js 22+, FFmpeg on PATH", "npx hyperframes doctor", GITHUB_TOKEN guidance), but the 8-line "Catalog stub" blockquote and the upstream-maintenance meta-commentary ("quarantined and scanned like any hub install") explain catalog plumbing rather than the task. Mostly efficient with some unnecessary explanation — anchor 3.	3 / 5
Actionability	There are concrete, runnable commands ("hermes skills install official/creative/brag", "npx hyperframes doctor") and a fully enumerated options list ("--tone", "--format landscape\|vertical\|square", "--voice"), but the core pipeline ("commits to an angle and a tone", "hands a composition brief to Hyperframes") is only described, never instructed. Some concrete guidance but incomplete — anchor 3.	3 / 5
Workflow Clarity	The pipeline sequence is implicit in prose ("reads the project... storyboards a 15–25 second video, hands a composition brief to Hyperframes, and renders brag-output/brag.mp4") with no numbered steps, checkpoints, or error-recovery guidance. This is a multi-step render workflow, so the simple-skill exception does not apply; anchor 3 ("steps listed but validation gaps... sequence present but checkpoints missing or implicit").	3 / 5
Progressive Disclosure	At ~45 lines with well-organized sections, the body clearly signals one-level-deep external pointers ("Full documentation: https://github.com/latent-spaces/brag#readme", upstream "skills/brag/" with its step references and scripts) and explicitly explains that this directory holds only catalog metadata. Not 5 because the referenced bundle files (scripts/analyze_music_cues.py, tone presets, music library) are not present locally and navigation depends entirely on the external repo.	4 / 5
	Total	13 / 20 Passed

Description

48%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 terse and names a clear, distinctive niche, but it omits any concrete capability list and any "Use when..." trigger clause. It reads more like a catalog title than a skill description. The trigger cap keeps completeness at 3 and the near-total absence of stated actions holds specificity to 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants a launch/promo video for their project, a product demo clip, or share-ready marketing footage."

List 2–4 concrete actions in the description itself (e.g. "storyboards a 15–25s video, renders brag.mp4 with poster and share copy") rather than only the domain.

Include natural synonyms such as "promo video", "product video", and "marketing clip" so the skill triggers on the phrases users actually say.

Dimension	Reasoning	Score
Specificity	The description names the domain and tool ("Project launch video via Hyperframes") but lists no concrete actions such as storyboarding, tone selection, or rendering — those appear only in the body. It matches anchor 2 ("names the domain but actions are minimal or generic") better than 3, which requires 1–2 explicit actions in the description itself.	2 / 5
Completeness	The what is present ("Project launch video via Hyperframes") but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It sits above anchor 2 because the what is clear, not vague.	3 / 5
Trigger Term Quality	"launch video" is a natural phrase users would say and "Hyperframes" is a distinctive tool name, but common synonyms and variations (promo video, product video, marketing video, demo, announce) are missing. This fits anchor 3 ("some relevant keywords but missing common variations or synonyms").	3 / 5
Distinctiveness Conflict Risk	The pairing of a project launch video with the specific tool Hyperframes is mostly distinct with only minor overlap risk against generic video or motion-graphics skills. Not 5 because "launch video" alone could plausibly collide with other video-generation skills.	4 / 5
	Total	12 / 20 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/creative/brag/SKILL.md
Commit: 68fa7e9

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.