skill-best-practices

To structure agent skill metadata, use a standard frontmatter schema with required name and description fields, plus optional scripts, references, and assets directories to ensure discoverability and compliance across your team.

The best way to validate agent skill metadata is by running deterministic validation scripts that enforce a consistent file layout and guard against malformed frontmatter and inconsistent naming conventions.

You can scaffold a new agent skill directory by following a template-driven workflow that creates validated metadata frontmatter and organizes supporting files into dedicated resource folders like scripts and references.

Agent skill validation fails due to inconsistent naming when the metadata structure does not adhere to deterministic workflow rules, which enforce specific frontmatter schemas to prevent malformed entries.

Yes, you can use progressive disclosure to keep agent skill bodies lean by moving detailed logic into optional resource directories like scripts and references while maintaining standard metadata structure.