Skills structure: motion-graphics description has no "use when"; most references are not linked from SKILL.md · Issue #5855 · heygen-com/hyperframes · GitHub
Skip to content

Skills structure: motion-graphics description has no "use when"; most references are not linked from SKILL.md #5855

Open

Description

@Konstantin-Zhirnov

Problem

Checked against main on 2026-10-18 using Anthropic's skill authoring guidance: the description should say when to use the skill, references should be one level deep from SKILL.md, and files over 100 lines should start with a table of contents.

motion-graphics. The description lists what the skill produces and routes to /general-video and /hyperframes, but it has no explicit "Use when …" trigger. Choosing between motion-graphics, hyperframes and general-video is left to keyword overlap.

hyperframes. SKILL.md links only 4 of the 25 files in references/ (intent-interview.md, plugin-installation.md, routes/remotion-to-hyperframes.md, skill-lifecycle.md). The others, including workflow-catalog.md, route-briefs.md, brief-format.md, capability-menu.md, frame-worker-core.md and most of routes/, are not linked from SKILL.md. Agents tend to read files reached through another reference only partially (head -100).

hyperframes-animation. SKILL.md links 19 of 103 markdown files. The 48 rules/*.md are reachable only through rules-index.md, the 16 transitions/*.md only through transitions/catalog.md, and none of the 22 blueprints/*.md is linked from SKILL.md. 58 of the 61 files longer than 100 lines have no table of contents near the top.

Proposed solution

  • Add a "Use when …" sentence to the motion-graphics description.
  • List every reference file in SKILL.md with one line on when to read it (the indexes can stay).
  • Add a short contents block to files over 100 lines.

Alternatives considered

No response

Additional context

If #5651 (retiring the workflow skills) supersedes part of this, feel free to close those parts.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttriage/needs-triageNeeds current-behavior, related-work, and scope evaluation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions