How to declare tags and a license
Add tags and a license to the front matter of a SKILL.md. Tags let consumers install related resources in one step.
Prerequisites
- A Git registry with
SKILL.mdfiles. agent-marketplaceon yourPATH.
1. Add tags
Put tags under metadata.tags as a list of strings:
---
name: secure-inputs
description: Validate and sanitize user input.
metadata:
tags:
- security
- frontend
---
# secure-inputs
Validate and sanitize user input.Consumers select every resource with a tag through tags: in a resource group. Commands and subagents written as Markdown with front matter take metadata.tags in the same place.
2. Add a license
license is a top-level front matter field, next to name:
---
name: secure-inputs
description: Validate and sanitize user input.
license: Apache-2.0
metadata:
tags:
- security
- frontend
---3. Declare prerequisites
If the resource needs another resource installed, declare it under metadata.requires. See Declare resource prerequisites and the resource prerequisites reference.
4. Verify the metadata
From the registry root, run agent-marketplace list --from .. The command prints a table whose TAGS (metadata) column shows the declared tags; typical output:
REGISTRY KIND NAME TAGS (metadata) STATUS
. skill secure-inputs security,frontend availableThe license field does not appear in list output; inspect the file's front matter to check it. The resource metadata reference lists the accepted fields.
Boundaries
- Tags match exactly and are case-sensitive. Leading and trailing whitespace is ignored.
- License allowlists are enforced by Marketplace ingestion, not by the consumer CLI.
Troubleshooting
- Tags have no effect: check that
tagsis undermetadataand is a list of strings. The CLI ignores items that are not strings.