feat: add top-level plugin.json for elasticsearch and sync it via CI - #46
Conversation
Adds plugins/elasticsearch/plugin.json (npm-style manifest with skills list, author URL, and homepage) and updates version-sync.yml to include it alongside the existing .claude-plugin/plugin.json so the release workflow keeps all three files in sync.
|
Thanks Florian. Once we have the support of GitHub Copilot Plugins, I can request we be added to the awesome-copilot plug in marketplace. https://github.com/github/awesome-copilot/blob/main/docs/README.plugins.md |
|
Hey @gregorycrist @flobernd is there a reason we're only adding this for the elasticsearch plugin, and not the other namespaces? |
|
That is a good idea to include Observability, security, etc. I was just doing the quick and dirty one that I needed for my blog. Should I try to generate the other plugins as well, or are you able to? |
|
the GitHub Copilot CLI plugin reference states that skills is optional and defaults to ./skills/ when omitted. Based on that, i believe it is ok to remove. |
I've added the other plugins, do we also want to add a |
|
yes on the marketplace.json. |
|
This is good, please make sure this doesn't break the existing integrations and marketplaces before we move forward. :) |
I've just checked the claude marketplace / plugins by running locally on the branch, and all looks good there. Cursor doesn't replicate from |
|
Thanks Matt. Now I am getting conflicting information from GitHub Copilot. The awesome-copilot plugin marketplace is telling me that I do need the skills field. Also the plugin name has to match the directory name? Sorry. ❌ [plugin:elastic-elasticsearch] Plugin name 'elastic-elasticsearch' does not match directory name 'elasticsearch'. |
Hmmm interesting, it seems their validation is tighter than copilot itself |
|
definitely. Here is the PR issue from awesome-copilot. github/awesome-copilot#1865 |
Summary
plugins/elasticsearch/plugin.json— a top-level npm-style manifest for the Elasticsearch plugin with askillslist,author.url, andhomepagefields not present in the.claude-plugin/variant.github/workflows/version-sync.ymlto includeplugins/elasticsearch/plugin.jsonalongside the existing.claude-plugin/plugin.jsonso the release CI keeps all version fields in syncAs requested by @gregorycrist