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, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

Quality

93%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, highly actionable, and well-structured with verified one-level-deep references. The only gap is workflow_clarity: the inline install and wiring workflows omit explicit validation/verification checkpoints, capping that dimension at 2.

Suggestions

Add an explicit verification step after wiring a block (e.g., 'Confirm the block renders by previewing the host composition and checking data-composition-id matches the block's internal ID') to close the workflow_clarity gap.

Include a short feedback loop for the install step — e.g., 'If hyperframes add reports missing registry access, check the registry URL in hyperframes.json and retry' — so failures have a recovery path inline.

Reference the existing references/demo-html-pattern.md from the body (it is unreferenced) or note it under Discovery/Contributing so all bundle files are discoverable.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence — quick-reference commands, an HTML snippet, and a numbered wiring list with no padding or explanation of concepts Claude already knows; not level 2 because nearly every line is actionable rather than containing unnecessary explanation.	3 / 3
Actionability	Copy-paste-ready commands (`hyperframes add data-chart --json`), a complete HTML block snippet with all wiring attributes, and a concrete 5-step component-wiring procedure; not level 2 because guidance is executable and complete rather than pseudocode or missing key details.	3 / 3
Workflow Clarity	Sequences are present (numbered component-wiring steps, install-then-wire flow, idea→scaffold→validate→PR for contributing), but the inline install/wiring workflows lack explicit validation or verify-it-renders checkpoints — the only validation signal is delegated to contributing.md; not level 3 because no inline feedback loop or checklist is provided, and not level 1 because steps are clearly sequenced.	2 / 3
Progressive Disclosure	Body is a concise overview with each section ending in a well-signaled one-level-deep reference (install-locations, wiring-blocks, wiring-components, discovery, contributing, templates), and all six referenced files exist in ./references/; not level 2 because references are clearly signaled and content is appropriately split rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 strong across all dimensions: third-person, concrete, with an explicit Use-when trigger and tool-specific terms that make it both findable and unlikely to conflict. No meaningful weaknesses.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — "Install and wire registry blocks and components", "install locations, block sub-composition wiring, component snippet merging, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR)" — matching the multiple-specific-actions anchor; not level 2 because the action list is comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers both what ("Install and wire registry blocks and components into HyperFrames compositions") and when ("Use when running hyperframes add...") with an explicit Use-when clause; not level 2 because the when-trigger is stated, not merely implied.	3 / 3
Trigger Term Quality	Natural triggers a user would say are well covered — "running hyperframes add", "installing a block or component", "wiring an installed item into index.html", "working with hyperframes.json"; not level 2 because common phrasings and tool invocation forms are present rather than just a few relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Clear HyperFrames-registry niche with tool-specific triggers (hyperframes add, hyperframes.json) unlikely to match other skills; not level 2 because the scope is narrowly scoped to this registry rather than overlapping with generic install/edit skills.	3 / 3
	Total	12 / 12 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: calesthio/OpenMontage
Path: .agents/skills/hyperframes-registry/SKILL.md
Commit: 0af32ce

Reviewed: 1 day 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.