microsoft / microsoft/modernize-java
Adopt Agent Plugins 1.0
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 3
- Forks
- 0
- Ø Merge
- 7 Std. 29 Min.
- Gemergte PRs (30 T.)
- 1
Beschreibung
Adopt Agent Plugins 1.0
Why this matters
Agent Plugins 1.0 is an open, vendor-neutral standard for packaging reusable Agent Skills and MCP servers so they can be discovered and loaded consistently across compatible clients.
Adopting the standard would make this plugin easier to consume across GitHub Copilot, Codex, Cursor, VS Code, and other compatible clients without requiring client-specific repackaging or duplicated component structures.
Resources:
- Agent Plugins
- Agent Plugins 1.0 specification
- GitHub Changelog: Agent Plugins 1.0 in VS Code, Copilot CLI, and the Copilot app
Requested changes
Please update this plugin to conform to the Agent Plugins 1.0 specification:
- Move
plugin.jsonto the root of the plugin directory. - Add the
$schemafield:
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json"
}
- Align the manifest fields with the Agent Plugins 1.0 schema.
- Place portable Agent Skills under the plugin-root
skills/directory. - Place MCP server configuration in the plugin-root
mcp.jsonfile, where applicable. - Use the
com.github.copilot/namespace for GitHub Copilot-specific components and metadata that are outside the portable Agent Plugins contract, such as agents, hooks, instructions, and extensions (including canvases).
The intended structure is similar to:
plugin/
├── plugin.json
├── skills/
│ └── <skill>/
│ └── SKILL.md
├── mcp.json
└── com.github.copilot/
└── <GitHub Copilot-specific components>
Compatibility considerations
If this repository also supports Claude Code's plugin format, please retain the Claude-specific manifest and layout as needed. Claude Code does not currently support the Agent Plugins 1.0 specification, so .claude/plugin.json may still be required for Claude Code compatibility.
However, the portable Agent Plugins manifest should live at the plugin root, and portable components should follow the standard locations described in the specification.
If the current plugin uses a non-standard location for any of the following, please consider moving or exposing them through the standard layout:
- Skills should be discoverable under the plugin-root
skills/directory. - MCP configuration should be available through the plugin-root
mcp.jsonfile. - Client-specific files should be placed under the appropriate reverse-domain namespace, such as
com.github.copilot/.
This would allow the plugin to support multiple clients while preserving any existing client-specific integrations.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Lies die Agent Plugins 1.0-Spezifikation und untersuche das aktuelle Plugin-Layout, insbesondere plugin.json, .claude/plugin.json, skills/, mcp.json und alle GitHub-Copilot-spezifischen Dateien. Vergleiche die bestehende Struktur mit dem angeforderten Root-Manifest, den portablen Verzeichnissen und dem com.github.copilot/-Namespace. Die Aufgabe ist erledigt, wenn das portable Layout konform ist und dabei die Claude Code-Kompatibilität, wo erforderlich, erhalten bleibt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github, vscode
- Bereich
- tooling
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 62/100