Skip to content
Skills Library
Programming · Automation

qa-target-setup

/qa-target-setup

Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".

Licence
MIT
Last repository change
06.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".

Triggers from the description

setup targetadd targetconfigure appnew target

Arguments

/qa-target-setup <url> [--name <id>] [--shared]
Original author description

Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".

How it works

  1. Flow
Original SKILL.md headings · 139 lines, 843 words
SKILL.md preview
---
name: qa-target-setup
description: >
  Interactive setup for a new target application. Navigates to the URL, detects auth requirements,
  walks through login flow creation, auto-detects scope, and saves target config.
  Use when user says: "setup target", "add target", "configure app", "new target".
argument-hint: "<url> [--name <id>] [--shared]"
allowed-tools: Bash(playwright-cli:*), Bash(npx playwright-cli:*), Bash(npx playwright:*), Bash(qualiow:*), Bash(npx -y -p qualiow-exploratory-testing qualiow:*), Read, Write, Glob, Grep
---

# Target Application Setup

Interactive wizard that writes a target config. By default it writes the **project-local**
`qa/target.yml` (the file every session skill reads when no `--target` is given; see
`${CLAUDE_SKILL_DIR}/../qa-explore/references/paths.md`). With `--shared`, it writes
`data/targets/<name>.yml` instead, for a target the whole team shares by name. Keep internal
hostnames in `qa/target.yml` or in `data/targets/local-*.yml` (both gitignored patterns).

Security: `${CLAUDE_SKILL_DIR}/../qa-explore/references/security-rules.md` applies (the
production rule decides the `safety:` block; never write a credential value into YAML).
The fields written here are what the session skills read to fill `**Environment:**` and the
session metadata in `${CLAUDE_SKILL_DIR}/../qa-explore/references/output-contract.md`, so
`id`, `environment.kind` and `base_url` must be the real ones.

## Flow

### 1. Gather Basic Info

Ask the user for:
- **Target name** (slug, e.g. `company-staging`; becomes `id:` and, with `--shared`, the filename)
- **Base URL** (e.g. `https://staging.company.com`)
- **Domain type** (`ecommerce`, `saas`, `fintech`, `marketing`, `identity`, or auto-detect against `<data>/domains/*.yml`)

Apply the production rule to the hostname now and tell the user what it decided.

### 2. Navigate and Analyze

Use the session id `-s=setup-<HHmm>-<name>` on every command (omitted below):

```bash
playwright-cli open <base_url>
playwright-cli snapshot
```

From the snapshot, detect:
- Is this a login page? (password fields, "Sign in" buttons)
- What's the main navigation structure?
- What kind of application is this? (helps auto-detect the domain)

### 3. Handle Authentication

**If no login detected:** set `auth.strategy: none` and skip to step 4.

**If login detected**, ask which strategy to use:

**Option A: Storage State (recommended)**
1. Ask the user for the env var **names** for username and password (values go in `qa/.env`).
2. Log in via playwright-cli. The username may be filled as a literal; the password is filled
   by `qualiow auth fill`, which reads the variable itself so the value never passes through
   you. `--session` takes the `setup-<HHmm>-<name>` id without `-s=`; write `qualiow` as the
   prefix resolved from `${CLAUDE_SKILL_DIR}/../qa-explore/references/paths.md` (CLI):
   ```bash
   playwright-cli snapshot  # find form fields
   playwright-cli fill <email_ref> "<username value>"
   qualiow auth fill --session <sid> --ref <password_ref> --env <the password env var NAME> --target <name>
   playwright-cli click <submit_ref>
   ```
   `auth fill` types only a login credential the target declares. With names other than
   `QA_USER`/`QA_PASS`, write the target file's `auth.credentials` block (step 5) before logging
   in. Exit 2 means the variable is not set in `qa/.env` yet: ask the user to add it there, never
   to paste the value into the conversation.
   If the identity provider needs MFA, reopen headed (`playwright-cli open <login_url> --headed`) and let the user complete it by hand; never automate an MFA challenge.
3. Verify login succeeded (snapshot shows dashboard/profile).
4. Save state: `playwright-cli state-save .auth/<name>.json`
5. Set `auth.strategy: storage_state` with `state_file: ".auth/<name>.json"`, plus `auth.credentials.username` / `auth.credentials.password` naming the env vars so a session can re-login when the state expires.

**Option B: Token**
1. Ask for the token env var name and the injection method (cookie or localStorage).
2. Set `auth.strategy: token`, `auth.token: <ENV_VAR_NAME>`.

### 4. Detect Scope

After login (or on the landing page):
```bash
playwright-cli snapshot
```

From the snapshot, identify:
- Top-level navigation sections → suggest as `scope.start_pages`
- Suggest `scope.include_patterns` based on the URL structure
- Suggest `scope.exclude_patterns` for common exclusions (`/admin`, `/api`, `*.pdf`)
- `scope.max_depth` (default 3)

Ask the user to confirm/modify scope.

### 5. Configure Browser Settings

Suggest defaults:
- `headless: false` (so the user can watch)
- `viewport: { width: 1280, height: 720 }`
- Ask whether mobile emulation is needed (`browser.device`, e.g. `iPhone 15`, used with `playwright-cli open --device="iPhone 15"`, or `--mobile` for a generic mobile device — the two flags are mutually exclusive, and `--mobile` is unsupported on Firefox)

### 6. Safety Settings

- If the production rule fired, or the user says this is production: `safety.read_only: true`, `safety.no_form_submit: true`.
- Otherwise: `safety.read_only: false`, `safety.no_form_submit: false`.

### 7. Save Config

Write `qa/target.yml` (default) or `data/targets/<name>.yml` (`--shared`) with all gathered
configuration; `id` equals the target name. Then close the session:

```bash
playwright-cli close
playwright-cli delete-data
```

Update `qa/.env.example` (create it if missing) with every env var name the config references,
each as a commented `# NAME=` line. Never write values.

### 8. Confirm

Present the saved config to the user:
- Target name and URL
- Auth strategy configured
- Scope defined
- How to use: `/qa-explore` (picks up `qa/target.yml`) or `/qa-explore --target <name>` for a shared target

### 9. Optional — Offer Playwright Test Agents Bootstrap

If the user plans to author full Playwright tests against this target later (not just
exploratory sessions), offer to scaffold the Test Agents workspace now while credentials and
scope are already loaded:

```bash
npx playwright init-agents --loop=claude
```

With `--loop=claude` this writes the planner / generator / healer definitions into
`.claude/agents/`, a `.mcp.json` registering the `playwright-test` server, and a `specs/`
scaffold with a seed spec if the project has none (Playwright 1.56+; other loops: `codex`,
`copilot`, `opencode`, `vscode`, `vscode-legacy`). It is **strictly optional**; declining does not affect
the target config just written. If the user accepts, note in the config's `notes` field that
Test Agents are scaffolded.

This step requires `@playwright/test` and a `playwright.config.*` in the target project. If
either is missing, skip it silently.

Versions

The database has no other skills named qa-target-setup.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version f4ef05f00059 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100qa-setup
    Run /qa-setup once per project to configure the QA Stack. Use it before the first /qa-mode run, when reply language, spawn caps, execution mode, the issue tracker, or the browser driver change. It detects capabilities, writes the config file the router reads, and reports what it found.
  • 90setup
    One-time project setup for the dev-pipeline plugin. Detects the project's stack and build/test commands, asks a few short questions, and writes dev-pipeline.json in the project root. Use when the user says "set up dev-pipeline", "configure the pipeline", "change which model does…
  • 100setup-init
    Interactive first-run setup. Auto-detects the user's repos, frameworks, event SDKs, and test patterns, asks ONLY the questions detection can't answer, then writes a complete .manifest/repos.yml with zero placeholders. Use on first run, when `/setup` finds no repos.yml, or when…
  • 100create-auth
    Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or…
  • 100auth-tool-cloudbase
    CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before…
  • 100create-auth
    Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.