New: 97,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

Breeze Testing

by LanternOps in LanternOps/breeze

Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature.

AGPL-3.0Auto-check passedTesting & QA

Install Breeze Testing

skills CLI
$ npx skills add LanternOps/breeze --skill breeze-testing -a claude-code

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

GitHub CLI
$ gh skill install LanternOps/breeze breeze-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/LanternOps/breeze.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/breeze-testing .claude/skills/breeze-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
breeze-testing
GitHub stars
130
Token cost
~668 tokens
SKILL.md length
316 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature.

  • Works in 6 steps: Happy path — basic success case. → Auth/authz — unauthenticated, wrong… → Validation — missing required fields,… → …
  • Modifying tests in this repo
  • SKILL.md covers Writing API Route Tests (Vitest), Writing Go Agent Tests, Writing Shared Validator Tests and Coverage Contract — Every New…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Breeze Testing is an agent skill from LanternOps/breeze. Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature. Use when writing or modifying tests in this repo.

Its SKILL.md is about 670 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, ORMs and data access and Brand voice and tone. It works with Vitest and Zod. The repository describes itself as: The open-source IT platform that comes with the workers. RMM + PSA in one system, with a governed AI operator built in. The licence is AGPL-3.0.

When your agent uses it

  • Modifying tests in this repo
  • Tasks that involve Unit testing
  • Tasks that involve ORMs and data access

Example prompts

  • “/breeze-testing”

Workflow steps

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

  1. Happy path — basic success case.
  2. Auth/authz — unauthenticated, wrong role, wrong org.
  3. Validation — missing required fields, invalid types, boundary values.
  4. Multi-tenant isolation — cross-org access denied.
  5. Error cases — not found, conflict, server error.
  6. Edge cases — empty arrays, nil inputs, concurrent access.

What it can do on your machine

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

    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

Breeze Testing loads about 668 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 316 words of instructions outside code blocks.

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

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 LanternOps/breeze at commit 1f72bb7, republished under its AGPL-3.0 licence (© LanternOps). 316 words, ~668 tokens.

Download SKILL.mdSave it as .claude/skills/breeze-testing/SKILL.md (or your agent's skills folder).
name
breeze-testing
description
Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature. Use when writing or modifying tests in this repo.

Breeze Testing

Project-specific conventions for writing tests. Frameworks and file placement live in CLAUDE.md; this skill covers the writing craft: patterns that catch real bugs, gotchas that burn people, and the coverage contract every new feature must satisfy.

Writing API Route Tests (Vitest)

  • Mock Drizzle ORM query chains matching the exact chain pattern in the source (e.g., select().from().where()).
  • Always test multi-tenant isolation — verify org-scoped data can't be accessed cross-org.
  • Test all HTTP methods, auth/authz, Zod validation failures, not-found, and error cases.
  • Use proper UUIDs in mock data — Zod validates UUID format and will reject 'other-org'.
  • Avoid trailing slashes in test URLs — Hono sub-routers return 404 for trailing slashes.
  • vi.mock factories are hoisted — don't reference module-level const values inside them; use literal values instead.
  • Read 2-3 existing test files in the same directory before writing new ones to match patterns.

Writing Go Agent Tests

  • Use table-driven tests for functions with multiple input/output combinations.
  • Always run with -race flag to catch data races.
  • Mock external dependencies (network, OS, filesystem) — never make real network calls.
  • Use build tags for platform-specific tests: //go:build !windows or //go:build darwin.
  • Test nil/empty inputs, error paths, and concurrency safety (spawn goroutines in tests).
  • Place test helpers in the same package, not in a separate _test package.

Writing Shared Validator Tests

  • Test valid inputs, invalid inputs, boundary values, and Zod defaults/coercion.
  • For discriminated unions, test each variant separately.
  • Test omitempty/optional fields with both present and absent values.
  • For schemas with superRefine, test all validation branches.

Coverage Contract — Every New Feature Must Test

  1. Happy path — basic success case.
  2. Auth/authz — unauthenticated, wrong role, wrong org.
  3. Validation — missing required fields, invalid types, boundary values.
  4. Multi-tenant isolation — cross-org access denied.
  5. Error cases — not found, conflict, server error.
  6. Edge cases — empty arrays, nil inputs, concurrent access.
  • Frameworks, file placement, and CI integration: see CLAUDE.md → Testing Standards.
  • Post-implementation end-to-end verification: use the feature-testing skill.

© LanternOps, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/breeze-testing of LanternOps/breeze.

Open the folder on GitHubat commit 1f72bb7

Compare with similar skills

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

Breeze Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Breeze Testing this skillLanternOps/breeze130—~668Automated safety check: PassAGPL-3.0
Backend Testingbiersoeckli/QuickStack361—~670Automated safety check: PassGPL-3.0
Typescript Idiomsirahardianto/awesome-agv157—~6.1kAutomated safety check: PassMIT
Vue Idiomsirahardianto/awesome-agv157—~6kAutomated safety check: PassMIT
Nestjs Drizzle Crud Generatorgiuseppe-trisciuoglio/developer-kit355—~1.3kAutomated safety check: NotesMIT
Effect TStellahq/opensession392—~3.7kAutomated safety check: PassMIT

Similar skills

  • Backend Testing

    biersoeckli/QuickStack

    Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions.

    361 GitHub stars~670 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Typescript Idioms

    irahardianto/awesome-agv

    TypeScript strict typing: type narrowing, discriminated unions, Zod runtime validation, generic utility types, and Vitest testing.

    157 GitHub stars~6.1k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Vue Idioms

    irahardianto/awesome-agv

    Vue 3 Composition API patterns: <script setup syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing.

    157 GitHub stars~6k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Nestjs Drizzle Crud Generator

    giuseppe-trisciuoglio/developer-kit

    Generates complete CRUD modules for NestJS applications with Drizzle ORM.

    355 GitHub stars~1.3k tokensUpdated 27 days ago
    DatabasesAuto-check: notes

  • 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

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

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

More from LanternOps/breeze

All 14 skills in this repo

  • Agent Info

    LanternOps/breeze

    Quick reference for the Breeze RMM Go agent architecture, commands, configuration, build process, and data flows.

    130 GitHub stars~4.7k tokensUpdated today
    Auto-check: notes

  • Agent Log Debugging

    LanternOps/breeze

    A skill your agent uses when debugging agent issues, investigating agent errors, checking agent connectivity, or reviewing agent diagnostic logs.

    130 GitHub stars~1.6k tokensUpdated today
    Auto-check: notes

  • AI Agent

    LanternOps/breeze

    Quick reference for the Breeze RMM AI Agent system architecture, MCP tools, streaming chat, cost tracking, guardrails, and MCP server.

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

  • Breeze Helper

    LanternOps/breeze

    Quick reference for the Breeze Helper Tauri desktop app — architecture, Rust backend commands, React frontend, config files, IPC with the Go agent, helper chat API routes, tool approval flow, and…

    130 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • E2E Coverage

    LanternOps/breeze

    A skill your agent uses when running a broad manual/AI-driven end-to-end verification of Breeze RMM across many merged PRs or commits — "test everything since the last release", release-readiness…

    130 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Feature Delivery

    LanternOps/breeze

    A skill your agent uses when orchestrating Breeze implementation work from this seat — dispatching waves or issue fixes to background sessions, deciding whether an open PR gets merged, handling a…

    130 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Breeze Testing

What does Breeze Testing do?

Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature. Breeze Testing is an agent skill from LanternOps/breeze. Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature.

When should I use Breeze Testing?

Breeze Testing fits situations like: modifying tests in this repo; tasks that involve Unit testing; tasks that involve ORMs and data access.

How do I install Breeze Testing in Claude Code?

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

How do I install Breeze Testing in Codex?

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

Can I use Breeze 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 LanternOps/breeze --skill breeze-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/breeze-testing, .gemini/skills/breeze-testing, .github/skills/breeze-testing and .opencode/skills/breeze-testing in your project.

What does Breeze Testing need to run?

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

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

Breeze Testing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Breeze Testing use?

About 668 tokens (SKILL.md is roughly 2.7k 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 Breeze Testing?

Skills that share tags, products or a category with Breeze Testing: Backend Testing (biersoeckli/QuickStack, 361 stars), Typescript Idioms (irahardianto/awesome-agv, 157 stars), Vue Idioms (irahardianto/awesome-agv, 157 stars) and Nestjs Drizzle Crud Generator (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Breeze Testing?

LanternOps (a GitHub organization) maintains it in LanternOps/breeze, which has 130 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

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