Skip to content

feat(kiro): add BrowserStack Kiro power - #536

Merged
gaurav-singh-9227 merged 6 commits into
browserstack:mainfrom
SavioBS629:feat/kiro-power
Oct 30, 2026
Merged

gaurav-singh-9227 merged 6 commits into
browserstack:mainfrom
SavioBS629:feat/kiro-power

Conversation

@SavioBS629

@SavioBS629 SavioBS629 commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Adds a Kiro power for the BrowserStack MCP server at integrations/kiro-power/, for listing in the Kiro Powers directory.

A power is an Agent Plugins package: a manifest, an MCP config pointing at the hosted server, and skills describing each BrowserStack workflow. Kiro activates it from keywords in the user's prompt and keeps it out of context otherwise.

Files

Path What
plugin.json name, version, description, author, activation keywords, licence AGPL-3.0-only, homepage, repository. Validates against Agent Plugins 1.0.0
mcp.json streamable-http → https://mcp.browserstack.com/mcp; Kiro runs the OAuth sign-in, no credentials in config. Validates against Agent Plugins 1.0.0
skills/browserstack/ Hub: routes the user's wording to a product skill; shared rules and result card
skills/live/, skills/app-live/ Manual sessions on real browsers and devices
skills/automate/, skills/app-automate/ SDK setup, run, and failure debugging (RCA → logs by session type → self-healed selectors)
skills/accessibility/ Scans, reports from scans/builds/links, comparisons, auth configs, WCAG questions
skills/test-management/, skills/test-reporting-analytics/ Capability-registry flow with confirm-before-write, plus references/workflows.md built from the docs workflow tables

Skills are named after BrowserStack products. Percy is not included yet.

README

  • Support email and privacy-policy link under Support.
  • A pointer to the power, with the subfolder URL for Kiro's GitHub import.

Depends on #486

Kiro renders every tool description into one activation result capped at 30,000 characters. The current tool set exceeds it, so Kiro truncates the list and the agent guesses tool names. #486 brings the set under the cap. This PR can merge independently, but the power should be listed only once #486 is released.

Testing

Kiro CLI with --v3, against a build that includes #486, tracing each tool call from Kiro's session files:

Flow Result
Activation under 30,000 chars, not truncated
Live — desktop and Galaxy S23 correct tool and arguments on first call
Automate failure (Playwright) listBuildId → listTestIds → fetchRCA; correct root cause and fix
App Automate failure (iOS) same chain; correct cause and fix
Accessibility scan / fetch issues / WCAG question correct tool and arguments on first call
Build insights correct
Test Management projects, test cases, folders capability registry, including product-clash handling; correct
Test Reporting recent builds capability registry, correct

🤖 Generated with Claude Code

SavioBS629 and others added 4 commits October 14, 2026 12:27
Adds integrations/kiro-power, an Agent Plugins package for Kiro's Powers
directory: plugin.json (product-approved activation keywords), mcp.json
pointing at the hosted Streamable HTTP server, and one skill per
BrowserStack product: live, app-live, automate, app-automate,
accessibility, test-management, test-reporting-analytics, plus a hub
skill that routes by the user's phrasing.

Automate, App Automate, Live, App Live and Accessibility skills were
validated against the hosted server on real builds; each carries a
"validated behaviour" section. Test Management and TRA skills drive the
capability registry and ship the docs workflow tables as references.

README: support email and privacy policy link (required by the Kiro
submission form) and a pointer to the power.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The "Validated behaviour" sections recorded one-off test results
(specific builds, resolved versions, a made-up app id). The rules they
support are already stated in each skill, so remove the logs and reword
the few lines that still read as test notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README conflict: kept main's new Prerequisites section and placed the
Kiro power note above it. Support email and privacy policy lines merged
cleanly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- accessibility: issues can come from scans, builds, workflow and app
  reports or a dashboard link; earlier scans are found via
  searchCapability instead of re-scanning; compareWith shows new and
  resolved issues; wcagVersion option; lost auth config ids via
  askBrowserStackAI (a11y).
- app-automate: setup accepts a local app or a bs:// id from an earlier
  upload.
- automate, app-automate: pass test ids to fetchRCA as numbers;
  listTestIds returns strings and the first call was rejected in every
  Kiro test run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML (base), Organization UI (inherited), Workspace UI (inherited); Enforced overrides: Organization
  • Review profile: ASSERTIVE
  • Plan: Enterprise
  • Run ID: 99734ebe-5321-4205-aad9-ea8137dcfe39

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

SavioBS629 and others added 2 commits October 30, 2026 17:07
- README: give the subfolder tree URL for GitHub import, and the
  import-from-folder alternative
- automate, app-automate: logTypes accepts several types per call
- accessibility: drop the askBrowserStackAI and get-by-id steps; handle
  clients without elicitation without asking for a password in chat
- test-management, test-reporting-analytics: drop workflow counts

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- test-management: named write tools need the same confirmation as
  registry writes
- test-reporting-analytics: confirm before the capabilities that write
- skill descriptions carry their trigger phrases, which Kiro matches on
- accessibility: advanced rules run by default
- automate, app-automate: name getFailureLogs in the logs step; setup
  step count varies
- flaky and new-failure flags come from listTestIds only
- hub skill: drop the local-server note; mark the file upload tools as
  local-server only

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gaurav-singh-9227
gaurav-singh-9227 merged commit 45928a6 into browserstack:main Oct 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants