Skip to content

Add check that federated skill names never change - #6

Merged
danielholanda merged 1 commit into
mainfrom
dholanda/skill-name-check
Oct 7, 2026
Merged

danielholanda merged 1 commit into
mainfrom
dholanda/skill-name-check

Conversation

@danielholanda

@danielholanda danielholanda commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds a Skill Names workflow that fails if any of the three federated skills is renamed. These skills are sent to amd/skills, so their names must stay fixed:

  • lemonade-router-builder
  • local-ai-app-integration
  • local-ai-use

A skill's name lives in two places, and the check covers both:

  • Folder: skills/<name>/SKILL.md must exist. This catches a renamed or deleted folder.
  • Frontmatter: the name: field in SKILL.md must match exactly.

It runs on every pull request, on pushes to main, and on manual dispatch. There is no path filter, so it can be made a required check without getting stuck as pending on PRs that don't touch skills.

Test plan

Ran the check script locally:

  • Current skills pass
  • Changing local-ai-use frontmatter to local-ai-usage fails
  • Renaming the local-ai-use folder fails
  • Workflow passes on this PR

lemonade-router-builder, local-ai-app-integration, and local-ai-use are federated to github.com/amd/skills, so their folder names and SKILL.md frontmatter names must stay fixed.

Co-authored-by: Cursor <cursoragent@cursor.com>
@danielholanda
danielholanda merged commit ffb22cd into main Oct 7, 2026
1 check passed
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