BC hyperframes-cli
Scaffold, inspect, preview and render HyperFrames projects; use local or explicitly authorized hosted workflows.
A skill for HyperFrames, a framework that lets you scaffold, inspect, preview and render projects via CLI. Promises to work with local setups or explicitly authorized hosted workflows.
Files check out: 14 documents, no broken links, no critical issues. Code quality scores 83, safety 100. Process score sits at 56, meaning automated checks didn't run fully, but the skill wasn't tested on actual models or in sandbox.
Worth installing if you already use HyperFrames and want to automate operations through an AI agent. If you're new to the framework, this won't help much. Set it up if you need it, but don't expect miracles.
Scaffold, inspect, preview and render HyperFrames projects; use local or explicitly authorized hosted workflows.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "license_source" - note
frontmatter-keyunknown frontmatter key "date_added" - note
edit-residuethe text marks something as outdated (lines 31): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2413 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (11 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 112: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (12 of 12)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.