example-skill

To structure YAML frontmatter for a new skill submission, include required fields like name, description, version, author, and category, along with optional metadata for clear documentation and successful validation.

The correct markdown documentation structure for a marketplace skill features sections for installation, usage, and structure, ensuring contributors provide a complete and readable blueprint for review and deployment.

You create a ready-to-copy template for building new skills by copying a canonical example and adapting the frontmatter and documentation sections to fit your specific contribution requirements.

New skill submissions lack a consistent structure for review because contributors often omit standardized YAML frontmatter and clear documentation, leading to confusion during the deployment and validation processes.

Yes, a skill template needs specific fields to pass marketplace validation, requiring essential frontmatter such as name, description, version, author, and category to ensure proper discovery and structural consistency.