Background
Anthropic published the Agent Skills spec as an open standard on December 18, 2025 (agentskills.io), formalizing the SKILL.md folder format (YAML frontmatter + markdown body, optional bundled scripts/references) that Claude Code had used internally. Within 48 hours OpenAI and Microsoft added support, and as of mid-2026 roughly 40 tools implement it, including Claude Code, Codex CLI, Cursor, Gemini CLI, GitHub Copilot, and VS Code.
CodeCannon predates this standardization. Our skills currently live as flat command files (originally modeled on the pre-standard .claude/commands/*.md convention) rather than the now-normalized /SKILL.md folder format. This ticket covers bringing the repo in line with the standard and reconsidering the sync mechanism now that the ecosystem provides native multi-tool support.
Tasks
- Audit existing skills (ticket creation/closing, PR review, deployment handling, etc.) and convert each from its current file layout to /SKILL.md with proper frontmatter (name, description at minimum).
- Confirm target directory conventions per tool we care about:
- Claude Code: ~/.claude/skills/ (personal), .claude/skills/ (project)
- Codex CLI: ~/.codex/skills/ / .codex/skills/ (plus optional openai.yaml for UI metadata / MCP tool deps — evaluate if we need it)
- Cursor: .cursor/skills/ only (project-scoped, no personal/global path)
- Gemini CLI: ~/.gemini/skills/ / .gemini/skills/
- Evaluate whether the custom Python sync script is still needed. Since compatible tools now read the same SKILL.md folder format natively, syncing may reduce to a symlink strategy or a simple copy step per target directory rather than custom transformation logic. Determine if the script's job shrinks to just "place/link the folder in N locations" vs. its current scope.
- Flag any skill that relies on Claude Code-specific frontmatter (e.g. context: fork for subagent execution) that won't translate to other tools, and decide whether to keep it Claude-only or find a portable equivalent.
- Update README to describe the new format and reference agentskills.io as the spec source.
- Regression-test each migrated skill in Claude Code at minimum; spot-check in at least one other supported tool (Codex CLI or Cursor) if we're claiming cross-tool portability as a goal.
Why now: the sooner we adopt the standard format, the less custom glue code we maintain, and the more our skill set is portable if the team's tool mix changes.
Background
Anthropic published the Agent Skills spec as an open standard on December 18, 2025 (agentskills.io), formalizing the SKILL.md folder format (YAML frontmatter + markdown body, optional bundled scripts/references) that Claude Code had used internally. Within 48 hours OpenAI and Microsoft added support, and as of mid-2026 roughly 40 tools implement it, including Claude Code, Codex CLI, Cursor, Gemini CLI, GitHub Copilot, and VS Code.
CodeCannon predates this standardization. Our skills currently live as flat command files (originally modeled on the pre-standard .claude/commands/*.md convention) rather than the now-normalized /SKILL.md folder format. This ticket covers bringing the repo in line with the standard and reconsidering the sync mechanism now that the ecosystem provides native multi-tool support.
Tasks
Why now: the sooner we adopt the standard format, the less custom glue code we maintain, and the more our skill set is portable if the team's tool mix changes.