Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
Install Archestra Dev Testing
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .claude/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.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/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .claude/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .agents/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .agents/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .cursor/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .cursor/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/archestra-ai/archestra.git --path .agents/skills/archestra-dev-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .gemini/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .gemini/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install archestra-ai/archestra archestra-dev-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .github/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .github/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add archestra-ai/archestra --skill archestra-dev-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/archestra-dev-testing .opencode/skills/archestra-dev-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "archestra-dev-testing" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-testing into .opencode/skills/archestra-dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
archestra-dev-testing- GitHub stars
- 4.3k
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,650 words
- Files
- 2 (incl. references)
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
- Works in 6 steps: Name the bug it catches. Can't? Don't… → Could the type system, a schema, or the… → Pick the cheapest level that still… → …
- Test selection and quality across backend
- SKILL.md covers The one rule, Local checks and merge queue, Pick the level and The fluff test anti-pattern, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Archestra Dev Testing is an agent skill from archestra-ai/archestra. Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/backend-tests.md`).
It sits in Testing & QA, covering Unit testing and End-to-end testing. It works with Vitest. The repository describes itself as: Enterprise AI Platform with guardrails, MCP registry, gateway & orchestrator.
When your agent uses it
- Test selection and quality across backend
- Load its backend reference for Vitest projects
Example prompts
- “/archestra-dev-testing”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Name the bug it catches. Can't? Don't write it.
- Could the type system, a schema, or the compiler already catch it? Then skip
- Pick the cheapest level that still exercises the risky part — but don't mock
- Assert observable behaviour: responses, rendered output, persisted rows,
- E2E for happy paths or infrastructure contracts nothing cheaper can reach.
- If it can't be made to pass, don't commit it skipped.
What it can do on your machine
Read from SKILL.md and the folder at commit 0e0fe0e. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
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
Archestra Dev Testing loads about 3.2k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 1,650 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,650 words (~3,160 tokens).
“Run commands from platform/ unless specifically instructed otherwise.”
- name
- archestra-dev-testing
Files
SKILL.md and 1 other file (references) in .agents/skills/archestra-dev-testing of archestra-ai/archestra.
- SKILL.md
- references/backend-tests.md
Open the folder on GitHubat commit 0e0fe0e
Compare with similar skills
Archestra Dev Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Archestra Dev Testing this skillarchestra-ai/archestra | 4.3k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Designing TestsCloudAI-X/claude-workflow-v2 | 1.4k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.1k | Automated safety check: Pass | None | |
| Ha Frontend Testinghome-assistant/frontend | 5.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None |
Similar skills
Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Frontend Playwright E2E
ansible/ansible-ui
Write, run, and debug Playwright E2E / integration / live tests.
More from archestra-ai/archestra
All 22 skills in this repoMigrate To Archestra
archestra-ai/archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance.
Archestra Dev Backend
archestra-ai/archestra
A skill your agent uses when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
Archestra Dev E2E
archestra-ai/archestra
A skill your agent uses when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
Archestra Dev Frontend
archestra-ai/archestra
A skill your agent uses when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
Archestra Dev LLM Providers
archestra-ai/archestra
A skill your agent uses when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching…
Archestra Dev Migrations
archestra-ai/archestra
A skill your agent uses when changing Drizzle schemas, generating migrations, editing migration SQL, creating data-only migrations, diagnosing drizzle-kit check failures, or resolving…
Related
Works with
Categories
Questions about Archestra Dev Testing
What does Archestra Dev Testing do?
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance. Archestra Dev Testing is an agent skill from archestra-ai/archestra. Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
When should I use Archestra Dev Testing?
Archestra Dev Testing fits situations like: test selection and quality across backend; load its backend reference for Vitest projects.
How do I install Archestra Dev Testing in Claude Code?
Run `npx skills add archestra-ai/archestra --skill archestra-dev-testing -a claude-code`. Or copy the skill folder (.agents/skills/archestra-dev-testing in archestra-ai/archestra) into .claude/skills/archestra-dev-testing in your project. Claude Code loads it when a task matches its description.
How do I install Archestra Dev Testing in Codex?
Run `npx skills add archestra-ai/archestra --skill archestra-dev-testing -a codex`. Or copy the skill folder (.agents/skills/archestra-dev-testing in archestra-ai/archestra) into .agents/skills/archestra-dev-testing in your project. Codex loads it when a task matches its description.
Can I use Archestra Dev Testing 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 archestra-ai/archestra --skill archestra-dev-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/archestra-dev-testing, .gemini/skills/archestra-dev-testing, .github/skills/archestra-dev-testing and .opencode/skills/archestra-dev-testing in your project.
What does Archestra Dev Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Archestra Dev Testing is instructions for the agent only.
Does Archestra Dev Testing 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 Archestra Dev Testing 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. Review the folder before installing.
What licence does Archestra Dev Testing use?
Archestra Dev Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Archestra Dev Testing use?
About 3.2k tokens (SKILL.md is roughly 13k 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 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Archestra Dev Testing?
Skills that share tags, products or a category with Archestra Dev Testing: Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Svelte Testing (spences10/sveltest, 113 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars) and Ha Frontend Testing (home-assistant/frontend, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Archestra Dev Testing?
archestra-ai (a GitHub organization) maintains it in archestra-ai/archestra, which has 4,347 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 7, 2026.
Source: archestra-ai/archestra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.