# Installed Skill Reference

After running `npx skills add heygen-com/hyperframes` inside this workspace, a new Skill folder appears at:

```
.claude/skills/hyperframes/SKILL.md
```

This file is **what you would have written yourself** if you were authoring a Skill from scratch. The HyperFrames maintainers wrote it for you. Read it carefully — it is the most important Skill anatomy lesson in this section.

## What to look for inside `SKILL.md`

When you open `.claude/skills/hyperframes/SKILL.md`, look for:

1. **Frontmatter** — `name` and `description`. The `description` is the trigger sentence Claude uses to decide whether to load this Skill into context. Notice how specific it is.
2. **When to use / When not to use** — bounded scope. The maintainers tell Claude when this Skill is the wrong choice.
3. **Workflow** — step-by-step instructions, not vague advice.
4. **Output format** — what the produced composition.html must look like.
5. **Quality checklist** — what Claude should verify before declaring the work done.

## Why this matters more than a hand-authored toy Skill

Reading a real, production community Skill teaches you what "good" looks like in the wild — far better than copying a template. You will write your own Skills later; before that, learn to recognize the shape of one written by people who use it daily.

## Optional supporting files the Skill brings with it

HyperFrames also ships a `skills/` folder with pre-built composition components. The Skill itself references them on demand (progressive disclosure pattern from Section 5).
