Adopt Agent Plugins 1.0

.claude/plugin.json、plugin.json、任意の skills/、MCP 設定、GitHub Copilot 固有のファイルを含む、現在のプラグインレイアウトを調査します。これらの場所とマニフェストフィールドを Agent Plugins 1.0 仕様と比較します。ポータブルマニフェストとコンポーネントが標準のルート場所を使用し、Claude Code との互換性が維持されていれば完了です。

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.json to the root of the plugin directory.
• Add the $schema field:

{
    "$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.json file, 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.json file.
• 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.