jarvis-agent-skill-authoring

You validate SKILL.md frontmatter by ensuring YAML includes required name and description fields alongside a non-empty markdown body. This compliance confirms the entry point is valid and enables correct skill discovery within the repository.

Correct directory placement for in-repo JARVIS skills involves organizing files under the proper skills category. You must also maintain optional scripts, references, and assets directories to ensure proper peer conventions and skill discovery.

You create a valid SKILL.md file by drafting compliant YAML frontmatter with name and description fields, adding a non-empty markdown body, and following peer conventions for category placement and reuse guidelines within your repository.

Yes, you can use optional scripts, references, and assets directories when shipping JARVIS skills. Awareness of these directories is required during the authoring workflow to ensure correct structure and proper skill discovery within the repository.

Your repository-maintained JARVIS skill fails to load correctly when the SKILL.md file lacks compliant YAML frontmatter, has missing required name or description fields, or is placed under the wrong skills category directory.

The best way to maintain team conventions for SKILL.md authoring workflows is standardizing in-repo skill creation and edits. Following peer conventions, category placement, and reuse guidelines ensures consistent skill delivery and frontmatter validation.