ark

Plugin ark from marketplace agents-at-scale-ark in mckinsey/agents-at-scale-ark. Commands read from the repo's manifest — today.

Skills (27)

• a2a-protocol

  Reference documentation for the Agent2Agent (A2A) protocol. Use when building A2A servers or clients, configuring Ark A2AServer resources, debugging A2A communication, or answering questions about the A2A specification, Agent Cards, task lifecycle, streaming, extensions, or protocol bindings.

• Ark Analysis

  Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.

• ark-architecture

  Design architecture for Ark features following existing patterns and principles. Use when planning new features, extending components, or evaluating technical approaches.

• ark-controller-development

  Guidance for developing the Ark Kubernetes operator. Use when modifying Go types, CRDs, controllers, or webhooks. Helps with CRD generation and Helm chart sync issues.

• ark-dependabot-management

  Consolidate open Dependabot PRs into a single integration branch. Use when the user asks to "consolidate dependabot", "merge dependabot PRs", "batch dependency updates", or mentions dependabot PR management.

• ark-sdk-development

  Regenerate and debug types across the ARK stack (SDK, API, Dashboard). Use when fixing TypeScript type errors in ark-dashboard, updating types after CRD changes, regenerating types.ts from OpenAPI spec, debugging "Property does not exist on type" schema errors, or adding custom SDK functionality via

• ark-setup-cluster

  Set up and install the Ark platform in a Kubernetes cluster. Supports default mode (existing cluster) and isolated e2e testing mode (dedicated Kind cluster). Use when the user wants to install, deploy, test, or configure Ark.

• ark-chainsaw-testing

  Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.

• Ark Dashboard and UI Testing

  Test the Ark Dashboard and UI with Playwright and create PRs with screenshots. Use this skill when testing dashboard UI, taking screenshots for PRs, or validating dashboard changes.

• ark-documentation

  Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.

• issue-creation

  Structured workflow for drafting NEW GitHub issues with codebase research, duplicate detection, and testing approach. Always asks clarifying questions and shows the draft for approval before creating. For searching, listing, viewing, or updating existing issues, use the "issues" skill instead.

• ark-issues

  Search, list, view, and update existing GitHub issues. Primary use case is CVE tracking and security vulnerability issue management. Used by the ark-security-patcher agent. For drafting NEW issues with research and task breakdowns, use the "issue-creation" skill instead.

• multi-branch-cluster-setup

  Set up N isolated minikube clusters, one per Git worktree, for parallel Ark branch development. Use when the user wants to run multiple branches simultaneously, set up isolated Kubernetes environments per branch, create git worktrees with dedicated clusters, or configure devspace contexts for multi-

• openspec-apply-change

  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

• openspec-archive-change

  Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

• openspec-bulk-archive-change

  Archive multiple completed changes at once. Use when archiving several parallel changes.

• openspec-continue-change

  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

• openspec-explore

  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

• openspec-ff-change

  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

• openspec-new-change

  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

• openspec-onboard

  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

• openspec-sync-specs

  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

• openspec-verify-change

  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

• ark-pentest-issue-resolver

  Resolve common penetration testing issues in Ark. Use when fixing security vulnerabilities from pentest reports, security audits, or OWASP Top 10 issues.

• ark-research

  Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options or evaluating technologies.

• slack-announcement

  Produce a themed Slack post announcing Ark releases. Pulls from BOTH the Ark core repo (mckinsey/agents-at-scale-ark) and the Marketplace repo (mckinsey/agents-at-scale-marketplace), validates docs links, groups features by theme with relevant emoji, and ends with a "Coming next" section sourced fro

• ark-vulnerability-fixer

  CVE research and security patch workflow for Ark. Provides CVE API integration, mitigation strategies, and security-focused PR templates. Works with research, analysis, and setup skills for comprehensive vulnerability fixing.

Slash commands (11)

• /ark:ark-create-crd
• /ark:opsx:apply

  Implement tasks from an OpenSpec change (Experimental)

• /ark:opsx:archive

  Archive a completed change in the experimental workflow

• /ark:opsx:bulk-archive

  Archive multiple completed changes at once

• /ark:opsx:continue

  Continue working on a change - create the next artifact (Experimental)

• /ark:opsx:explore

  Enter explore mode - think through ideas, investigate problems, clarify requirements

• /ark:opsx:ff

  Create a change and generate all artifacts needed for implementation in one go

• /ark:opsx:new

  Start a new change using the experimental artifact workflow (OPSX)

• /ark:opsx:onboard

  Guided onboarding - walk through a complete OpenSpec workflow cycle with narration

• /ark:opsx:sync

  Sync delta specs from a change to main specs

• /ark:opsx:verify

  Verify implementation matches change artifacts before archiving

Subagents (6)

• ark-architect

  Use this agent when designing architecture for new Ark features, planning component extensions, or evaluating technical approaches that need to align with existing codebase patterns. Examples:\n\n- User: "I need to add a new CRD for managing prompt templates"\n Assistant: "I'll use the ark-architec

• ark-build-manager

  Triage and fix CI/CD build failures in Ark. Use when builds are failing, CI checks are red, tests are broken, or the user asks to "check the build", "fix CI", "why is the build failing", or "triage build issues".\n\n- User: "The build is red, can you check it?"\n Assistant: "I'll use the ark-build-

• ark-protocol-orchestrator

  Orchestrates multi-phase Ark feature development using the task folder protocol. Manages task lifecycle, coordinates specialist agents (ark-architect, ark-prototyper), and tracks progress through objectives → architecture → prototype → outcome phases.

• ark-prototyper

  Use this agent to build minimal, verifiable prototypes of Ark features. It makes the smallest changes needed to demonstrate the architecture and user experience - minimal CRD updates, simple API endpoints, basic CLI commands, and dashboard UI. Examples:\n\n- User: "Prototype the ark-broker feature"\

• ark-security-patcher

  Fix security vulnerabilities in Ark by researching CVEs, analyzing impact, proposing mitigations, implementing patches, and creating PRs. Use when the user reports CVE numbers or security issues that need fixing in Ark. Examples:\n\n- User: "Fix CVE-2025-55183 in Ark"\n Assistant: "I'll use the ark

• ark-researcher

  Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options, evaluating technologies, or investigating how to solve a technical problem.