Skip to content

feat: add top-level plugin.json for elasticsearch and sync it via CI - #46

Merged
MattDevy merged 4 commits into
mainfrom
feat/elasticsearch-top-level-plugin-json
May 28, 2026
Merged

feat: add top-level plugin.json for elasticsearch and sync it via CI#46
MattDevy merged 4 commits into
mainfrom
feat/elasticsearch-top-level-plugin-json

Conversation

@flobernd

Copy link
Copy Markdown
Member

Summary

  • Adds plugins/elasticsearch/plugin.json — a top-level npm-style manifest for the Elasticsearch plugin with a skills list, author.url, and homepage fields not present in the .claude-plugin/ variant
  • Updates .github/workflows/version-sync.yml to include plugins/elasticsearch/plugin.json alongside the existing .claude-plugin/plugin.json so the release CI keeps all version fields in sync

As requested by @gregorycrist

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.
@gregorycrist

Copy link
Copy Markdown

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

@gregorycrist

Copy link
Copy Markdown

@nayrttam or @MattDevy Could you get this reviewed and approved today? I would like to publish a blog about using this GitHub Copilot CLI plugin next week for the Microsoft Build developer conference. Thanks!

@MattDevy

Copy link
Copy Markdown
Contributor

Hey @gregorycrist @flobernd is there a reason we're only adding this for the elasticsearch plugin, and not the other namespaces?

@gregorycrist

Copy link
Copy Markdown

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?

Comment thread plugins/elasticsearch/plugin.json Outdated
@gregorycrist

gregorycrist commented May 28, 2026

Copy link
Copy Markdown

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.

@MattDevy

Copy link
Copy Markdown
Contributor

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 .github/plugin/marketplace.json like https://github.com/github/copilot-plugins/blob/main/.github/plugin/marketplace.json ?

@gregorycrist

Copy link
Copy Markdown

yes on the marketplace.json.

@Anaethelion

Copy link
Copy Markdown
Contributor

This is good, please make sure this doesn't break the existing integrations and marketplaces before we move forward. :)

@MattDevy

Copy link
Copy Markdown
Contributor

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 ./plugins folder, only ./skills/** so we're all there

@MattDevy
MattDevy merged commit e09318c into main May 28, 2026
2 checks passed
@MattDevy
MattDevy deleted the feat/elasticsearch-top-level-plugin-json branch May 28, 2026 14:58
@gregorycrist

Copy link
Copy Markdown

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'.
❌ [plugin:elastic-elasticsearch] plugin.json has no 'skills' field — required.
{Ansi.Red}Plugin spec conformance failures — fix the errors above.{Ansi.Reset}

@MattDevy

Copy link
Copy Markdown
Contributor

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'. ❌ [plugin:elastic-elasticsearch] plugin.json has no 'skills' field — required. {Ansi.Red}Plugin spec conformance failures — fix the errors above.{Ansi.Reset}

Hmmm interesting, it seems their validation is tighter than copilot itself

…/agent-skills   automation/skills-sync $   v25.8.1   16:37
❯ copilot plugin marketplace add elastic/agent-skills
Marketplace "elastic-agent-skills" added successfully.

 …/agent-skills   automation/skills-sync $   v25.8.1   16:37
❯ copilot plugin install elastic-elasticsearch@elastic-agent-skills
copilot plugin install elastic-kibana@elastic-agent-skills
copilot plugin install elastic-observability@elastic-agent-skills
copilot plugin install elastic-security@elastic-agent-skills
copilot plugin install elastic-cloud@elastic-agent-skills
Plugin "elastic-elasticsearch" installed successfully. Installed 7 skills.
Plugin "elastic-kibana" installed successfully. Installed 8 skills.
Plugin "elastic-observability" installed successfully. Installed 11 skills.
Plugin "elastic-security" installed successfully. Installed 4 skills.
Plugin "elastic-cloud" installed successfully. Installed 5 skills.

@gregorycrist

Copy link
Copy Markdown

definitely. Here is the PR issue from awesome-copilot. github/awesome-copilot#1865

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants