qa-argus-setup

Configure Argus QA browser automation, app settings, and Azure DevOps bug filing workflows.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-argus-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-argus-setup
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-argus-setup
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-argus-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of first-time Argus QA configuration by guiding setup for browser automation, project settings, and Azure DevOps credentials.

Core Features & Use Cases

  • Playwright MCP setup: Detects and installs the required browser automation server when it is missing.
  • Project configuration: Collects the app base URL, login route, and audit scope, then saves a reusable Claude configuration.
  • Azure DevOps readiness: Optionally captures organization, project, area path, and PAT for bug filing workflows.
  • Use Case: A QA engineer can run this once on a new app to prepare the environment for recurring cross-browser audits and bug reporting.

Quick Start

Run the Argus QA setup skill to configure browser automation, project details, and optional Azure DevOps bug filing for your app.

Frequently Asked Questions about qa-argus-setup

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

FAQPage Schema
How do I set up Playwright for browser automation in a new project?

To set up Playwright for browser automation, you need to configure the MCP server and validate local browser tooling. This Skill detects missing browser automation servers, installs the required Playwright MCP, and registers it with Claude Code.

What is the best way to configure Azure DevOps for automated bug filing?

Configuring Azure DevOps for automated bug filing requires capturing your organization, project, area path, and Personal Access Token (PAT). This setup stores credentials securely to enable automated bug reporting workflows directly from your audit results.

How do I prepare my environment for cross-browser audits?

Preparing for cross-browser audits involves configuring your application base URL, login route, and audit scope. This process validates local browser tooling and saves a reusable Claude configuration for recurring automated testing.

Do I need an Azure DevOps PAT to start running Argus QA setup?

An Azure DevOps PAT is optional for the initial setup but required if you want to enable automated bug filing. You can configure browser automation and project settings first, then securely add your credentials and area path later.

Can I reuse my QA configuration across multiple application audits?

Yes, you can reuse your QA configuration across multiple audits. The setup collects your app settings and saves them as a reusable Claude configuration, allowing QA engineers to run recurring cross-browser audits without reconfiguring the environment.

Why is my browser automation setup not working with Claude Code?

Browser automation fails when the Playwright MCP is missing or Claude Code MCP registration is incomplete. This Skill validates local browser tooling, detects missing automation servers, and installs the required components to resolve setup errors.