archestra-ai
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Appa Guide · archestra-ai bundleGuide an operator through configuring OpenAPPA on the host you run in — Claude Code or a kagent cluster. Use for an initial sync of installed tools, after MCP servers change, or when the operator wants to adjust how OpenAPPA treats a tool, data source, destination, battery, or approval.
- ▌ Appa Debug · archestra-aiExplain what the APPA runtime recorded for a gated Claude Code session — which tool calls ran, which were blocked, and why — in plain language, by reading the runtime's SQLite database and the session transcript. Use when the user asks why a tool call was blocked, what happened in a gated session, or wants an APPA decision log explained.
- ▌ Archestra MCP Catalog Entry · archestra-aiUse when adding a new MCP server to the public MCP catalog (mcp-catalog/data) or preparing/reviewing a catalog-entry PR. Derives the entry name from the server URL, live-probes remote servers to fill in tools/transport/auth, fetches and encodes the icon, and validates the manifest against the catalog schema before opening the PR.
- ▌ Managing Archestra Releases · archestra-ai bundleRuns rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
- ▌ Archestra Dev Bench Analysis · archestra-ai bundleMap-reduce a finished archestra-bench run into a Tier-1/Tier-2 improvement report using Claude subagents (same analysis as the Rust analyzer, no API key).
- ▌ Archestra Dev Override Sweep · archestra-aiUse when asked to sweep, clean up, or revisit pnpm overrides and minimumReleaseAge exclusions in platform/pnpm-workspace.yaml — unwinding a matured temporary CVE pin once its fix has cleared the 7-day window, or removing an override the dependency graph has made redundant. This skill only sweeps existing pins; it does not author new CVE fixes.
- ▌ Archestra Dev Interactions Migrations · archestra-aiUse BEFORE writing or running any Drizzle migration that touches the `interactions` table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy. Covers which operations are safe vs table-rewriting/lock-taking, the "never rebuild an index in a transactional migration" rule, and a read-only audit procedure against the GKE staging database to size the risk first.
- ▌ Migrate To Archestra · archestra-ai bundleMigrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
- ▌ Archestra Dev E2e · archestra-aiUse when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
- ▌ Archestra Pr Hygiene · archestra-aiUse when opening or updating an Archestra pull request to write an accurate conventional title and a practical, evidence-based description.
- ▌ Archestra Dev Backend · archestra-aiUse when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
- ▌ Archestra Dev Testing · archestra-aiUse when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
- ▌ Archestra Docs Writer · archestra-aiUse when writing or editing Archestra documentation pages under docs/pages/ — new feature docs, page rewrites, tone or copy fixes, or capturing docs screenshots.
- ▌ Archestra Dev Frontend · archestra-aiUse when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
- ▌ Access Request Intake · archestra-aiCollect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.
- ▌ Archestra Dev Rust Napi · archestra-aiUse when editing Rust in this repo — the NAPI crates under platform/archestra-rs (app-runtime, image, and sandbox core/-rs crate pairs plus napi-loader, with their generated TypeScript bindings) or the standalone ai-labs Rust workspace (core/runner/cli/analyzer/dashboard) — including Rust build/test checks.
- ▌ Archestra Dev Migrations · archestra-ai bundleUse when changing Drizzle schemas, generating migrations, editing migration SQL, creating data-only migrations, diagnosing drizzle-kit check failures, or resolving migration/generated-client conflicts.
- ▌ Archestra Dev Investigate · archestra-aiUse when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.
- ▌ Archestra Dev Backend Tests · archestra-aiUse when writing or modifying Archestra backend unit tests (platform/backend/src/**/*.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
- ▌ Archestra Dev LLM Providers · archestra-aiUse when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
- ▌ Archestra Dev Observability · archestra-aiUse when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.