How do I install the Optimizetests skill?

Run npx skillmds@latest add blink-new/optimizetests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Optimizetests safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Optimizetests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Optimizetests free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Optimizetests?

blink-new (@blink-new) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Optimizetests by blink-new — Agent Skill

Name: Optimizetests
Author: blink-new

Optimizetests

Optimize OpenClaw test runtime end to end. Use when the user asks for /optimizetests, slow-test review, import optimization, deduping tests, moving misplaced core coverage to extensions, or reducing CI/test wall time without adding shards or dropping coverage.

blink-new 6ee5cde 2 files · 2.6 KB Updated Sep 17, 2026

File contents

Optimize Tests

Goal: real OpenClaw test/runtime speedups with coverage intact. Do not add shards, skip assertions, weaken gates, or tune runner flags as the main fix.

Runbook

Read docs/help/testing.md, docs/ci.md, and the scoped AGENTS.md files for any subtree you will edit.
Establish evidence before edits:
- Full ranking: pnpm test:perf:groups --full-suite --allow-failures --output .artifacts/test-perf/<name>.json
- Targeted file: timeout 240 /usr/bin/time -l pnpm test <file> --maxWorkers=1 --reporter=verbose
- Import suspicion: add OPENCLAW_VITEST_IMPORT_DURATIONS=1 OPENCLAW_VITEST_PRINT_IMPORT_BREAKDOWN=1
Attack highest-return hotspots first:
- broad barrels or importActual() in hot tests
- per-test vi.resetModules() plus fresh imports
- expensive gateway/server/client setup where reset/reuse proves same behavior
- core tests asserting extension-owned behavior
- duplicated fixture construction or contract assertions
Prefer production-quality fixes:
- narrow runtime seams over broad mocks
- pure helpers for static parsing/metadata
- injected deps over module resets
- extension-owned tests for bundled plugin/provider/channel behavior
After each change, rerun the same benchmark and the proving test lane. Record before/after wall time, Vitest duration, and max RSS when available.
Run pnpm check:changed; run broader gates (pnpm check, pnpm test, pnpm build) when touched surfaces require them.
Commit scoped changes with scripts/committer "<conventional message>" <paths...>. Push when requested. If CI is red, inspect with gh run list/view, fix, push, repeat until current CI is green or a blocker is proven unrelated.

Output

End with the pushed commit(s), before/after timings, gates run, current CI state, and any remaining tail lanes that need separate optimization.

---name: optimizetestsdescription: Optimize OpenClaw test runtime end to end. Use when the user asks for /optimizetests, slow-test review, import optimization, deduping tests, moving misplaced core coverage to extensions, or reducing CI/test wall time without adding shards or dropping coverage.---# Optimize TestsGoal: real OpenClaw test/runtime speedups with coverage intact. Do not add shards,skip assertions, weaken gates, or tune runner flags as the main fix.## Runbook1. Read `docs/help/testing.md`, `docs/ci.md`, and the scoped `AGENTS.md` files for any subtree you will edit.2. Establish evidence before edits: - Full ranking: `pnpm test:perf:groups --full-suite --allow-failures --output .artifacts/test-perf/<name>.json` - Targeted file: `timeout 240 /usr/bin/time -l pnpm test <file> --maxWorkers=1 --reporter=verbose` - Import suspicion: add `OPENCLAW_VITEST_IMPORT_DURATIONS=1 OPENCLAW_VITEST_PRINT_IMPORT_BREAKDOWN=1`3. Attack highest-return hotspots first: - broad barrels or `importActual()` in hot tests - per-test `vi.resetModules()` plus fresh imports - expensive gateway/server/client setup where reset/reuse proves same behavior - core tests asserting extension-owned behavior - duplicated fixture construction or contract assertions4. Prefer production-quality fixes: - narrow runtime seams over broad mocks - pure helpers for static parsing/metadata - injected deps over module resets - extension-owned tests for bundled plugin/provider/channel behavior5. After each change, rerun the same benchmark and the proving test lane. Record before/after wall time, Vitest duration, and max RSS when available.6. Run `pnpm check:changed`; run broader gates (`pnpm check`, `pnpm test`, `pnpm build`) when touched surfaces require them.7. Commit scoped changes with `scripts/committer "<conventional message>" <paths...>`. Push when requested. If CI is red, inspect with `gh run list/view`, fix, push, repeat until current CI is green or a blocker is proven unrelated.## OutputEnd with the pushed commit(s), before/after timings, gates run, current CI state,and any remaining tail lanes that need separate optimization.

Frequently asked questions