Adopt the Agent Plugins standard for cross-client use - #1
Open
shayhowe wants to merge 1 commit into
Open
Conversation
… use - Add a root plugin.json conforming to the Agent Plugins spec v1.0.0 (closed schema), making the plugin recognizable by any compliant client alongside Claude Code's .claude-plugin/plugin.json. - Add license and compatibility frontmatter to all six skills per the Agent Skills spec, noting the ActiveCampaign MCP server requirement for standalone installs. - README: reframe as a cross-client Agent Plugin, add a compatibility matrix (portable skills/manifest vs. Claude Code-only commands, agents, and MCP userConfig), and add Codex/Cursor setup steps. - No portable mcp.json: the v1 MCP format requires a fixed URL and ActiveCampaign MCP URLs are per-account; each client configures the server directly. Claude Code behavior is unchanged. - Bump version to 0.3.0 in both manifests; add CHANGELOG entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Restructures the plugin to follow the open Agent Plugins specification v1.0.0 so it works across Claude, Codex, Cursor, and any other compliant client — while keeping Claude Code behavior fully unchanged.
plugin.jsonconforming to the Agent Plugins v1.0.0 manifest schema (validated against the published schema). The spec's closed field set excludes Claude-specificdisplayName/userConfig, so.claude-plugin/plugin.jsonremains as-is for Claude Code.licenseandcompatibilityfrontmatter per the Agent Skills spec — the skills are the portable payload other clients install standalone, andcompatibilityflags the ActiveCampaign MCP server requirement.Design decisions
mcp.json. The v1 MCP format requires a fixed server URL (no user-config mechanism), and ActiveCampaign MCP URLs are per-account (yoursubdomain.activehosted.com). MCP therefore stays client-configured: Claude Code keeps prompting viauserConfig, and the README documents manual MCP setup for other clients. Revisit if a future spec version adds user configuration.commands/andagents/stay at the root as Claude Code extras. Spec v1 explicitly scopes these out as "too client-specific for a stable portable contract"; the README matrix documents the boundary.Validation
plugin.jsonvalidated against the publishedplugin.schema.json(closed schema, name pattern,$schemaconst).SKILL.mdfrontmatter blocks YAML-parsed and checked against Agent Skills rules (name matches directory, name charset/length, description ≤ 1024 chars, compatibility ≤ 500 chars)..claude-plugin/plugin.json,.mcp.json) parse-checked; no functional changes to them beyond the version bump.🤖 Generated with Claude Code