Skip to content

Strip non-canonical keys from SKILL.md frontmatter#13

Open
bryan-anthropic wants to merge 1 commit into
datadog-labs:mainfrom
bryan-anthropic:fix/skill-frontmatter-canonical-keys
Open

Strip non-canonical keys from SKILL.md frontmatter#13
bryan-anthropic wants to merge 1 commit into
datadog-labs:mainfrom
bryan-anthropic:fix/skill-frontmatter-canonical-keys

Conversation

@bryan-anthropic
Copy link
Copy Markdown

The three skills/*/SKILL.md files currently carry license: and metadata: keys in their YAML frontmatter:

---
name: ddsetup
description: ...
allowed-tools: Read
license: Apache-2.0
metadata:
  author: Datadog
  version: "0.7.10"
---

The Claude skill schema recognizes a small set of canonical keys (name, description, allowed-tools, user-invocable, argument-hint). Additional keys like license: and metadata: aren't part of the schema, and some validators in the ecosystem reject them on load.

We observed this rejecting on a recent direct upload of the plugin to one of the marketplace surfaces. Stripping the non-canonical keys lets the plugin load cleanly across all install paths, including direct zip upload and URL-source ingestion.

Per-skill provenance (license, author, version) is already captured in LICENSE, NOTICE, and .claude-plugin/plugin.json at the repo root, so no information is lost.

Diff

3 files, 12 deletions — only the license: line and the 3-line metadata: block from each of:

  • skills/ddsetup/SKILL.md
  • skills/ddconfig/SKILL.md
  • skills/ddtoolsets/SKILL.md

Skill content and allowed-tools are unchanged.

Remove license: and metadata: blocks from skills/ddsetup/, skills/ddconfig/,
and skills/ddtoolsets/ SKILL.md frontmatter. These keys aren't part of the
Claude skill schema and trip some loaders that enforce canonical-keys-only.

Provenance is unchanged — license info is captured in LICENSE + NOTICE at
the repo root, and author/version live in .claude-plugin/plugin.json.
@bryan-anthropic bryan-anthropic requested a review from a team as a code owner May 21, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant