Repository navigation
feat(plugin): add the Kiro power, the Antigravity manifest and support/privacy sections - #41
Open
sahilsunny wants to merge 2 commits into
Open
sahilsunny wants to merge 2 commits into
sahilsunny wants to merge 2 commits into
Conversation
…t/privacy sections Kiro Powers and Google Antigravity each need their own manifest: a Kiro power is an Agent Plugins package (plugin.json + mcp.json) and Antigravity reads .antigravity-plugin/plugin.json. Kiro reviewers also require a privacy policy link and support contact in the README. The marketplace contact address moves to contact@scrapingbee.com.
Kiro does not expand ${VAR} inside a power's mcp.json headers
(kirodotdev/Kiro#11258), so the Bearer header reached the server literally.
mcp-remote expands the variable itself; verified with a tools/call through
the bridge.
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
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.
What
plugins/scrapingbee-kiro/: a Kiro power in the Agent Plugins format (plugin.json,mcp.jsonconnectinghttps://mcp.scrapingbee.com/mcpwithAuthorization: Bearer ${SCRAPINGBEE_API_KEY}, README, LICENSE, synced skills). Added toscripts/sync-skills.sh.plugins/scrapingbee-cli/.antigravity-plugin/plugin.jsonfor Google Antigravity (skills-only, logo, three suggested prompts).author.emailin the Copilot manifest.support@scrapingbee.com(does not exist) tocontact@scrapingbee.comin both marketplace files.Why
One batch of repo changes for the next round of marketplace submissions. Kiro Powers need a
plugin.json+mcp.jsonpackage root and a README with a privacy policy link and support contact; Antigravity reads its own manifest. The Kiro package is a separate folder because Cursor also loads Agent Plugins from a rootplugin.json, which would bypass the Cursor-onlyvariablesprompt inplugins/scrapingbee-cursor/.Verification
https://antigravity.google/schemas/v1/plugin.json(additionalProperties: false, max 3 prompts) and the Kiro files against the Agent Pluginspluginandmcpschemas (type: streamable-http,headersstring map).plugins/scrapingbee-kiro/skillsis byte-identical to.agents/skillsafterscripts/sync-skills.sh.support@scrapingbee.comleft in tracked files.