Follow the upstream skills/ vs dev-skills/ split - #1
Merged
Merged
Conversation
galaxyproject/galaxy-skills#35 reorganizes that repo into two trees: skills/ for using Galaxy and dev-skills/ for building it, with no harness scanning the latter. sync-skills.sh rsyncs the upstream root, so once that lands it would vendor both trees a level deeper and gen-manifests would register all 16 skills as one bundle, which quietly undoes the split. So each tree now gets vendored into its own plugin instead: galaxy-skills stays the analyst set and galaxy-dev-skills carries tool-dev, nf-to-galaxy, update-usegalaxy-tool, trackhubs and hub-news-posts. Nothing is lost, people just install the half they want. Skill files under plugins/*/skills/ are the output of the sync, run against the #35 branch so CI can see the end state -- re-pin to main once it merges. The vendored tree no longer carries upstream's AGENTS.md and README.md, since those describe the whole repo rather than what ends up in a plugin. CI needed updating either way: both jobs asserted galaxy-skills:tool-dev and nf-process-to-galaxy-tool, which now live in the other plugin. Also dropped the galaxy-skills#36 frontmatter workaround from the Codex validator step -- #35 quotes the argument-hint value, so all 76 skills parse as strict YAML and the validator can run against every plugin without an exception.
Member
Author
|
@nekrut if you want to merge galaxyproject/galaxy-skills#35 and then this one, I think that gets it all into the right shape. Only loose end after that is re-pinning both galaxy-skills mirrors to |
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.
galaxyproject/galaxy-skills#35 reorganizes that repo into two trees --
skills/for using Galaxy,dev-skills/for building it, with no harness scanning the latter.sync-skills.shrsyncs the upstream root, so once #35 lands it would vendor both trees a level deeper andgen-manifests.pywould register all 16 skills as one bundle, which quietly undoes the split. Your weekly sync would open that PR on its own.So each tree gets vendored into its own plugin:
galaxy-skillsstays the analyst set (7 skills),galaxy-dev-skillscarriestool-dev,nf-to-galaxy,update-usegalaxy-tool,trackhubsandhub-news-posts(9). Nothing is lost -- people install the half they want, which is your "install only the plugins you need" line applied one level down.Two things worth a look:
The skill files under
plugins/*/skills/are sync output, run against the #35 branch so CI can see the end state. Re-pin tomainonce #35 merges. The vendored tree also stops carrying upstream'sAGENTS.mdandREADME.md, since those describe the whole repo rather than what lands in a plugin -- say the word if you'd rather keep them.CI needed changes either way: both jobs asserted
galaxy-skills:tool-devandnf-process-to-galaxy-tool, which move. I also dropped the #36 workaround from the Codex validator step -- #35 quotes theargument-hintvalue, so all 76 skills parse as strict YAML and the validator can run across every plugin with no exception.validate.pywith pyyaml reports zero warnings now.Locally:
validate.pyOK (4 plugins, 76 skills),claude plugin validate --strictpasses on the marketplace and all four plugins. Skill count stays 76, so both CI thresholds of 70 still hold.Not addressed here, but worth deciding separately:
galaxy-connectoverlaps upstream'sgalaxy-integration, and its advice about searching forget_userrather than assuming a tool-name prefix is better than what upstream says. That probably wants to go upstream so there's one connect skill rather than two.