myco:myco-skill-lifecycle

Coordinate Myco skill lifecycle from vault knowledge to validated SKILL.md files.

12|2|Updated Mar 15, 2026

Search Tags:#automation #workflow #governance #skill-generation #skill-lifecycle #myco #vault-knowledge

Ready to run

npx skills add https://github.com/goondocks-co/myco --skill myco-myco-skill-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: myco:myco-skill-lifecycle
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/myco-skill-lifecycle
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-myco-skill-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the end-to-end Myco skill lifecycle by turning vault knowledge into structured SKILL.md artifacts while managing candidates through survey, approve, generate, and evolve phases.

Core Features & Use Cases

End-to-end lifecycle orchestration: survey, approve, generate, evolve.
Vault-driven candidate identification and governance via the Skills dashboard, including edge cases where candidates appear but no skills materialize or require refreshing.
On-disk SKILL.md generation with proper frontmatter, validation, and safe tooling constraints.

Quick Start

Initialize or run the skill lifecycle workflow to turn vault knowledge into SKILL.md artifacts.

Frequently Asked Questions about myco:myco-skill-lifecycle

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

FAQPage Schema

How do I automate SKILL.md generation from vault knowledge?▼

Automate SKILL.md generation by running the end-to-end skill lifecycle workflow, which surveys vault knowledge, approves candidates, and generates validated on-disk artifacts with proper frontmatter.

What is the best way to manage skill lifecycle governance and enforce tooling constraints?▼

Manage skill lifecycle governance by orchestrating survey, approve, generate, and evolve phases, which enforces frontmatter and tooling constraints like name, description, managed_by, user-invocable, and allowed-tools.

How do I handle vault knowledge candidates that appear but no skills materialize?▼

Handle non-materializing candidates through the dashboard workflow, which identifies vault-driven candidates and manages edge cases where skills require refreshing or fail to materialize.

Can I validate frontmatter and allowed-tools constraints during skill generation?▼

Validate frontmatter and allowed-tools constraints during skill generation, as the lifecycle enforces name, description, managed_by, user-invocable, and allowed-tools fields for safe SKILL.md production.

Do I need a dashboard workflow to survey and evolve existing skills?▼

Use the Skills dashboard to survey and evolve existing skills, as it drives vault-based candidate identification and orchestrates the evolve phase for refreshing or updating existing artifacts.

What are the limitations when turning vault knowledge into SKILL.md artifacts?▼

Limitations include dependency on vault knowledge quality for candidate identification and strict adherence to enforced frontmatter and tooling constraints, which may block generation if validation fails.