Agent skill

Testing Orcaq

OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.

MITAuto-check passedTesting & QA

Install Testing Orcaq

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a claude-code

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

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq --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/cin12211/orca-q.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/testing-orcaq .claude/skills/testing-orcaq && 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/

Paste into Claude Code

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .claude/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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

$skill-installer install https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq

Type 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.

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/testing-orcaq .agents/skills/testing-orcaq && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .agents/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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.

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/testing-orcaq .cursor/skills/testing-orcaq && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .cursor/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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

$ gemini skills install https://github.com/cin12211/orca-q.git --path .claude/skills/testing-orcaq

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/testing-orcaq .gemini/skills/testing-orcaq && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .gemini/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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.

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq

Installs 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).

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/testing-orcaq .github/skills/testing-orcaq && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .github/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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.

skills CLI

$ npx skills add cin12211/orca-q --skill testing-orcaq -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cin12211/orca-q testing-orcaq --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/testing-orcaq .opencode/skills/testing-orcaq && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "testing-orcaq" agent skill from https://github.com/cin12211/orca-q/tree/main/.claude/skills/testing-orcaq into .opencode/skills/testing-orcaq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-orcaq", 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: testing-orcaq
GitHub stars: 224
Token cost: ~1.6k tokens
SKILL.md length: 353 words
Files: 1
Skills in repo: 16
Repo updated: Sep 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.

Works in 8 steps: Decision Tree — Which Command? → npm Script Reference → Vitest Projects → …
Write tests for OrcaQ
SKILL.md covers 1. Decision Tree — Which…, 2. npm Script Reference, 3. Vitest Projects and 4. Playwright Projects &…, plus 4 more sections
Calls bun and bash

What it does

Testing Orcaq is an agent skill from cin12211/orca-q. OrcaQ-specific testing guide. Use when asked to run, debug, or write tests for OrcaQ. Covers all bun test: scripts, fixture profiles, Vitest projects (unit / nuxt / integration), and Playwright DB projects. Load BEFORE suggesting any test command so the agent uses the correct script and profile.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing, Browser testing and Test generation. It works with Playwright, Vitest, Nuxt and Docker. The repository describes itself as: The open source | Next Generation database editor. The licence is MIT.

When your agent uses it

Write tests for OrcaQ
Tasks that involve Unit testing
Tasks that involve Browser testing

Example prompts

“/testing-orcaq”

Requirements

Docker

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Decision Tree — Which Command?
npm Script Reference
Vitest Projects
Playwright Projects & Fixture Profiles
Fixture Profile Reference
Key Env Vars
Fast Iteration Pattern
Rules the Agent Must Follow

What it can do on your machine

Read from SKILL.md and the folder at commit 3142fe6. 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
Shell commands in SKILL.md call:
- bun
- bash
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

Testing Orcaq loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 353 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~78
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

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

The full file from cin12211/orca-q at commit 3142fe6, republished under its MIT licence (© cin12211). 353 words, ~1,567 tokens.

Download SKILL.mdSave it as .claude/skills/testing-orcaq/SKILL.md (or your agent's skills folder).

name: testing-orcaq
description: OrcaQ-specific testing guide. Use when asked to run, debug, or write tests for OrcaQ. Covers all bun test:* scripts, fixture profiles, Vitest projects (unit / nuxt / integration), and Playwright DB projects. Load BEFORE suggesting any test command so the agent uses the correct script and profile.
tools: Read, Edit, Bash, Grep, Glob
category: testing
color: blue
displayName: OrcaQ Testing
applyTo: test/**,scripts/test-services/**,.github/workflows/**

OrcaQ Testing — Agent Skill

Read docs/TESTING_GUIDE.md for the full reference. This skill encodes the decision rules so you choose the right command without checking every time.

1. Decision Tree — Which Command?

Is the test purely logic / no DB / no browser?
  └─ YES → bun test:unit
  └─ NO →
      Is it a Vue component test (nuxt env)?
        └─ YES → bun test:nuxt
        └─ NO →
            Is it an API / server integration test?
              └─ YES →
                  Are fixtures already running?
                    └─ YES → bun test:api:raw
                    └─ NO  → bun test:api          ← auto-provisions + cleans up
              └─ NO →
                  It is a Playwright E2E test.
                  Do you need a specific DB only?
                    └─ YES → bash scripts/test-services/run-tests.sh --fixtures=<profile> -- playwright test --project <db>
                    └─ NO  → bun test:e2e          ← all fixtures, all projects

2. npm Script Reference

Script	What it does	Needs Docker?
`bun test:all`	All Vitest suites (unit + nuxt + integration)	No
`bun test:unit`	Unit tests only (`test/unit/`)	No
`bun test:nuxt`	Nuxt component tests (`test/nuxt/`)	No
`bun test:api`	Integration tests — auto starts all fixtures	Yes
`bun test:api:raw`	Integration tests — fixtures must already be up	Yes
`bun test:e2e`	Playwright — auto starts all fixtures	Yes
`bun test:e2e:raw`	Playwright — fixtures must already be up	Yes
`bun test:coverage`	Full coverage report	No
`bun test:watch`	Watch mode (development)	No
`bun test:fixtures:up`	Start all Docker fixtures	Yes
`bun test:fixtures:down`	Stop and remove all Docker fixtures	Yes

3. Vitest Projects

Project flag	Files	Notes
`--project unit`	`test/unit/*/.{test,spec}.ts`	Pure logic, no framework
`--project nuxt`	`test/nuxt/*/.{test,spec}.ts`	Vue component tests
`--project integration`	`test/api/*/.{test,spec}.ts`	Requires all DB fixtures

Run one file:

bash

bun vitest --run test/unit/core/helpers/myHelper.spec.ts

4. Playwright Projects & Fixture Profiles

Playwright project	Fixture profile to use
`common`	`all`
`postgres`	`postgres`
`mysql`	`mysql`
`mariadb`	`mariadb`
`redis`	`redis`
`sqlite`	`sqlite`
`oracle`	manual (no Docker compose profile)

Run isolated by DB:

bash

bash scripts/test-services/run-tests.sh --fixtures=postgres -- playwright test --project postgres
bash scripts/test-services/run-tests.sh --fixtures=redis   -- playwright test --project redis
bash scripts/test-services/run-tests.sh --fixtures=sqlite  -- playwright test --project sqlite

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

5. Fixture Profile Reference

Profile	Containers started
`postgres`	PostgreSQL 16 only
`mysql`	MySQL 8.4 only
`mariadb`	MariaDB 11.4 only
`sql`	PostgreSQL + MySQL + MariaDB
`redis`	Redis 7.4 only
`mongodb`	MongoDB 7 only
`sqlite`	File prep only (no Docker)
`all`	All of the above
`none`	Nothing

Manual fixture control:

bash

bash scripts/test-services/start-fixtures.sh --profile <profile>
bash scripts/test-services/stop-fixtures.sh  --profile <profile>

6. Key Env Vars

All use ORCAQ_ prefix. Defaults are set by start-fixtures.sh automatically.

ORCAQ_POSTGRES_PORT=5432      ORCAQ_POSTGRES_DATABASE=pagila
ORCAQ_MYSQL_PORT=3306         ORCAQ_MYSQL_DATABASE=sakila
ORCAQ_MARIADB_PORT=3307       ORCAQ_MARIADB_DATABASE=sakila
ORCAQ_REDIS_PORT=6379
ORCAQ_KEEP_FIXTURES=1         # keep containers alive after run
ORCAQ_FIXTURE_PROFILE=all     # override profile via env

7. Fast Iteration Pattern

When iterating on integration or E2E tests, start fixtures once and reuse:

bash

bun test:fixtures:up           # 1× — start all containers
bun test:api:raw               # run repeatedly
# or
bun test:e2e:raw               # run repeatedly
bun test:fixtures:down         # done

8. Rules the Agent Must Follow

Never run test:api or test:e2e when fixtures are already up — use the :raw variant to avoid double-provisioning.
Never start all fixtures to test a single DB — use the matching profile.
Always run bun test:unit after any source change to verify no regression before running heavier suites.
Do not run bun test:all for a change scoped to one DB — pick the narrowest relevant suite.
Use ORCAQ_KEEP_FIXTURES=1 when debugging flaky tests so containers survive after failure.

Files

Just SKILL.md in .claude/skills/testing-orcaq of cin12211/orca-q.

Open the folder on GitHubat commit 3142fe6

Compare with similar skills

Testing Orcaq 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.

Testing Orcaq compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Testing Orcaq this skillcin12211/orca-q	224	—	~1.6k	Automated safety check: Pass	MIT	17 days ago
Test CommanderEliasOulkadi/shokunin	114	—	~3k	Automated safety check: Notes	MIT	3 days ago
Qe Test Executionproffesor-for-testing/agentic-qe	494	—	~1.2k	Automated safety check: Pass	MIT	4 days ago
Test GenerationEmeaAppGbb/spec2cloud	100	—	~5.5k	Automated safety check: Pass	MIT	5 mo ago
Control UI E2Eopenclaw/openclaw	392k	—	~2.9k	Automated safety check: Pass	MIT	today
Ckeditor5 TestingTriliumNext/Trilium	38k	—	~3.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Test Commander
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
114 GitHub stars~3k tokensUpdated 3 days ago
Testing & QAAuto-check: notes
Qe Test Execution
proffesor-for-testing/agentic-qe
Orchestrates test suite execution with parallel sharding, intelligent retry, and real-time reporting across Jest, Vitest, and Playwright.
494 GitHub stars~1.2k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Test Generation
EmeaAppGbb/spec2cloud
Generate BDD test code from Gherkin scenarios. An agent skill from EmeaAppGbb/spec2cloud.
100 GitHub stars~5.5k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Control UI E2E
openclaw/openclaw
A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…
392k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check passed
Ckeditor5 Testing
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
38k GitHub stars~3.3k tokensUpdated today
Testing & QAAuto-check passed
Check Visual Changes
igrlk/storybook-addon-test-codegen
Check the visual impact of an edit mid-task with uiverify check — render just the components you're touching on the UI Verify fleet and diff them against the real CI baseline, without opening a PR…
154 GitHub starsUsed in 1 repo~1.4k tokens
Testing & QAAuto-check passed

Questions about Testing Orcaq

What does Testing Orcaq do?

OrcaQ-specific testing guide. An agent skill from cin12211/orca-q. Testing Orcaq is an agent skill from cin12211/orca-q. OrcaQ-specific testing guide.

When should I use Testing Orcaq?

Testing Orcaq fits situations like: write tests for OrcaQ; tasks that involve Unit testing; tasks that involve Browser testing.

How do I install Testing Orcaq in Claude Code?

Run `npx skills add cin12211/orca-q --skill testing-orcaq -a claude-code`. Or copy the skill folder (.claude/skills/testing-orcaq in cin12211/orca-q) into .claude/skills/testing-orcaq in your project. Claude Code loads it when a task matches its description.

How do I install Testing Orcaq in Codex?

Run `npx skills add cin12211/orca-q --skill testing-orcaq -a codex`. Or copy the skill folder (.claude/skills/testing-orcaq in cin12211/orca-q) into .agents/skills/testing-orcaq in your project. Codex loads it when a task matches its description.

Can I use Testing Orcaq 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 cin12211/orca-q --skill testing-orcaq -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-orcaq, .gemini/skills/testing-orcaq, .github/skills/testing-orcaq and .opencode/skills/testing-orcaq in your project.

What does Testing Orcaq need to run?

Going by SKILL.md and its folder, Testing Orcaq needs the command-line tools its instructions call (bun and bash). Our summary lists: Docker.

Does Testing Orcaq 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 Testing Orcaq 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 Testing Orcaq use?

Testing Orcaq 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 Testing Orcaq use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing Orcaq?

Skills that share tags, products or a category with Testing Orcaq: Test Commander (EliasOulkadi/shokunin, 114 stars), Qe Test Execution (proffesor-for-testing/agentic-qe, 494 stars), Test Generation (EmeaAppGbb/spec2cloud, 100 stars) and Control UI E2E (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Orcaq?

cin12211 (a GitHub user) maintains it in cin12211/orca-q, which has 224 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 21, 2026.

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

Install Testing Orcaq

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

OrcaQ Testing — Agent Skill

1. Decision Tree — Which Command?

2. npm Script Reference

3. Vitest Projects

4. Playwright Projects & Fixture Profiles

5. Fixture Profile Reference

6. Key Env Vars

7. Fast Iteration Pattern

8. Rules the Agent Must Follow

Files

Compare with similar skills

Similar skills

More from cin12211/orca-q

Related

Questions about Testing Orcaq