Add AI Agent Skills and Knowledge category - #1056
Open
serradura wants to merge 1 commit into
Open
Conversation
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
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.
Adds a category for gems that package knowledge and reusable skills for AI coding agents to read. Four gems qualify today, so it clears the two-entry bar:
agent_skill_parserparses skill files (YAML frontmatter plus Markdown body).bundler-skillsfindsskills/directories inside your dependency gems and links them into the project's agent skills directory.ruby_llm-skillsloads and validates Agent Skills for RubyLLM.okfreads, validates, lints, searches, and serves Open Knowledge Format bundles, the Markdown plus YAML format an agent reads project knowledge from. I maintain this one, which is what prompted the PR, but it is not the reason for the category.I put it under Machine Learning because that is the closest existing group. Developer Tools is arguable, and a separate AI group would be another option if more of these land. Rename or move it as you see fit.
Checklist from the template: all four are published gems, referenced by gem name rather than GitHub path.
I could not run the suite locally since my Ruby is 4.0.5 and
.ruby-versionpins 3.4.1. Instead I checked the three things the specs assert, by loading the whole catalog the waylib/catalog.rbdoes: the shape validates againstjson-schema.yml(30 groups, 219 categories, permalinks and project names matching their patterns), the new category has no duplicates, and all four gem names resolve on RubyGems.