Agent skill

Eng QA Bootstrap

by compozy in compozy/compozy

Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA.

MITAuto-check passedTesting & QA

Install Eng QA Bootstrap

skills CLI
$ npx skills add compozy/compozy --skill eng-qa-bootstrap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compozy/compozy eng-qa-bootstrap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/eng/eng-qa-bootstrap .claude/skills/eng-qa-bootstrap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eng-qa-bootstrap
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
629 words
Files
6 (incl. scripts, references)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA.

  • Works in 4 steps: Resolve the scenario slug and, for… → For a new pass, run the bootstrap helper… → Reuse only when continuing the same… → …
  • Local QA needs daemon
  • SKILL.md covers Required Inputs, Procedure and Error Handling
  • Runs Python scripts from its folder; calls python3 and make

What it does

Eng QA Bootstrap is an agent skill from compozy/compozy. Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Use when local QA needs daemon, workspace, provider, or playbook setup. Do not use for unit tests, planning-only work, or browser-only checks.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/bootstrap-contract.md`, `scripts/bootstrap-qa-env-smoke-test.py` and `scripts/bootstrap-qa-env.py`).

It sits in Testing & QA, covering Unit testing. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.

When your agent uses it

  • Local QA needs daemon
  • Planning-only work
  • Browser-only checks

Example prompts

  • “Use the eng-qa-bootstrap skill to bootstrap isolated Compozy QA labs and emits the canonical manifest for downstream QA”
  • “/eng-qa-bootstrap”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the scenario slug and, for eng-real-scenario-qa, validate the playbook under .agents/skills/eng/eng-real-scenario-qa/references/pla…
  2. For a new pass, run the bootstrap helper (bootstrap, mutating)
  3. Reuse only when continuing the same active QA session or loop with its exact manifest
  4. Record the emitted BOOTSTRAP_MANIFEST; do not reconstruct environment values manually.

What it can do on your machine

Read from SKILL.md and the folder at commit eec2ed1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eng QA Bootstrap loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 629 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from compozy/compozy at commit eec2ed1, republished under its MIT licence (© compozy). 629 words, ~1,325 tokens.

Download SKILL.mdSave it as .claude/skills/eng-qa-bootstrap/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
eng-qa-bootstrap
description
Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Use when local QA needs daemon, workspace, provider, or playbook setup. Do not use for unit tests, planning-only work, or browser-only checks.
trigger
explicit
argument-hint
[scenario-slug] [--playbook <ref> | --profile targeted --required-surface <surface>]

Compozy QA Bootstrap

Provision infrastructure and scratch evidence for one QA pass. Bootstrap does not prove runtime behavior; downstream QA owns journeys and verdicts.

Required Inputs

  • scenario-slug (optional): short lab context; defaults to release-candidate.
  • --playbook <ref>: required when called by eng-real-scenario-qa; omitted for generic qa-execution infrastructure.
  • --profile targeted --required-surface <surface>: use for a bounded non-agent journey; repeat the surface flag for every CLI/API/Web/runtime/provider plane in scope.

Procedure

Step 1: Create or Resume One Lab

  1. Resolve the scenario slug and, for eng-real-scenario-qa, validate the playbook under .agents/skills/eng/eng-real-scenario-qa/references/playbooks/.
  2. For a new pass, run the bootstrap helper (bootstrap, mutating): python3 .agents/skills/eng/eng-qa-bootstrap/scripts/bootstrap-qa-env.py --scenario "<scenario-slug>" --repo-root . [--playbook "<ref>" | --profile targeted --required-surface "<surface>"]
  3. Reuse only when continuing the same active QA session or loop with its exact manifest: python3 .agents/skills/eng/eng-qa-bootstrap/scripts/bootstrap-qa-env.py --scenario "<scenario-slug>" --repo-root . [--playbook "<ref>"] --reuse-manifest "<manifest-path>"
  4. Record the emitted BOOTSTRAP_MANIFEST; do not reconstruct environment values manually.

Done when: one fresh or same-session lab has one readable manifest and no unrelated lab was reused.

Step 2: Verify the Handoff Contract

  1. Read .agents/skills/eng/eng-qa-bootstrap/references/bootstrap-contract.md in full.
  2. Check that the emitted manifest, required paths, launch policy, and teardown command match the selected profile. Use helper diagnostics and the strict auditor for machine-checkable fields; do not manually repeat each schema check.
  3. When a playbook was supplied, also validate the materialized playbook, agents, open-task tree, knowledge files, required deliverables/collaboration, and populated charter.
  4. Treat scaffolding as empty evidence until downstream QA records real actions and the strict auditor passes.

Done when: manifest, env, paths, scenario contract, charter, playbook artifacts, and filesystem all describe the same isolated lab with no placeholders in a playbook run.

Step 3: Hand Off to Downstream QA

  1. Pass qa-docs-path=docs/qa to qa-report and qa-execution; keep QA_OUTPUT_PATH as lab-side scratch evidence only.
  2. Launch providers, Web, browser, and config operations exactly from the manifest contract. Preserve operator home for native_cli + home_policy=operator; use isolated provider homes for bound-secret or brokered lanes.
  3. Export the manifest-derived COMPOZY_WEB_API_PROXY_TARGET for Web QA and serialize config writes against one isolated home.
  4. Register every long-lived process immediately under <QA_OUTPUT_PATH>/qa/pids/.
  5. Require downstream QA to run the manifest's strict AUDIT_COMMAND before a behavior-first verdict.

Done when: downstream skills consume the canonical manifest, durable findings land under docs/qa/, scratch evidence stays in the lab, and every owned process is registered.

Show full SKILL.md (247 more words)Show less

Step 4: Preserve Continuation State

  1. Report the manifest path, lab root, COMPOZY_HOME, base URL, dated run-report path, and reuse status.
  2. For a continuing loop, append the exact machine-readable continuation block from the bootstrap contract. Hand off with the lab alive; Step 5 runs when downstream QA reaches a terminal outcome, not before its first action.

Done when: the next continuation can identify the same lab from one exact manifest without discovery or guessing.

Step 5: Tear Down on Every Terminal Path

  1. On PASS, FAIL, BLOCKED, or abort, run the manifest's exact TEARDOWN_COMMAND; only a confirmed continuation of the same loop may defer it.
  2. The teardown must stop the daemon, tmux server, registered PIDs, lab-root processes, and lab-port listeners without touching unrelated labs.
  3. Cite <QA_OUTPUT_PATH>/qa/teardown.json with "clean": true. Survivors are a blocking failure.
  4. Reserve make qa-reap for intentional stale-lab recovery across the machine, not normal cleanup of one active run.

Done when: the current lab's teardown evidence is clean and no process owned by this pass remains alive.

Error Handling

  • Requested reuse fails health checks: use the fresh manifest emitted by the helper; do not revive stale state manually.
  • Provider reports global config errors: compare the command's home policy with the manifest; isolated and operator-home lanes intentionally differ.
  • Web reaches the wrong daemon: restart the Web process with the manifest-derived proxy target.
  • Teardown reports survivors: inspect each TEARDOWN_SURVIVOR, stop only processes owned by the current lab, and rerun the same targeted teardown.

© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in .agents/skills/eng/eng-qa-bootstrap of compozy/compozy.

  • SKILL.md
  • references/bootstrap-contract.md
  • scripts/bootstrap-qa-env-smoke-test.py
  • scripts/bootstrap-qa-env.py
  • scripts/qa_skill_paths.py
  • scripts/teardown-qa-env.py

Open the folder on GitHubat commit eec2ed1

Compare with similar skills

Eng QA Bootstrap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eng QA Bootstrap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eng QA Bootstrap this skillcompozy/compozy2.8k—~1.3kAutomated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
Testing OpenLogi UIAprilNEA/OpenLogi23k—~1.1kAutomated safety check: PassApache-2.0
Go Testingcxuu/golang-skills1701 repos~1.3kAutomated safety check: PassApache-2.0
Contractssamchon/nestia2.2k—~1.3kAutomated safety check: PassMIT
Cohesion Over TestabilityEpicenterHQ/epicenter4.8k—~2kAutomated safety check: PassCustom licence

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Go Testing

    cxuu/golang-skills

    A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.

    170 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed
  • Contracts

    samchon/nestia

    Defines self-acknowledgments for production declarations and tests.

    2.2k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Cohesion Over Testability

    EpicenterHQ/epicenter

    Collapse test-shaped production boundaries while preserving behavior and coverage.

    4.8k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 16 days ago
    Testing & QAAuto-check passed

More from compozy/compozy

All 47 skills in this repo
  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed
  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed
  • Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed
  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Categories

Questions about Eng QA Bootstrap

What does Eng QA Bootstrap do?

Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Eng QA Bootstrap is an agent skill from compozy/compozy. Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA.

When should I use Eng QA Bootstrap?

Eng QA Bootstrap fits situations like: local QA needs daemon; planning-only work; browser-only checks.

How do I install Eng QA Bootstrap in Claude Code?

Run `npx skills add compozy/compozy --skill eng-qa-bootstrap -a claude-code`. Or copy the skill folder (.agents/skills/eng/eng-qa-bootstrap in compozy/compozy) into .claude/skills/eng-qa-bootstrap in your project. Claude Code loads it when a task matches its description.

How do I install Eng QA Bootstrap in Codex?

Run `npx skills add compozy/compozy --skill eng-qa-bootstrap -a codex`. Or copy the skill folder (.agents/skills/eng/eng-qa-bootstrap in compozy/compozy) into .agents/skills/eng-qa-bootstrap in your project. Codex loads it when a task matches its description.

Can I use Eng QA Bootstrap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill eng-qa-bootstrap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eng-qa-bootstrap, .gemini/skills/eng-qa-bootstrap, .github/skills/eng-qa-bootstrap and .opencode/skills/eng-qa-bootstrap in your project.

What does Eng QA Bootstrap need to run?

Going by SKILL.md and its folder, Eng QA Bootstrap needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and make). Our summary lists: Python 3.

Does Eng QA Bootstrap access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Eng QA Bootstrap safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Eng QA Bootstrap use?

Eng QA Bootstrap is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eng QA Bootstrap use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Eng QA Bootstrap?

Skills that share tags, products or a category with Eng QA Bootstrap: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 170 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eng QA Bootstrap?

compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,792 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.

Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.