Agent skills portable bundle format compliance

Question

Ensure agent skills follow the portable skill bundle format exactly:

skill-name/
├── SKILL.md          # Required: YAML frontmatter + instructions.
├── scripts/          # Optional: executable code the agent may run.
├── references/       # Optional: documentation loaded on demand.
└── assets/           # Optional: templates and static resources.

Portability rules:

• Directory name must equal the name field in frontmatter (lowercase, hyphenated, 64 chars max).
• description is the trigger — states what the skill does AND when to invoke it (1024 chars max).
• Reference bundled files by relative path (./references/methodology.md).
• Progressive disclosure: frontmatter always loaded; body on activation; scripts/references/assets read only when body says so.
• SKILL.md must be binding on its own — anything essential only in references is an obligation that may never be read.

Installation locations: ~/.agents/skills/, .agents/skills/, ~/.claude/skills/, .claude/skills/, ~/.copilot/skills/, .github/skills/, .opencode/skills/.

Distribution: Copy on install OR symlink from canonical directory.

Decision needed: Audit existing skills in .agents/skills/ for compliance. Create any missing files (SKILL.md frontmatter, progressive disclosure structure).

Label: wayfinder:task
Part of #2517

Start by auditing the existing skills under .agents/skills/ against the portable bundle structure and portability rules in the issue. Create any missing SKILL.md frontmatter or progressive-disclosure files, and consider the work complete when each skill conforms to the stated naming, description, relative-path, and installation requirements.