feat: add skills as namespace-level catalogue entries with external source repos#884
Draft
DevelopmentCats wants to merge 3 commits into
Draft
feat: add skills as namespace-level catalogue entries with external source repos#884DevelopmentCats wants to merge 3 commits into
DevelopmentCats wants to merge 3 commits into
Conversation
Add agent skills to the registry catalogue alongside modules and
templates, following the agentskills.io specification with proper
frontmatter metadata (license, version, author, tags).
- Add registry/coder/skills/coder-modules/ and
registry/coder/skills/coder-templates/ as catalogue entries,
each with SKILL.md (full spec frontmatter + body) and README.md.
- Update .agents/skills/ frontmatter to match catalogue versions.
- Update CI/CD workflows and scripts to support skills:
- deploy-registry.yaml: add skills path trigger
- release.yml: detect skills vs modules for changelog path
- version-bump.yaml: add skills path trigger
- version-bump.sh: include skills in change detection
- tag_release.sh: scan skills directories and extract version
from SKILL.md frontmatter
…urce references Skills content now lives in source repos (e.g., coder/skills) instead of being duplicated in the registry. Each namespace declares its skill source repo(s) in a single registry/<namespace>/skills/README.md with a sources field in the frontmatter. Changes: - Replace per-skill directories (coder-modules/, coder-templates/) with a single registry/coder/skills/README.md that references coder/skills - Revert .agents/skills/ frontmatter changes (those files will move to coder/skills repo) - Revert version-bump.sh and tag_release.sh skill-specific version extraction (versioning lives in source repos now) - Keep CI/CD path triggers for registry/**/skills/** so catalogue metadata changes trigger deployment The registry-server build pipeline (PR #442) will need to be updated to clone source repos declared in the README.md frontmatter and auto-discover skills from them.
DevelopmentCats
changed the title
The README validation tool has an allowlist of directories permitted under registry/<namespace>/. Add 'skills' to that list so the skills/README.md catalogue entry passes validation. Skills are added to supportedUserNameSpaceDirectories but not to supportedResourceTypes, so the skills directory is allowed to exist without being validated as a module or template.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces per-skill catalogue entries with a namespace-level model where each namespace declares its skill source repo(s) in a single
registry/<namespace>/skills/README.md. The registry becomes a directory of skill repos, not a container for duplicated skill content.This aligns with the Skills as First-Class Registry Catalogue Items problem document.
Changes
New catalogue format
registry/coder/skills/README.mddeclarescoder/skillsas the source repo via asourcesfield in the frontmatter:The registry-server build pipeline will clone source repos at build time, auto-discover all skills inside them, and serve them through the existing API, MCP, and well-known discovery endpoints.
CI/CD path triggers
deploy-registry.yaml: Addedregistry/**/skills/**so catalogue metadata changes onmaintrigger redeployment.release.yml: Updated tag extraction to detect whether a tag is for a module or skill and set the changelog path accordingly.version-bump.yaml: Addedregistry/**/skills/**to path triggers.Removed
registry/coder/skills/coder-modules/,registry/coder/skills/coder-templates/) with their duplicated SKILL.md + README.md files. Skill content lives in source repos..agents/skills/frontmatter additions. These skills will move tocoder/skills.version-bump.shandtag_release.shskill-specific version extraction. Versioning lives in source repos.How it works
Namespaces list one or more source repos. The build process clones them, walks
skills/*/SKILL.md, and serves each repo's skills as a distinct group:Related