Synopsis
Description
Validates a plugin folder against the Agent Plugins specification, and each of its skills against the Agent Skills specification. It reports problems and never changes the folder. The same check runs whenflox agent import writes a package and when that package is built.
<path> is a plugin folder:
Options
What is checked
plugin.jsonexists, is valid JSON, and matches the schema its$schemanames.- The folder’s name matches the manifest’s
name. skills/holds at least one skill: a folder directly under it with a file named exactlySKILL.md. Symbolic links are not followed.- Each
SKILL.mdhas frontmatter with anameand adescriptionthat follow the Agent Skills rules. mcp.json, when present, matches the MCP schema for the same specification version asplugin.json.- Each local MCP server’s
commandis a bare program name or a./path inside the plugin.
Warnings and errors
A deviation that agents load anyway is a warning, and the plugin stays valid. Common warnings are unknown frontmatter fields, such asversion:, a skill name that does not match its folder, and a missing description.
Claude Code components such as agents/ or hooks/hooks.json at the plugin root also warn, because packages keep them under com.anthropic.claude-code/.
Everything else is an error, including any schema violation and a symbolic link under skills/.
Exit status
Example
See also
flox agent audit, which checks a plugin for security issues- Package a skill repository