devskill 2.0.7 → 2.0.8

package/skills/sandbox-npm-install/scripts/install.sh

@@ -0,0 +1,193 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Sandbox npm Install Script
+# Installs node_modules on local ext4 filesystem and symlinks into the workspace.
+# This avoids native binary crashes (esbuild, lightningcss, rollup) on virtiofs.
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(cd "$SCRIPT_DIR/../../.." && pwd)"
+
+# Local ext4 base directory where node_modules is installed to avoid virtiofs crashes.
+# Change this path if your sandbox uses a different local filesystem location.
+readonly DEPS_BASE="/home/agent/project-deps"
+WORKSPACE_CLIENT=""
+INSTALL_PLAYWRIGHT="false"
+
+usage() {
+  cat <<EOF
+Usage: $(basename "$0") [options]
+
+Options:
+  --workspace <path>   Client workspace containing package.json
+  --playwright         Install Playwright Chromium browser
+  --help               Show this help message
+
+Examples:
+  bash scripts/install.sh
+  bash scripts/install.sh --workspace app/client --playwright
+EOF
+}
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --workspace)
+      if [[ -z "${2:-}" ]]; then
+        echo "Error: --workspace requires a path argument"
+        usage
+        exit 1
+      fi
+      WORKSPACE_CLIENT="$2"
+      shift 2
+      ;;
+    --playwright)
+      INSTALL_PLAYWRIGHT="true"
+      shift
+      ;;
+    --help|-h)
+      usage
+      exit 0
+      ;;
+    *)
+      echo "Unknown option: $1"
+      usage
+      exit 1
+      ;;
+  esac
+done
+
+if [[ -z "$WORKSPACE_CLIENT" ]]; then
+  if [[ -f "$PWD/package.json" ]]; then
+    WORKSPACE_CLIENT="$PWD"
+  elif [[ -f "$REPO_ROOT/package.json" ]]; then
+    WORKSPACE_CLIENT="$REPO_ROOT"
+  fi
+fi
+
+if [[ -n "$WORKSPACE_CLIENT" ]]; then
+  WORKSPACE_CLIENT="$(cd "$WORKSPACE_CLIENT" 2>/dev/null && pwd || true)"
+fi
+
+if [[ -z "$WORKSPACE_CLIENT" || ! -f "$WORKSPACE_CLIENT/package.json" ]]; then
+  echo "Could not find a valid workspace client path containing package.json."
+  echo "Use --workspace <path> to specify it explicitly."
+  exit 1
+fi
+
+echo "=== Sandbox npm Install ==="
+echo "Workspace: $WORKSPACE_CLIENT"
+
+# Derive a unique subdirectory from the workspace path relative to the repo root.
+# e.g. /repo/apps/web -> apps-web, /repo -> <repo-basename>
+REL_PATH="${WORKSPACE_CLIENT#"$REPO_ROOT"}"
+REL_PATH="${REL_PATH#/}"
+if [[ -z "$REL_PATH" ]]; then
+  REL_PATH="$(basename "$REPO_ROOT")"
+fi
+# Sanitize: replace path separators with hyphens
+DEPS_SUBDIR="${REL_PATH//\//-}"
+DEPS_DIR="${DEPS_BASE}/${DEPS_SUBDIR}"
+
+echo "Deps dir:  $DEPS_DIR"
+
+# Step 1: Prepare local deps directory
+echo "→ Preparing $DEPS_DIR..."
+if [[ -z "$DEPS_DIR" || "$DEPS_DIR" != "${DEPS_BASE}/"* ]]; then
+  echo "ERROR: DEPS_DIR ('$DEPS_DIR') is not under DEPS_BASE ('$DEPS_BASE'). Aborting."
+  exit 1
+fi
+rm -rf "$DEPS_DIR"
+mkdir -p "$DEPS_DIR"
+chmod 700 "$DEPS_DIR"
+cp "$WORKSPACE_CLIENT/package.json" "$DEPS_DIR/"
+
+# Copy .npmrc if present (needed for private registries / scoped packages)
+# Permissions restricted to owner-only since .npmrc may contain auth tokens
+if [[ -f "$WORKSPACE_CLIENT/.npmrc" ]]; then
+  cp "$WORKSPACE_CLIENT/.npmrc" "$DEPS_DIR/"
+  chmod 600 "$DEPS_DIR/.npmrc"
+fi
+
+if [[ -f "$WORKSPACE_CLIENT/package-lock.json" ]]; then
+  cp "$WORKSPACE_CLIENT/package-lock.json" "$DEPS_DIR/"
+  INSTALL_CMD=(npm ci)
+else
+  echo "! package-lock.json not found; falling back to npm install"
+  INSTALL_CMD=(npm install)
+fi
+
+# Step 2: Install on local ext4
+echo "→ Running ${INSTALL_CMD[*]} on local ext4..."
+cd "$DEPS_DIR" && "${INSTALL_CMD[@]}"
+
+# Step 3: Symlink into workspace
+echo "→ Symlinking node_modules into workspace..."
+cd "$WORKSPACE_CLIENT"
+rm -rf node_modules
+ln -s "$DEPS_DIR/node_modules" node_modules
+
+has_dep() {
+  local dep="$1"
+  node -e "
+    const pkg=require(process.argv[1]);
+    const deps={...(pkg.dependencies||{}),...(pkg.devDependencies||{}),...(pkg.optionalDependencies||{})};
+    process.exit(deps[process.argv[2]] ? 0 : 1);
+  " "$WORKSPACE_CLIENT/package.json" "$dep"
+}
+
+verify_one() {
+  local label="$1"
+  shift
+  if "$@" >/dev/null 2>&1; then
+    echo "  ✓ $label OK"
+    return 0
+  fi
+
+  echo "  ✗ $label FAIL"
+  return 1
+}
+
+# Step 4: Verify native binaries when present in this project
+echo "→ Verifying native binaries..."
+FAIL=0
+
+if has_dep esbuild; then
+  verify_one "esbuild" node -e "require('esbuild').transform('const x: number = 1',{loader:'ts'}).catch(()=>process.exit(1))" || FAIL=1
+fi
+
+if has_dep rollup; then
+  verify_one "rollup" node -e "import('rollup').catch(()=>process.exit(1))" || FAIL=1
+fi
+
+if has_dep lightningcss; then
+  verify_one "lightningcss" node -e "try{require('lightningcss')}catch(_){process.exit(1)}" || FAIL=1
+fi
+
+if has_dep vite; then
+  verify_one "vite" node -e "import('vite').catch(()=>process.exit(1))" || FAIL=1
+fi
+
+if [ "$FAIL" -ne 0 ]; then
+  echo "✗ Binary verification failed. Try running the script again (crashes can be intermittent)."
+  exit 1
+fi
+
+# Step 5: Optionally install Playwright
+if [[ "$INSTALL_PLAYWRIGHT" == "true" ]]; then
+  echo "→ Installing Playwright browsers..."
+  if [[ "${EUID:-$(id -u)}" -eq 0 ]]; then
+    npx playwright install --with-deps chromium
+  elif command -v sudo &>/dev/null && sudo -n true 2>/dev/null; then
+    # Non-root but passwordless sudo available — install browsers then system deps
+    npx playwright install chromium
+    sudo npx playwright install-deps chromium
+  else
+    npx playwright install chromium
+    echo "⚠ System dependencies not installed (no root/sudo access)."
+    echo "  Playwright tests may fail. Run: sudo npx playwright install-deps chromium"
+  fi
+fi
+
+echo ""
+echo "=== ✓ Sandbox npm install complete ==="
+echo "Run 'npm run dev' to start the dev server."

package/skills/scaffolding-oracle-to-postgres-migration-test-project/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: scaffolding-oracle-to-postgres-migration-test-project
+description: 'Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use when setting up test infrastructure before writing migration integration tests, or when a test project is needed for Oracle-to-PostgreSQL validation.'
+---
+
+# Scaffolding an Integration Test Project for Oracle-to-PostgreSQL Migration
+
+Creates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests.
+
+## Workflow
+
+```
+Progress:
+- [ ] Step 1: Inspect the target project
+- [ ] Step 2: Create the xUnit test project
+- [ ] Step 3: Implement transaction-rollback base class
+- [ ] Step 4: Implement seed data manager
+- [ ] Step 5: Verify the project compiles
+```
+
+**Step 1: Inspect the target project**
+
+Read the target project's `.csproj` to determine the .NET version and existing package references. Match these versions exactly — do not upgrade.
+
+**Step 2: Create the xUnit test project**
+
+- Target the same .NET version as the application under test.
+- Add NuGet packages for Oracle database connectivity and xUnit.
+- Add a project reference to the target project only — no other application projects.
+- Add an `appsettings.json` configured for Oracle database connectivity.
+
+**Step 3: Implement transaction-rollback base class**
+
+- Create a base test class that opens a transaction before each test and rolls it back after.
+- Catch and handle all exceptions to guarantee rollback.
+- Make the pattern inheritable by all downstream test classes.
+
+**Step 4: Implement seed data manager**
+
+- Create a global seed manager for loading test data within the transaction scope.
+- Do not commit seed data — transactions roll back after each test.
+- Do not use `TRUNCATE TABLE` — preserve existing database data.
+- Reuse existing seed files if available.
+- Establish a naming convention for seed file location that downstream test creation will follow.
+
+**Step 5: Verify the project compiles**
+
+Build the test project and confirm it compiles with zero errors before finishing.
+
+## Key Constraints
+
+- Oracle is the golden behavior source — scaffold for Oracle first.
+- Keep to existing .NET and C# versions; do not introduce newer language or runtime features.
+- Output is an empty test project with infrastructure only — no test cases.

package/skills/scaffolding-oracle-to-postgres-migration-test-project/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/scaffolding-oracle-to-postgres-migration-test-project`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/scoutqa-test/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/scoutqa-test/SKILL.md

@@ -0,0 +1,375 @@
+---
+name: scoutqa-test
+description: 'This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibility audits, e-commerce flows, and user flow validation using ScoutQA CLI. Use this skill proactively after implementing web application features to verify they work correctly.'
+---
+
+# ScoutQA Testing Skill
+
+Perform AI-powered exploratory testing on web applications using the `scoutqa` CLI.
+
+**Think of ScoutQA as an intelligent testing partner** that can autonomously explore, discover issues, and verify features. Delegate testing to multiple parallel ScoutQA executions to maximize coverage while saving time.
+
+## When to Use This Skill
+
+Use this skill in two scenarios:
+
+1. **User requests testing** - When the user explicitly asks to test a website or verify functionality
+2. **Proactive verification** - After implementing web features, automatically run tests to verify the implementation works correctly
+
+**Example proactive usage:**
+
+- After implementing a login form → Test the authentication flow
+- After adding form validation → Verify validation rules and error handling
+- After building a checkout flow → Test the end-to-end purchase process
+- After fixing a bug → Verify the fix works and didn't break other features
+
+**Best practice**: When you finish implementing a web feature, proactively start a ScoutQA test in the background to verify it works while you continue with other tasks.
+
+## Running Tests
+
+### Testing Workflow
+
+Copy this checklist and track your progress:
+
+Testing Progress:
+
+- [ ] Write specific test prompt with clear expectations
+- [ ] Run scoutqa command in background
+- [ ] Inform user of execution ID and browser URL
+- [ ] Extract and analyze results
+
+**Step 1: Write specific test prompt**
+
+See "Writing Effective Prompts" section below for guidelines.
+
+**Step 2: Run scoutqa command**
+
+**IMPORTANT**: Use the Bash tool's timeout parameter (5000ms = 5 seconds) to capture execution details:
+
+When calling the Bash tool, set `timeout: 5000` as a parameter:
+
+- This is the Bash tool's built-in timeout parameter in Claude Code (NOT the Unix `timeout` command)
+- After 5 seconds, the Bash tool returns control with a task ID and the process continues running in the background
+- This is different from Unix `timeout` which kills the process - here the process keeps running
+- The first 5 seconds capture the execution ID and browser URL from ScoutQA's output
+- The test continues running remotely on ScoutQA's infrastructure with the background task
+
+```bash
+scoutqa --url "https://example.com" --prompt "Your test instructions"
+```
+
+In the first few seconds, the command will output:
+
+- **Execution ID** (e.g., `019b831d-xxx`)
+- **Browser URL** (e.g., `https://app.scoutqa.ai/t/019b831d-xxx`)
+- Initial tool calls showing test progress
+
+After the 5-second timeout, the Bash tool returns a task ID and the command continues running in the background. You can work on other tasks while the test runs. The timeout is only to capture the initial output (execution ID and browser URL) - the test keeps running both locally as a background task and remotely on ScoutQA's infrastructure.
+
+**Step 3: Inform user of execution ID and browser URL**
+
+After the Bash tool returns with the task ID (having captured the execution details in the first 5 seconds), inform the user of:
+
+- The ScoutQA execution ID and browser URL so they can monitor progress in their browser
+- The background task ID if they want to check local command output later
+
+The test continues running in the background while you continue other work.
+
+**Step 4: Extract and analyze results**
+
+See "Presenting Results" section below for the complete format.
+
+### Command Options
+
+- `--url` (required): Website URL to test (supports `localhost` / `127.0.0.1`)
+- `--prompt` (required): Natural language testing instructions
+- `--project-id` (optional): Associate with a project for tracking
+- `-v, --verbose` (optional): Show all tool calls including internal ones
+
+### Local Testing Support
+
+ScoutQA supports testing `localhost` and `127.0.0.1` URLs autonomously — no manual setup required.
+
+```bash
+# Seamlessly test a locally running app when you're developing your app
+scoutqa --url "http://localhost:3000" --prompt "Test the registration form"
+```
+
+### When to Use Each Command
+
+**Starting a new test?** → Use `scoutqa --url --prompt`
+**Verifying a known issue?** → Use `scoutqa issue-verify --issue-id <id>`
+**Finding issue IDs from an execution?** → Use `scoutqa list-issues --execution-id <id>`
+**Agent needs more context?** → Use `scoutqa send-message` (see "Following Up on Stuck Executions")
+
+## Writing Effective Prompts
+
+Focus on **what to explore and verify**, not prescriptive steps. ScoutQA autonomously determines how to test.
+
+**Example: User registration flow**
+
+```bash
+scoutqa --url "https://example.com" --prompt "
+Explore the user registration flow. Test form validation edge cases,
+verify error handling, and check accessibility compliance.
+"
+```
+
+**Example: E-commerce checkout**
+
+```bash
+scoutqa --url "https://shop.example.com" --prompt "
+Test the checkout flow. Verify pricing calculations, cart persistence,
+payment options, and mobile responsiveness.
+"
+```
+
+**Example: Running parallel tests for comprehensive coverage**
+
+Launch multiple tests in parallel by making multiple Bash tool calls in a single message, each with the Bash tool's `timeout` parameter set to `5000` (milliseconds):
+
+```bash
+# Test 1: Authentication & security
+scoutqa --url "https://app.example.com" --prompt "
+Explore authentication: login/logout, session handling, password reset,
+and security edge cases.
+"
+
+# Test 2: Core features (runs in parallel)
+scoutqa --url "https://app.example.com" --prompt "
+Test dashboard and main user workflows. Verify data loading,
+CRUD operations, and search functionality.
+"
+
+# Test 3: Accessibility (runs in parallel)
+scoutqa --url "https://app.example.com" --prompt "
+Conduct accessibility audit: WCAG compliance, keyboard navigation,
+screen reader support, color contrast.
+"
+```
+
+**Implementation**: Send a single message with three Bash tool calls. For each Bash tool invocation, set the `timeout` parameter to `5000` milliseconds. After 5 seconds, each Bash call returns with a task ID while the processes continue running in the background. This captures the execution ID and browser URL from each test in the initial output, then all three continue running in parallel (both as background tasks locally and remotely on ScoutQA's infrastructure).
+
+**Key guidelines:**
+
+- Describe **what to test**, not **how to test** (ScoutQA figures out the steps)
+- Focus on goals, edge cases, and concerns
+- Run multiple parallel executions for different test areas
+- Trust ScoutQA to autonomously explore and discover issues
+- Always set the Bash tool's `timeout` parameter to `5000` milliseconds when calling scoutqa commands (this returns control after 5 seconds while the process continues in the background)
+- For parallel tests, make multiple Bash tool calls in a single message
+- Remember: Bash tool timeout ≠ Unix timeout command (Bash timeout continues the process in background, Unix timeout kills it)
+
+### Common Test Scenarios
+
+**Post-deployment smoke test:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Smoke test: verify critical functionality works after deployment.
+Check homepage, navigation, login/logout, and key user flows.
+"
+```
+
+**Accessibility audit:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Audit accessibility: WCAG 2.1 AA compliance, keyboard navigation,
+screen reader support, color contrast, and semantic HTML.
+"
+```
+
+**E-commerce testing:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Explore e-commerce functionality: product search/filtering,
+cart operations, checkout flow, and pricing calculations.
+"
+```
+
+**SaaS application:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Test SaaS app: authentication, dashboard, CRUD operations,
+permissions, and data integrity.
+"
+```
+
+**Form validation:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Test form validation: edge cases, error handling, required fields,
+format validation, and successful submission.
+"
+```
+
+**Mobile responsiveness:**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Check mobile experience: responsive layout, navigation,
+touch interactions, and viewport behavior.
+"
+```
+
+**Verification of a known issue:**
+
+```bash
+# First, find issue IDs from a previous execution
+scoutqa list-issues --execution-id <executionId>
+
+# Then verify the issue (creates a new verification execution automatically)
+scoutqa issue-verify --issue-id <issueId>
+```
+
+The `issue-verify` command will:
+
+1. Create a verification execution for the issue
+2. Show the execution ID and browser URL
+3. Stream the agent's verification progress in real-time
+4. Display a completion summary with a link to results
+
+**Feature verification (after implementation):**
+
+```bash
+scoutqa --url "$URL" --prompt "
+Verify the new [feature name] works correctly. Test core functionality,
+edge cases, error handling, and integration with existing features.
+"
+```
+
+**Example: Proactive testing after coding a feature**
+
+After implementing a user registration form, automatically verify it works:
+
+```bash
+scoutqa --url "http://localhost:3000/register" --prompt "
+Test the newly implemented registration form. Verify:
+- Form validation (email format, password strength, required fields)
+- Error messages display correctly
+- Successful registration flow
+- Edge cases (duplicate emails, special characters, etc.)
+"
+```
+
+This catches issues immediately while the implementation is fresh in context.
+
+## Listing Issues
+
+Use `scoutqa list-issues` to browse issues found in a previous execution. This is useful for finding issue IDs to use with `issue-verify`.
+
+```bash
+scoutqa list-issues --execution-id <executionId>
+```
+
+**Options:**
+
+- `--execution-id` (required): Execution ID (from the `/t/<executionId>` URL or CLI output)
+
+**Example output:**
+
+```
+Showing 3 issues:
+
+🔴 019c-abc1
+   Login button unresponsive on mobile
+   Severity: critical | Category: usability | Status: open
+
+🟠 019c-abc2
+   Missing form validation on email field
+   Severity: high | Category: functional | Status: open
+
+🟡 019c-abc3
+   Color contrast insufficient on footer links
+   Severity: medium | Category: accessibility | Status: resolved
+```
+
+## Presenting Results
+
+### Immediate Presentation (After Starting Test)
+
+Right after running the scoutqa command, present the execution details to the user:
+
+```markdown
+**ScoutQA Test Started**
+
+Execution ID: `019b831d-xxx`
+View Live: https://app.scoutqa.ai/t/019b831d-xxx
+
+The test is running remotely. You can view real-time progress in your browser at the link above while I continue with other tasks.
+```
+
+### Final Results (After Completion)
+
+When the execution completes, use this format to present findings:
+
+```markdown
+**ScoutQA Test Results**
+
+Execution ID: `ex_abc123`
+
+**Issues Found:**
+
+[High] Accessibility: Missing alt text on logo image
+
+- Impact: Screen readers cannot describe the logo
+- Location: Header navigation
+
+[Medium] Usability: Submit button not visible on mobile viewport
+
+- Impact: Users cannot complete form on mobile devices
+- Location: Contact form, bottom of page
+
+[Low] Functional: Search returns no results for valid queries
+
+- Impact: Search feature appears broken
+- Location: Main search bar
+
+**Summary:** Found 3 issues across accessibility, usability, and functional categories. See full interactive report with screenshots at the URL above.
+```
+
+Always include:
+
+- **Execution ID** (e.g., `ex_abc123`) for reference
+- **Issues found** with severity, category (accessibility, usability, functional), impact, and location
+
+## Following Up on Stuck Executions
+
+If the remote agent gets stuck or needs clarification, use `send-message` to continue:
+
+```bash
+# Example: Agent is stuck at login, user provides credentials
+scoutqa send-message --execution-id ex_abc123 --prompt "
+Use these test credentials: username: testuser@example.com, password: TestPass123
+"
+
+# Example: Agent asks which flow to test next
+scoutqa send-message --execution-id ex_abc123 --prompt "
+Focus on the checkout flow next, skip the wishlist feature
+"
+```
+
+## Checking Test Results
+
+ScoutQA tests run remotely on ScoutQA's infrastructure. After starting a test with a short timeout to capture the execution ID:
+
+1. The test continues running remotely (not locally in background)
+2. You can continue other work immediately
+3. To check results later, visit the browser URL provided when the test started
+4. Alternatively, use `scoutqa get-execution --execution-id <id>` to fetch results via CLI
+
+**Best practice**: Start tests by setting the Bash tool's `timeout` parameter to `5000` milliseconds. After 5 seconds, the Bash tool returns control with a task ID and the execution details (execution ID and browser URL) while the test continues running in the background. You can then continue other work and check results on ScoutQA's website or via CLI when needed.
+
+## Troubleshooting
+
+| Issue                          | Solution                                                    |
+| ------------------------------ | ----------------------------------------------------------- |
+| `command not found: scoutqa`   | Install CLI: `npm i -g @scoutqa/cli@latest`                 |
+| Auth expired / unauthorized    | Run `scoutqa auth login`                                    |
+| Test hangs or needs input      | Use `scoutqa send-message --execution-id`                   |
+| Check test results             | Visit browser URL or `scoutqa get-execution --execution-id` |
+| Need issue ID for verification | Run `scoutqa list-issues --execution-id <id>`               |

package/skills/scoutqa-test/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/scoutqa-test`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24