kortix-skill-authoring

To standardize OpenCode skill creation, define mandatory frontmatter fields like name and description in a SKILL.md file. This ensures reliable discovery and consistent structure across local worktrees and registry workflows.

The best way to structure reusable skill units is using a lightweight, modular directory with a SKILL.md file and optional scripts, references, and assets subfolders. This encapsulates publishing workflows and enables clear registry discovery.

Yes, you can use optional resources like scripts, references, and assets subfolders when authoring a SKILL.md file. This extends skill capabilities without bloating the root directory structure.

You need frontmatter fields for OpenCode skill discovery because mandatory fields like name and description enable reliable identification. Without standardized frontmatter, discovery across repositories and registries fails.

Yes, skill authoring works across local worktrees and registry workflows. The standardized SKILL.md applies to OpenCode skills across repositories, enabling consistent naming and deployment.

A limitation of using a modular structure for skill publication is that omitting mandatory frontmatter fields like name and description breaks discovery, while overloading root directories defeats the lightweight design purpose.