mirror of
https://github.com/aws/agent-toolkit-for-aws.git
synced 2026-09-14 14:30:26 +08:00
c0991f463b
Cursor's plugin system (github.com/cursor/plugins) reads a root .cursor-plugin/marketplace.json that indexes plugins, each with its own .cursor-plugin/plugin.json — the same multi-plugin layout this repo already uses for Claude Code (.claude-plugin) and Codex (.codex-plugin). Add Cursor as a third supported agent: - .cursor-plugin/marketplace.json indexing all three plugins, and a .cursor-plugin/plugin.json in each of aws-core, aws-agents, and aws-data-analytics. Descriptions and keywords enumerate the bundled-skill domains (matching the enriched Claude/Codex manifests); skills point at ./skills/ and mcpServers reuses the existing ./.mcp.json, so no config is duplicated. OpenSearch keywords are included on aws-core (Bedrock Knowledge Bases support opensearch_serverless / opensearch_managed_cluster vector stores) but not on aws-agents or aws-data-analytics, neither of which bundles a skill that operates OpenSearch. - README: add a Cursor quick-start section (add the repo as a team marketplace via Settings -> Plugins -> Import from Repo) and list Cursor alongside Claude Code, Codex, and Kiro. - tools/validate.py: validate the Cursor marketplace index and each .cursor-plugin/plugin.json, mirroring the existing Claude/Codex checks (name present and matching the plugin directory). Manifests validate against Cursor's published marketplace.schema.json and plugin.schema.json (ajv). python3 tools/validate.py, markdownlint, and gitleaks all pass. Signed-off-by: Andre Kurait <akurait@amazon.com>