New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Console Testing

by synnaxlabs in synnaxlabs/synnax

Rules for writing and editing unit tests in the Console (console/src//.spec.ts[x]).

Custom licenceAuto-check passedTesting & QA

Install Console Testing

skills CLI
$ npx skills add synnaxlabs/synnax --skill console-testing -a claude-code

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

GitHub CLI
$ gh skill install synnaxlabs/synnax console-testing --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/synnaxlabs/synnax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/console-testing .claude/skills/console-testing && 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
console-testing
GitHub stars
128
Token cost
~5.4k tokens
SKILL.md length
2,457 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Custom licence

At a glance

Rules for writing and editing unit tests in the Console (console/src//.spec.ts[x]).

  • Works in 4 steps: Real client + real flux stores against a… → Real store + real flux with a null… → vi.fn() injected through a prop or DI… → …
  • Reviewing a console Vitest spec
  • SKILL.md covers Rule 1: Test through the…, Rule 2: Prefer real…, Rule 3: Keep the environment… and Rule 4: Shared test…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Console Testing is an agent skill from synnaxlabs/synnax. Rules for writing and editing unit tests in the Console (console/src//.spec.ts[x]). Use whenever authoring, refactoring, or reviewing a console Vitest spec, building or reaching for a test wrapper/store/fixture, deciding whether to mock or use real infrastructure, or wiring shared test scaffolding. Enforces blackbox testing through the public namespace, real-over-mock with dependency injection, and a single home per helper.

Its SKILL.md is about 5.4k 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, Test generation and Design patterns. It works with Vitest. The repository describes itself as: The data and operations foundation for hardware.

When your agent uses it

  • Reviewing a console Vitest spec
  • Reaching for a test wrapper/store/fixture
  • Deciding whether to mock
  • Use real infrastructure

Example prompts

  • “Use the console-testing skill to rule for writing and editing unit tests in the Console (console/src//.spec.ts[x])”
  • “/console-testing”

Workflow steps

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

  1. Real client + real flux stores against a live cluster. This is the default reach
  2. Real store + real flux with a null client and preloaded state. For logic that
  3. vi.fn() injected through a prop or DI parameter. A spy handed to a component as
  4. A sanctioned environment seam (last resort, closed list). The only things that

What it can do on your machine

Read from SKILL.md and the folder at commit fdfe2bb. 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

Console Testing loads about 5.4k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 2,457 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~5.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); 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 2,457 words (~5,409 tokens).

“These rules govern every Vitest spec under console/src. They exist because a handful of failure modes keep recurring: importing internals instead of the public API, reaching for mocks when the real thing would do, stubbing browser primitives, and copy-pasting scaffolding…”

— opening of SKILL.md by synnaxlabs, Custom licence
name
console-testing

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/console-testing of synnaxlabs/synnax.

Open the folder on GitHubat commit fdfe2bb

Compare with similar skills

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

Console Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Console Testing this skillsynnaxlabs/synnax128—~5.4kAutomated safety check: PassCustom licence
Effect TSmattiacerutti/supernova187—~2.8kAutomated safety check: PassMIT
Concept Page Test Writerleonardomso/33-js-concepts67k—~5.5kAutomated safety check: PassMIT
Caliber Testingcaliber-ai-org/ai-setup1.3k—~3.2kAutomated safety check: PassMIT
Effect TStellahq/opensession392—~3.7kAutomated safety check: PassMIT
MoAI TDD Workflowmodu-ai/moai-adk1.2k—~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Effect TS

    mattiacerutti/supernova

    Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source.

    187 GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Concept Page Test Writer

    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.

    67k GitHub stars~5.5k tokensUpdated 27 days ago
    Testing & QAAuto-check passed

  • Caliber Testing

    caliber-ai-org/ai-setup

    Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment…

    1.3k GitHub stars~3.2k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

  • Effect TS

    tellahq/opensession

    Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.

    392 GitHub stars~3.7k tokensUpdated today
    Testing & QAAuto-check passed

  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Test Coverage

    scott-fryxell/brayness

    Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

    124 GitHub stars~1.6k tokensUpdated 10 days ago
    Testing & QAAuto-check passed

More from synnaxlabs/synnax

All 10 skills in this repo

  • PR Comments

    synnaxlabs/synnax

    Workflow for working through unresolved review comments on a pull request you authored.

    128 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Synnax Integration Debug

    synnaxlabs/synnax

    Triage failures from the Synnax integration test suite (uv run tc ...).

    128 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

  • Code Review

    synnaxlabs/synnax

    Process and hard rules for conducting code reviews in this repo: PRs, branches, commit ranges, and working diffs.

    128 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Create Linear Issue

    synnaxlabs/synnax

    Synnax Linear issue conventions. An agent skill from synnaxlabs/synnax.

    128 GitHub stars~846 tokensUpdated today
    Auto-check passed

  • Design

    synnaxlabs/synnax

    Process and hard rules for designing and planning complex new features, refactors, and re-architectures.

    128 GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Eb Review

    synnaxlabs/synnax

    Process and hard rules for a fast software quality audit of work this session just produced, or of a solution being proposed before it is built.

    128 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Console Testing

What does Console Testing do?

Rules for writing and editing unit tests in the Console (console/src//.spec.ts[x]). Console Testing is an agent skill from synnaxlabs/synnax.ts[x]).

When should I use Console Testing?

Console Testing fits situations like: reviewing a console Vitest spec; reaching for a test wrapper/store/fixture; deciding whether to mock; use real infrastructure.

How do I install Console Testing in Claude Code?

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

How do I install Console Testing in Codex?

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

Can I use Console 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 synnaxlabs/synnax --skill console-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/console-testing, .gemini/skills/console-testing, .github/skills/console-testing and .opencode/skills/console-testing in your project.

What does Console Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Console Testing is instructions for the agent only.

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

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

About 5.4k tokens (SKILL.md is roughly 22k 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 Console Testing?

Skills that share tags, products or a category with Console Testing: Effect TS (mattiacerutti/supernova, 187 stars), Concept Page Test Writer (leonardomso/33-js-concepts, 67k stars), Caliber Testing (caliber-ai-org/ai-setup, 1.3k stars) and Effect TS (tellahq/opensession, 392 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Console Testing?

synnaxlabs (a GitHub organization) maintains it in synnaxlabs/synnax, which has 128 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.

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