Restructure skills catalog into categories - #22
Open
njb90 wants to merge 5 commits into
Open
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Runs the real skills CLI against the checkout and fails when the number of discovered skills differs from the number of SKILL.md files, so a skill dropped by bad frontmatter or wrong depth cannot merge silently. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
README groups the skills table by category, leads the install section with --skill examples. CONTRIBUTING.md records the layout, frontmatter, description-shape, cross-reference, versioning and local-check rules. specs/ is gitignored. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
GitHub Actions sets CI, which makes the skills CLI colour its output, so 'Found 5 skills' arrived as 'Found \e[32m5\e[39m skills' and the grep never matched (found=0, expected=5). Set NO_COLOR and strip any remaining ANSI escapes before grepping. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Two new CI jobs alongside discovery, both backed by scripts that run locally too: - links: every cloudinary.com link to a .md page or llms.txt must carry install_source and referrer, so docs traffic from skills is attributable. - versions: on pull requests, any skill whose content changed against the base must bump metadata.version. Pure moves with identical content are ignored, so restructures pass; new skills pass. CONTRIBUTING documents both rules and the local commands. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Collaborator
Author
|
@jackieros - moved the restructure to here and added the 2 ci checks for links with no referrer and version bumping. |
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
2 participants
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.
Moves the skills catalog to a flat category layout, adds a CI check to catch skills silently dropping out of discovery, and records the authoring conventions later skills must follow. No shipped skill changes behaviour.
Split out of #21 per review so the restructure can ship first. #21 now carries only the
cloudinary-uploadskill and is stacked on this branch.Why this layout
skills/<category>/<name>/SKILL.mdat exactly depth two. Folders are invisible to users and agents, so moving a skill does not break installs.cloudinary-nextkeeps its name. Renaming would orphan existing installs.use-cases/andutilities/are not created here. They will be created when we add skills in those categories.Open questions from #21 review