hyperframes-registry

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, and registry discovery.

Quality

96%

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

90%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 strong, lean skill body with executable commands, complete snippets, and a well-structured one-level reference layout. The two gaps are minor: no explicit validation checkpoint in the wiring workflows, and one bundle reference file (demo-html-pattern.md) is not discoverable from the body.

Suggestions

Add an explicit validation checkpoint after wiring a block or component (e.g. a step to confirm data-composition-id matches the block's internal composition ID and to preview the host composition before considering the wiring done).

Reference demo-html-pattern.md from the body — e.g. a line in the Wiring components section pointing to it — so all bundle files are discoverable from SKILL.md.

Consider a short 'Verify install' note after hyperframes add (check the CLI's reported output paths against the configured hyperframes.json paths) to close the feedback loop on install locations.

Dimension	Reasoning	Score
Conciseness	The ~100-line body is lean with every explanation carrying domain-specific knowledge Claude lacks (block vs component semantics, key data attributes), and no padding or explanation of generic concepts. Each section earns its tokens.	5 / 5
Actionability	Guidance is copy-paste ready throughout: five concrete CLI invocations with flags, a complete data-composition-src HTML snippet, a full hyperframes.json example, a curl command for registry discovery, and numbered steps for merging component snippets.	5 / 5
Workflow Clarity	The component wiring steps form a clear numbered sequence (read file, copy HTML, copy style, copy script, add timeline calls), but no validation checkpoints are given — e.g. verifying data-composition-id matches the block's internal ID is stated as a requirement in prose but never framed as a check step. Fits 'clear sequence with most checkpoints present; minor validation gaps', not 5 which requires explicit validation steps.	4 / 5
Progressive Disclosure	Each section ends with a well-signaled one-level-deep reference ('See [wiring-blocks.md](./references/wiring-blocks.md) for full details') and nested linking was verified absent in the reference files. However, the bundle file demo-html-pattern.md is never referenced from the body, leaving an orphaned resource and a minor navigation gap.	4 / 5
	Total	18 / 20 Passed

Description

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

An exemplary description: third-person, concrete, and concise. It states what the skill does, gives explicit 'Use when' triggers covering commands, artifacts, and file names, and delineates its niche clearly. No weaknesses identified.

Dimension	Reasoning	Score
Specificity	Multiple concrete actions are enumerated — 'Install and wire registry blocks and components', 'running hyperframes add', 'wiring an installed item into index.html' — and the coverage sentence lists install locations, block sub-composition wiring, component snippet merging, and registry discovery, comprehensively covering the skill's surface.	5 / 5
Completeness	It explicitly answers both 'what' (install and wire registry blocks and components into HyperFrames compositions) and 'when' via a concrete 'Use when...' clause with four trigger conditions, matching the top anchor example pattern.	5 / 5
Trigger Term Quality	Triggers include the literal command users would type ('hyperframes add'), the natural nouns 'block' and 'component', and concrete file names 'index.html' and 'hyperframes.json', giving comprehensive coverage including file extensions.	5 / 5
Distinctiveness Conflict Risk	'HyperFrames' names a clear niche and the triggers are specific CLI commands and config files, so the description is clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	20 / 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: openai/plugins
Path: plugins/hyperframes/skills/hyperframes-registry/SKILL.md
Commit: 5fd93af

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