SKILL.md format compatibility with other skill hosting tools?

[latentloop07]

question on the SKILL.md format used here for ms's coding agents. is the schema intentionally compatible with the anthropic-style SKILL.md format (name, description, body, YAML frontmatter)? our internal registry tool ingests SKILL.md from any source and would be nicer if both ecosystems used the exact same shape.

specifically asking because: if these are compatible, we (skillnote, mit: github.com/luna-prompts/skillnote) could add a microsoft/skills shorthand to our marketplace importer alongside the anthropic ones. would benefit anyone using ms's SDK skills with non-ms agents too.

[omribz156]

I took a quick source-backed pass over the current repo shape. I am not a maintainer, so I cannot answer the "intentionally compatible" part, but the current files look broadly compatible with the common SKILL.md pattern if an importer treats name and description as the required fields and ignores unknown frontmatter keys.

What I found:

• README.md says new skills should include YAML frontmatter with name and description.
• .github/skills/skill-creator/SKILL.md describes the required file as SKILL.md with YAML frontmatter (name, description) plus Markdown instructions.
• Current sample skills such as .github/plugins/azure-sdk-python/skills/azure-ai-projects-py/SKILL.md and .github/plugins/azure-sdk-typescript/skills/azure-storage-blob-ts/SKILL.md use that base shape, but also add optional fields like license and nested metadata (author, version, package).
• The repo currently has about 181 SKILL.md files, so an importer should probably be tolerant rather than assume only two frontmatter keys.

So, practically: name + description + Markdown body appears safe as the baseline. Exact schema compatibility is less clear because the repo uses extra metadata fields and I did not find a formal schema declaring which keys are guaranteed. A small docs note or schema file for "minimum required fields" vs "optional metadata" would probably make marketplace/tooling integrations easier.

This check was Codex-assisted, with the final comment manually reviewed against the repo sources.