api-gateway

You can centralize API routing by routing external calls through a unified gateway that identifies SKILL.md files, loads frontmatter to build a discoverable provider list, and uses the body as the activation prompt for runtime tasks.

Markdown-driven discovery loads Skill metadata from SKILL.md frontmatter and uses the Markdown body as the activated system prompt, validating required fields before enabling a Skill with graceful fallbacks for missing resources.

Yes, a SKILL.md file with name and description frontmatter is required at the root to load resources and prompts, while optional scripts, references, and assets directories extend capabilities on demand.

The best way to test Skill activation workflows is routing a sample request through a managed provider, verifying routing references in the included references folder, and validating Skill units via frontmatter-driven discovery.

Yes, you can extend capabilities through progressive resource loading by adding optional resources in scripts, references, and assets directories to support multi-provider workflows and integration notes on demand.

Skill validation fails because activation safeguards validate required fields before enabling a Skill, ensuring the frontmatter contains the necessary name and description metadata to build a discoverable Skill list.