Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
A skill your agent uses when writing or modifying Vitest tests, .vitest setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior.
$ npx skills add alchemyplatform/aa-sdk --skill testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alchemyplatform/aa-sdk 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/alchemyplatform/aa-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing .claude/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/alchemyplatform/aa-sdk/tree/main/.agents/skills/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 alchemyplatform/aa-sdk --skill testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alchemyplatform/aa-sdk testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemyplatform/aa-sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/testing .agents/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 alchemyplatform/aa-sdk --skill testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alchemyplatform/aa-sdk testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemyplatform/aa-sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/testing .cursor/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/alchemyplatform/aa-sdk.git --path .agents/skills/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 alchemyplatform/aa-sdk --skill testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alchemyplatform/aa-sdk testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemyplatform/aa-sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/testing .gemini/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 alchemyplatform/aa-sdk 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 alchemyplatform/aa-sdk --skill testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alchemyplatform/aa-sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/testing .github/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 alchemyplatform/aa-sdk --skill 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 alchemyplatform/aa-sdk testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemyplatform/aa-sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/testing .opencode/skills/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 "testing" agent skill from https://github.com/alchemyplatform/aa-sdk/tree/main/.agents/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
testingA skill your agent uses when writing or modifying Vitest tests, .vitest setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior.
Testing is an agent skill from alchemyplatform/aa-sdk. Use when writing or modifying Vitest tests, .vitest setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior.
Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `rules/affected-tests.md`, `rules/anvil-and-rundler.md` and `rules/vitest-workspace.md`).
It sits in Testing & QA, covering Unit testing. It works with Vitest. The licence is MIT.
Read from SKILL.md and the folder at commit 2d60342. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Testing loads about 305 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 82 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.
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.
The full file from alchemyplatform/aa-sdk at commit 2d60342, republished under its MIT licence (© alchemyplatform). 82 words, ~305 tokens.
.claude/skills/testing/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.aa-sdk uses Vitest workspace projects with shared .vitest setup. CI runs
affected package tests and a separate typecheck-only Vitest pass.
| Rule | When to read |
|---|---|
| Vitest projects | Before changing tests or per-package Vitest config. |
| Anvil and Rundler | Before changing tests that depend on local chain fixtures. |
| Affected tests | Before choosing local verification for package changes. |
vitest.config.ts loads .vitest and packages/* through
test.projects..vitest/vitest.shared.ts sets ~test, global setup, timeouts, and thread pool.scripts/run-affected-tests.sh uses Turborepo dry-run output to select
Vitest projects.© alchemyplatform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files in .agents/skills/testing of alchemyplatform/aa-sdk.
Open the folder on GitHubat commit 2d60342
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 |
|---|---|---|---|---|---|---|
| Testing this skillalchemyplatform/aa-sdk | 321 | — | ~305 | Automated safety check: Pass | MIT | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Vitestsupabase/supabase | 111k | 12 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Test GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Control UI E2Eopenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Adding LLM MCP ToolsTriliumNext/Trilium | 38k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 |
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
supabase/supabase
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
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…
TriliumNext/Trilium
A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…
leonardomso/33-js-concepts
Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.
alchemyplatform/aa-sdk
A skill your agent uses when editing docs//.mdx, generated reference docs, TypeDoc comments, typedoc.json, docs/docs.yml, or documentation review instructions.
alchemyplatform/aa-sdk
A skill your agent uses when throwing, catching, wrapping, documenting, or testing runtime errors in aa-sdk packages.
alchemyplatform/aa-sdk
A skill your agent uses when changing package entry points, exports maps, public API barrels, import paths, or subpath exports in aa-sdk packages.
alchemyplatform/aa-sdk
A skill your agent uses when changing GitHub workflows, Lerna versioning, package publish, or post-merge docs hooks (revalidate + SDK indexer).
alchemyplatform/aa-sdk
A skill your agent uses when changing packages/smart-accounts, account implementations, modules, permissions, nonces, deferred actions, or account address helpers.
alchemyplatform/aa-sdk
A skill your agent uses when changing package management, workspace config, build scripts, generated outputs, Turborepo/Lerna config, or local validation in aa-sdk.
Works with
Categories
A skill your agent uses when writing or modifying Vitest tests, .vitest setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior. Testing is an agent skill from alchemyplatform/aa-sdk.vitest setup, Anvil/Foundry or Rundler fixtures, per-package test config, or CI affected-test behavior.
Testing fits situations like: modifying Vitest tests; rundler fixtures; per-package test config; CI affected-test behavior.
Run `npx skills add alchemyplatform/aa-sdk --skill testing -a claude-code`. Or copy the skill folder (.agents/skills/testing in alchemyplatform/aa-sdk) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add alchemyplatform/aa-sdk --skill testing -a codex`. Or copy the skill folder (.agents/skills/testing in alchemyplatform/aa-sdk) into .agents/skills/testing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alchemyplatform/aa-sdk --skill 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/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.
SKILL.md names no scripts, command-line tools or credentials: Testing is instructions for the agent only.
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.
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.
Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 305 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Testing: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Vitest (supabase/supabase, 111k stars), Test Guard (amElnagdy/guard-skills, 1.3k 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.
alchemyplatform (a GitHub organization) maintains it in alchemyplatform/aa-sdk, which has 321 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 5, 2026.
Source: alchemyplatform/aa-sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.