hyperframes-registry

Install, discover, and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A well-structured, highly actionable body that offloads detail to real, clearly signaled one-level references. The main weakness is verbosity in the Discovery/reporting sections, where justification prose competes with the leaner command-focused content elsewhere.

Suggestions

Tighten the Discovery section: drop the explanatory rationale ('the registry holds more items than you can scan by eye…', 'This is the whole demand signal for the catalog. Skipping it means…') and keep only the rule and the command.

Add an inline validation checkpoint to the install→wire path (e.g., confirm the written files and that data-composition-id matches the block's internal ID) so the common workflow is self-verifying without jumping to a reference.

Move the extended on-device/consent-tier explanation into discovery.md and leave a one-line pointer, reducing the SKILL.md token footprint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable command blocks, but the Discovery and 'Report what the catalog does not have' sections carry rationale padding ('the registry holds more items than you can scan by eye…', 'This is the whole demand signal for the catalog. Skipping it means…') that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands (hyperframes add/catalog with flags), a JSON config example, and a complete HTML wiring snippet covering the common install and wiring cases.	5 / 5
Workflow Clarity	A clear numbered sequence for wiring components (1–5) and a named contributing workflow (idea → scaffold → build → validate → preview → ship), with validation/preview steps present though largely deferred to the referenced file.	4 / 5
Progressive Disclosure	Clean overview with well-signaled one-level-deep references ('See [x.md](./references/x.md) for full details'); all six referenced files exist and resolve, with detail appropriately split out of SKILL.md.	5 / 5
	Total	17 / 20 Passed

Description

92%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 strong, specific description with an explicit 'Use when' trigger clause and concrete command-level triggers tied to a distinct niche. The only soft spot is trigger-term breadth, which leans on command names rather than a wider set of natural-language synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Install, discover, and wire registry blocks and components', 'installing one item or every block matching a tag', 'wiring an installed item into index.html', and 'authoring a new block or component to contribute upstream (idea → scaffold → validate → PR)' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (install/discover/wire registry blocks and components) and 'when' via a concrete 'Use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json' clause.	5 / 5
Trigger Term Quality	Includes natural command-trigger phrases ('running hyperframes add', 'hyperframes catalog', 'working with hyperframes.json', 'wiring an installed item into index.html'), but the triggers are mostly command-name-centric with a few common natural-language variations absent.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to the HyperFrames registry and its specific commands (hyperframes add/catalog, hyperframes.json), giving a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: heygen-com/hyperframes
Path: skills/hyperframes-registry/SKILL.md
Commit: a562946

Reviewed: about 9 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.