メニュー
Browse Aircall staging or local dev URLs with automatic authentication. USE THIS skill (not the generic agent-browser skill) whenever the target URL contains "aircall" in the hostname (e.g. dashboard.aircall-staging.com, localhost running Aircall).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Find commits on `master` that have not been released yet, map each author to their Slack user ID via email, and draft a Slack message pinging them for prod-release sign-off. Use when the user asks to "check unreleased commits", "ping authors before prod release", or "who hasn't signed off on the release yet" for a GitLab-hosted repo (e.g. dashboard-v4).
Conventions for building components in Aircall's UI libraries — @aircall/ds (design system, Tailwind 4 + Base UI) and @aircall/blocks (higher-level compositions) — as they live in the Aircall Hydra monorepo. Use when adding or refactoring a component in packages/ds or packages/blocks, deciding between a compound component and a prop, wiring variants, polymorphism, or exports. Triggers on "build a DS component", "add a block", or work touching packages/ds / packages/blocks inside Hydra.
Fix a broken Playwright e2e test by reproducing the failure in a real browser FIRST and capturing the live UI, then editing the test once - instead of the blind edit-rerun-repeat loop. Use when an Aircall Playwright e2e test is failing/flaky, a CI e2e job is red, or on "fix this broken test". Leans on agent-browser-aircall-local for auth + portless URLs. Guards against masking a real product regression by editing the test to pass.
Orchestrates Kento's per-ticket dev loop end-to-end: optional Jira ticket → create/reuse a git worktree → implement → debug in the browser → commit, push, open the MR → optionally watch the pipeline. Runs autonomously through setup and implementation, then STOPS at a readiness gate before shipping. Use when the user wants to start work on a ticket/feature/fix, "spin up a worktree and implement", "take this from ticket to MR", or kick off the dev flow. Delegates each step to existing skills — it does not reimplement them.
Drive a fast-forward GitLab "merge train" on Aircall repos — merge a set of approved MRs one-by-one (rebase → arm merge-when-pipeline-succeeds → poll → merge), handling approval-resets, Cursor Bugbot gates, rebase conflicts, and flaky E2E retries. Supervised, CI-paced, human-gated. Use after aircall-react-doctor-pipeline produces Ready MRs, or whenever the user asks to "watch and merge" any batch of approved MRs on an Aircall GitLab repo whose merge_method is ff. Repo-agnostic within Aircall (reads merge settings dynamically); not react-doctor-specific.
Create a GitLab merge request using glab CLI with the first commit message as the title. Use when the user asks to open an MR for the current branch targeting main, or after completing work that needs review.
| name | agent-browser-aircall-local |
| description | Browse Aircall staging or local dev URLs with automatic authentication. USE THIS skill (not the generic agent-browser skill) whenever the target URL contains "aircall" in the hostname (e.g. dashboard.aircall-staging.com, localhost running Aircall). |
Drives an agent-browser session against an Aircall URL, authenticated by injecting auth cookies.
Session name is the --session <NAME> arg: use aircall-local for normal work, a distinct name
per worker for parallel agents.
Local Aircall dev servers run behind the portless proxy at a stable .localhost host —
https://<worktree>.<project>.localhost. Get it with portless list. Don't browse localhost:<port>.
Staging is https://dashboard.aircall-staging.com.
mcp__aircall-personal-tools__aircall_agent_browser_auth({ url: "<URL>" })
This fetches staging JWTs and writes ac-auth.id-token + ac-auth.refresh-token cookies scoped to
the hostname of the URL you pass. The Aircall app — staging AND local sandbox dev — reads those
cookies to authenticate. So:
https://<worktree>.conversations-center-ext.localhost/...). Host must match, or the app finds no
cookie and redirects to the staging login.PUBLIC_SANDBOX_EMAIL/PASSWORD
are in .env.local, which they usually are NOT — always run this auth step.aircall-local. For another session, propagate (see Parallel).# 1. auth against the URL → 2. open → 3. snapshot/interact (re-snapshot after every page change)
mcp__aircall-personal-tools__aircall_agent_browser_auth({ url: "<URL>" })
agent-browser --session aircall-local open "<URL>"
agent-browser --session aircall-local snapshot -i
Headed (--headed): display mode is fixed at first launch, so open first, then auth, then reopen:
agent-browser --session aircall-local open "<URL>" --headed # lands on login — expected
mcp__aircall-personal-tools__aircall_agent_browser_auth({ url: "<URL>" })
agent-browser --session aircall-local open "<URL>" # cookies now applied
Each --session <NAME> is an independent browser context (own cookies); concurrent agents need
distinct names or they clobber each other. The MCP tool only auths aircall-local, so propagate:
agent-browser --session aircall-local cookies get > /tmp/aircall-cookies.json
agent-browser --session <worker> cookies set --curl /tmp/aircall-cookies.json # then open
--headed ignored — a daemon for that session is already running; agent-browser --session <NAME> close, then reopen.Element is covered by <div…> — a popup/drawer overlay is open; close it, and grab a fresh ref after each snapshot (refs shift)./../ collapsing).agent-browser --session <NAME> close, or agent-browser close --all after a fan-out.