Solo Maintainer Release
serithemage/serverless-openclaw
Runs solo-maintainer release work end-to-end: release readiness review, notes, tags, GitHub release creation, deploy workflow dispatch, and post-release verification.
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…
$ npx skills add LanternOps/breeze --skill e2e-coverage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LanternOps/breeze e2e-coverage --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/LanternOps/breeze.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/e2e-coverage .claude/skills/e2e-coverage && 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 "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .claude/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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/LanternOps/breeze/tree/main/.claude/skills/e2e-coverageType 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 LanternOps/breeze --skill e2e-coverage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LanternOps/breeze e2e-coverage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LanternOps/breeze.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/e2e-coverage .agents/skills/e2e-coverage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .agents/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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 LanternOps/breeze --skill e2e-coverage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LanternOps/breeze e2e-coverage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LanternOps/breeze.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/e2e-coverage .cursor/skills/e2e-coverage && 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 "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .cursor/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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/LanternOps/breeze.git --path .claude/skills/e2e-coverage--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 LanternOps/breeze --skill e2e-coverage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LanternOps/breeze e2e-coverage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LanternOps/breeze.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/e2e-coverage .gemini/skills/e2e-coverage && 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 "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .gemini/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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 LanternOps/breeze e2e-coverageInstalls 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 LanternOps/breeze --skill e2e-coverage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LanternOps/breeze.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/e2e-coverage .github/skills/e2e-coverage && 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 "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .github/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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 LanternOps/breeze --skill e2e-coverage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LanternOps/breeze e2e-coverage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LanternOps/breeze.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/e2e-coverage .opencode/skills/e2e-coverage && 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 "e2e-coverage" agent skill from https://github.com/LanternOps/breeze/tree/main/.claude/skills/e2e-coverage into .opencode/skills/e2e-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-coverage", 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.
e2e-coverageA 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…
E2E Coverage is an agent skill from LanternOps/breeze. Use 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 sweeps, or resuming a partial sweep. Tracks coverage across runs so each sweep only tests the delta. NOT for single-feature post-implementation checks (use feature-testing for that).
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `runbook.md`).
It sits in Testing & QA, covering End-to-end testing and Feature launches and release readiness. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 1f72bb7. 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.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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.
E2E Coverage loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 704 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 LanternOps/breeze at commit 1f72bb7, republished under its AGPL-3.0 licence (© LanternOps). 704 words, ~1,604 tokens.
.claude/skills/e2e-coverage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.A coverage sweep verifies everything that changed since a baseline (a release tag or the last sweep), live, across UI/API/agent layers — and records what passed, failed, or was deferred so the next sweep is cheaper.
Core principle: every sweep starts from the last sweep. You test the delta (new commits + previously-deferred items), reuse a known-good environment recipe, and write results back to a durable ledger. Efficiency compounds: the env setup is recorded once, and covered ground is never re-tested.
For single-feature post-implementation verification, use the feature-testing skill instead — this skill is for broad multi-PR passes and reuses feature-testing's per-layer mechanics.
The running containers may NOT be running the code you think they are. A checked-out branch does not mean the live stack serves it — the containers can be an old image, a detached build, or a stale dist/. Testing against the wrong build produces false PASSes and phantom 404s.
Always verify the live stack before testing anything. See runbook.md → "Verify the stack is running the code under test". This is step 0 of every sweep.
digraph sweep {
rankdir=TB;
baseline [label="1. Baseline = max(last release tag, last swept commit)", shape=box];
delta [label="2. Delta = git log baseline..HEAD + carry-forward unresolved items", shape=box];
env [label="3. Verify/bring up env (runbook.md) — confirm it serves HEAD", shape=box];
classify [label="4. Classify each item: P0/P1/P2 x API/UI/AGENT/SKIP, creds-free vs creds-gated", shape=box];
test [label="5. Test the delta (reuse runbook recipes); record as you go", shape=box];
record [label="6. Write plan + results files; update the index pointer", shape=box];
baseline -> delta -> env -> classify -> test -> record;
}git tag --sort=-creatordate | head → last released tag. Find the most recent docs/testing/*-test-results.md and its "last swept commit". Baseline = whichever is newer. If no prior sweep, baseline = the last release tag.git log <baseline>..HEAD --oneline. Open the previous results file and carry forward every item still marked DEFERRED / NEEDS-CREDS / open FAIL — recheck whether creds/agents are now available. Items marked PASS below the baseline are not re-tested.runbook.md. Don't rediscover them.runbook.md recipes (login/JWT, RBAC negative tests, device lookups) and feature-testing's per-layer mechanics. Record each result immediately.Two files per sweep in docs/testing/, plus one living index. Keep the existing format (see docs/testing/v0.66.1-to-HEAD-*.md as the reference shape).
| File | Purpose |
|---|---|
docs/testing/<baseline>-to-HEAD-test-plan.md | The classified checklist of delta items (one per PR/commit), P0/P1/P2 + layer tags |
docs/testing/<baseline>-to-HEAD-test-results.md | Results: per-item status + evidence, findings, bugs filed. Records the "last swept commit". |
docs/testing/e2e-coverage-index.md | One line per sweep: baseline → results file → last-swept commit. The pointer the next sweep reads first. |
Status legend (use these exact tokens so the next sweep can grep them):
PASS — verified live, with evidence.FAIL — broken; file/track a bug, link it. Stays carried-forward until fixed+reverified.DEFERRED — testable but not exercised this run (time/data); say why.NEEDS-CREDS — blocked on external credentials or a live agent (Google/M365 tenant, Win/macOS agent). Carried forward.SKIP — covered by unit/CI; no manual E2E warranted (dep bumps, internal refactors). Note it; don't silently omit.Priority legend: P0 = security / auth / multi-tenant isolation / data corruption. P1 = user-visible new feature or behavior change. P2 = secondary surface or pre-existing area touched.
| Need | Command / pointer |
|---|---|
| Last release tag | git tag --sort=-creatordate | head |
| Delta since baseline | git log <baseline>..HEAD --oneline |
| Is the live stack serving HEAD? | runbook.md → stale-stack verification |
| Bring up local env (caddy + dev mode) | runbook.md → bring-up |
| Local login → JWT | runbook.md → JWT helper (admin@breeze.local / BreezeAdmin123!) |
| RBAC negative tests | runbook.md → site-scoped e2e-sitea user |
| Seed topology (orgs/sites/devices) | runbook.md → seed topology |
| curl fails inside a loop? | runbook.md → sandbox gotcha (use /usr/bin/curl, no loops) |
NEEDS-CREDS and carry forward — don't let them vanish from coverage.E2E_* env creds locally. Those target 2breeze.app (often down). Local DB uses admin@breeze.local / BreezeAdmin123! — see runbook.© 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
SKILL.md and 1 other file in .claude/skills/e2e-coverage of LanternOps/breeze.
Open the folder on GitHubat commit 1f72bb7
E2E Coverage 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 |
|---|---|---|---|---|---|---|
| E2E Coverage this skillLanternOps/breeze | 130 | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 | |
| Solo Maintainer Releaseserithemage/serverless-openclaw | 196 | — | ~418 | Automated safety check: Pass | None | |
| Releasecodewhale-hq/Codewhale | 41k | — | ~189 | Automated safety check: Pass | MIT | |
| Test Scenariosphuryn/pm-skills | 27k | — | ~866 | Automated safety check: Pass | MIT | |
| Hai Goalhylarucoder/hai-stack | 380 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Qe Courtproffesor-for-testing/agentic-qe | 494 | — | ~3.2k | Automated safety check: Pass | MIT |
serithemage/serverless-openclaw
Runs solo-maintainer release work end-to-end: release readiness review, notes, tags, GitHub release creation, deploy workflow dispatch, and post-release verification.
codewhale-hq/Codewhale
Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness.
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
hylarucoder/hai-stack
Creates or rewrites a goal document for ambiguous, multi-phase, high-risk, or explicitly planned execution: verifiable outcome, boundary, current state, phases, proof-bearing todos, dry-run, and…
proffesor-for-testing/agentic-qe
Adversarial review court — a delivery (diff, PR, test suite, or artifact) is prosecuted by independent AI reviewers from different vendors, each with its own probe set, then a SHIP verdict must…
petrkindlmann/qa-skills
Build a single sprint or release test plan. An agent skill from petrkindlmann/qa-skills.
LanternOps/breeze
Quick reference for the Breeze RMM Go agent architecture, commands, configuration, build process, and data flows.
LanternOps/breeze
A skill your agent uses when debugging agent issues, investigating agent errors, checking agent connectivity, or reviewing agent diagnostic logs.
LanternOps/breeze
Quick reference for the Breeze RMM AI Agent system architecture, MCP tools, streaming chat, cost tracking, guardrails, and MCP server.
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…
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…
LanternOps/breeze
A skill your agent uses when reviewing, triaging, or managing the incoming GitHub backlog on the Breeze repo — PRs, Discussions, AND Issues.
Categories
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…. E2E Coverage is an agent skill from LanternOps/breeze. Use 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 sweeps, or resuming a partial sweep.
E2E Coverage fits situations like: running a broad manual/AI-driven end-to-end verification of Breeze RMM across many merged PRs; commits — test everything since the last release; release-readiness sweeps; resuming a partial sweep.
Run `npx skills add LanternOps/breeze --skill e2e-coverage -a claude-code`. Or copy the skill folder (.claude/skills/e2e-coverage in LanternOps/breeze) into .claude/skills/e2e-coverage in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LanternOps/breeze --skill e2e-coverage -a codex`. Or copy the skill folder (.claude/skills/e2e-coverage in LanternOps/breeze) into .agents/skills/e2e-coverage 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 LanternOps/breeze --skill e2e-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/e2e-coverage, .gemini/skills/e2e-coverage, .github/skills/e2e-coverage and .opencode/skills/e2e-coverage in your project.
Going by SKILL.md and its folder, E2E Coverage needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. 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.
E2E Coverage 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.
About 1.6k tokens (SKILL.md is roughly 6.4k 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 E2E Coverage: Solo Maintainer Release (serithemage/serverless-openclaw, 196 stars), Release (codewhale-hq/Codewhale, 41k stars), Test Scenarios (phuryn/pm-skills, 27k stars) and Hai Goal (hylarucoder/hai-stack, 380 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.