Describe the catalog change and the user-facing outcome.
- Catalog package path:
- Skills touched:
- Agents touched:
- package
manifest.jsonupdates: links.repository:links.docs:links.nuget:- sibling
skills/<skill>/manifest.jsonoragents/<agent>/manifest.jsonchanges:
- The change stays inside
catalog/<type>/<package>/for package-owned content -
SKILL.mdfrontmatter does not declareversion,category,packages, orpackage_prefix - Package metadata lives in the package
manifest.json - Skill- or agent-specific metadata lives in the nearest sibling
manifest.json - Agents, if any, live in
catalog/<type>/<package>/agents/<agent>/AGENT.md - I ran
python3 scripts/generate_catalog.py --validate-only - I ran
python3 scripts/generate_agent_catalog.py --validate-onlyif agents changed - I ran
python3 scripts/generate_pages.pyif contributor-facing site content changed - I ran
dotnet build dotnet-skills.slnx -c Release - I ran
dotnet test dotnet-skills.slnx -c Release
- I updated
README.mdorCONTRIBUTING.mdif the contributor workflow or catalog structure changed - I added or updated upstream watch entries if the package needs release or docs monitoring