myco:write-myco-skill

Create and validate Myco-managed SKILL.md files with required frontmatter.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill myco-write-myco-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:write-myco-skill
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/write-myco-skill
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-write-myco-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and validation of a Myco-managed SKILL.md file, ensuring every skill entry conforms to the required frontmatter contract and is ready for vault ingestion.

Core Features & Use Cases

  • Ensures the SKILL.md frontmatter includes all six required fields: name, description, managed_by, user-invocable, allowed-tools, and validates their presence and formatting.
  • Validates path safety, prevents common schema issues during skill creation or updates, and provides guidance on remediation when constraints are violated.
  • Supports authoring new skills, updating existing ones, and repairing previously failed qualifications within the Skill vault.

Quick Start

Run vault_write_skill to create or update the SKILL.md for the target skill and validate it against the required frontmatter and constraints.

Frequently Asked Questions about myco:write-myco-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate YAML frontmatter in a SKILL.md file?

To validate YAML frontmatter in a SKILL.md file, run the vault_write_skill command to enforce six required fields: name, description, managed_by, user-invocable, and allowed-tools. It checks formatting and path safety before vault ingestion.

What are the required frontmatter fields for skill management automation?

Required frontmatter fields for skill management include name, description, managed_by, user-invocable, and allowed-tools. Validating these fields ensures your SKILL.md file passes quality gates and is ready for vault ingestion.

How do I fix a failed quality gate in a skill vault?

To fix a failed quality gate in a skill vault, run vault_write_skill to repair the SKILL.md file. It enforces the required frontmatter schema, rejects invalid vault_* tool names, and ensures path safety to pass validation.

Why are vault_* tool names rejected in allowed-tools?

Vault_* tool names are rejected in allowed-tools to prevent schema conflicts during skill creation and updates. Enforcing this constraint ensures path safety and validates your SKILL.md file for successful vault ingestion.

Can I automate the creation of a SKILL.md file with safe atomic writes?

Yes, you can automate SKILL.md file creation with safe atomic writes by running vault_write_skill. It validates the required YAML frontmatter and ensures path safety during skill authoring and vault updates.