qa

Verify Centaur user-facing agent workflows via Slack smoke tests.

4|2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/useatrium/atrium --skill qa-useatrium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/useatrium/atrium/tree/main/centaur/.agents/skills/qa
Command: npx skills add https://github.com/useatrium/atrium --skill qa-useatrium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, openssl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies that a running Centaur deployment works through the user-facing Slack agent path, rather than merely confirming that isolated APIs respond.

Core Features & Use Cases

  • End-to-End Smoke Testing: Validates tool loading, Slack threads, file uploads and downloads, company context, logs, metrics, and authenticated AI-team tools.
  • Deployment Readiness Checks: Supports extended checks for staging, previews, promotion gates, concurrency, scheduler behavior, and deadlock detection.
  • Failure Triage and Reporting: Classifies authentication, permission, DNS, upstream, schema, timeout, and runtime failures, then produces a concise Slack-friendly pass/fail report with evidence.
  • Use Case: When preparing a new Centaur release, run the smoke test from a fresh Slack thread to confirm that agents can respond, exchange files, access company context, and reach observability services before promotion.

Quick Start

Run the QA skill from a new Slack thread in a channel where the Centaur bot is present and request an end-to-end smoke test of the running deployment.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end smoke tests for a Slack agent deployment?

End-to-end smoke tests for a Slack agent deployment run directly from a new Slack thread where the bot is present, validating tool loading, file exchanges, and observability before generating a pass/fail report.

What does integration testing for a Slackbot deployment actually verify?

Integration testing for a Slackbot deployment verifies the complete user-facing agent workflow, checking stack health, deployment readiness, file exchange, company context, concurrency, and authenticated tool access.

Do I need specific tools to check deployment readiness for Slack agents?

Checking deployment readiness for Slack agents requires jq, curl, and openssl, alongside a running Slackbot environment and valid Slack signing credentials to validate integration successfully.

Why does my Slack agent smoke test fail during promotion checks?

Slack agent smoke tests fail during promotion checks due to authentication, permission, DNS, upstream, schema, timeout, or runtime failures, which are classified and reported with concise evidence.

Can I test concurrency and deadlock detection for Slack agents?

Testing concurrency and deadlock detection for Slack agents is supported through extended deployment readiness checks that validate scheduler behavior and concurrent tool interactions.

What is the best way to validate observability for a Centaur deployment?

Validating observability for a Centaur deployment involves running smoke tests that check if agents can reach logs and metrics services through the Slack path, ensuring stack health before release promotion.