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

Libreqos Review Subagents Workflow

by LibreQoE in LibreQoE/LibreQoS

Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

GPL-2.0Auto-check passedTesting & QA

Install Libreqos Review Subagents Workflow

skills CLI
$ npx skills add LibreQoE/LibreQoS --skill libreqos-review-subagents-workflow -a claude-code

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

GitHub CLI
$ gh skill install LibreQoE/LibreQoS libreqos-review-subagents-workflow --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/LibreQoE/LibreQoS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/libreqos-review-subagents-workflow .claude/skills/libreqos-review-subagents-workflow && 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
libreqos-review-subagents-workflow
GitHub stars
718
Token cost
~1.2k tokens
SKILL.md length
527 words
Files
2
Skills in repo
8
Repo updated
First seen
Licence
GPL-2.0

At a glance

Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

  • Works in 7 steps: After any change to the repo, spawn… → After each source-code implementation… → After a substantial implementation batch… → …
  • Code changes need recent-diff review for DRY/duplication
  • SKILL.md covers Agents, Required Invocation Rules, What Counts As A Large Session and Invocation Pattern, plus 2 more sections
  • Calls cargo

What it does

Libreqos Review Subagents Workflow is an agent skill from LibreQoE/LibreQoS. Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions. Use when code changes need recent-diff review for DRY/duplication, slop detection, Rust quality, accessibility, test coverage, scope control, and algorithmic sanity.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering Subagents, Test coverage and Accessibility. It works with Rust. The repository describes itself as: Self-hosted traffic management and network operations platform for ISPs. Use CAKE and fqcodel to reduce bufferbloat, enforce bandwidth plans, and troubleshoot congestion with… The licence is GPL-2.0.

When your agent uses it

  • Code changes need recent-diff review for DRY/duplication
  • Algorithmic sanity

Example prompts

  • “/libreqos-review-subagents-workflow”

Workflow steps

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

  1. After any change to the repo, spawn heckler against the current recent changes.
  2. After each source-code implementation batch, also spawn reaper against the same scope.
  3. After a substantial implementation batch in a large session, spawn thomas, beck, and jonas in parallel against the current recent changes.
  4. If UI changed, spawn helen at the same checkpoint.
  5. Use the current worktree diff as the default scope. If the worktree is clean but the session included recent commits, pass an explicit…
  6. Review the findings, fix valid issues, or record why a concern is intentionally accepted.
  7. Before final completion, rerun any reviewer whose scope changed since the prior pass.

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • cargo

    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

Libreqos Review Subagents Workflow loads about 1.2k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 527 words of instructions outside code blocks.

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

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 LibreQoE/LibreQoS at commit 3eeaf94, republished under its GPL-2.0 licence (© LibreQoE). 527 words, ~1,248 tokens.

Download SKILL.mdSave it as .claude/skills/libreqos-review-subagents-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
libreqos-review-subagents-workflow
description
Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions. Use when code changes need recent-diff review for DRY/duplication, slop detection, Rust quality, accessibility, test coverage, scope control, and algorithmic sanity.

LibreQoS Review Sub-Agents Workflow

Use this skill when code changes in this repo need the project-standard reviewer pass.

Agents

  • thomas: adversarial review of recent code changes for Rust best practices, safety, idiomatic style, and warning or Clippy suppression
  • beck: review of recent code changes for meaningful unit-test coverage and weak or pointless tests
  • jonas: review of recent code changes for scope drift, unrelated cleanup, and algorithmic or performance mistakes
  • helen: review of recent user-interface changes for accessibility, ADA issues, missing alt text, missing labels, missing ARIA semantics, and related barriers
  • reaper: review of recent changes for duplicated functionality (DRY violations), dead code, placeholders, and lazy algorithm choices
  • heckler: hyper-skeptical slop detector for AI slop, dead code, placeholders, and lazy algorithm choices; returns a slop score (goal: 0/10)

Required Invocation Rules

  • After any changes to the repo, invoke heckler before returning to the user.
  • If heckler reports a non-zero slop score, print SLOP! SLOP! SLOP ALERT!, fix the slop, and re-run until the score is 0/10 (see $libreqos-anti-slop).
  • After each batch of source-code edits (Rust/Python/JS/etc.), invoke reaper before returning to the user.
  • During large sessions, invoke thomas, beck, and jonas together after substantial implementation batches.
  • Always invoke thomas, beck, and jonas before the final user-facing completion message when code changed in the session.
  • After any user-interface change, invoke helen.
  • If the session includes both UI and code changes, invoke helen alongside the others at the same review checkpoint.

What Counts As A Large Session

Treat a session as large when any of these are true:

  • the diff is more than a tiny one-file tweak
  • multiple files or crates changed
  • you finished a meaningful implementation batch and are about to continue layering on more work
  • the blast radius is not obvious from a quick glance
Show full SKILL.md (234 more words)Show less

Invocation Pattern

  1. After any change to the repo, spawn heckler against the current recent changes.
  2. After each source-code implementation batch, also spawn reaper against the same scope.
  3. After a substantial implementation batch in a large session, spawn thomas, beck, and jonas in parallel against the current recent changes.
  4. If UI changed, spawn helen at the same checkpoint.
  5. Use the current worktree diff as the default scope. If the worktree is clean but the session included recent commits, pass an explicit commit or diff range.
  6. Review the findings, fix valid issues, or record why a concern is intentionally accepted.
  7. Before final completion, rerun any reviewer whose scope changed since the prior pass.

Required Prompt Shape

When spawning a reviewer, include:

  • the review scope:
    • current worktree diff, or
    • explicit commit or diff range
  • the intent of the change
  • any area-specific context that helps the reviewer load the right project skills

Example prompt for thomas, beck, and jonas:

text
Review the recent changes for this session. Use the current worktree diff as the review scope unless I specify a narrower range. The goal of the change is: <brief intent>.

Example prompt for reaper:

text
Review the recent changes for duplicated functionality (DRY violations), dead code, placeholders, and lazy algorithm choices. Use the current worktree diff as the review scope unless I specify a narrower range. The goal of the change is: <brief intent>.

Example prompt for heckler:

text
Review the recent changes for AI slop, dead code, placeholders, and lazy algorithm choices. Return a slop score (goal: 0/10). Use the current worktree diff as the review scope unless I specify a narrower range. The goal of the change is: <brief intent>.

Example prompt for helen:

text
Review the recent user-interface changes for this session. Use the current worktree diff as the review scope unless I specify a narrower range. Focus on accessibility and other user barriers.

Notes

  • These agents are read-only review surfaces, not replacements for targeted tests, cargo check, cargo clippy, or visual verification.
  • For tiny trivial edits, an intermediate review pass may be unnecessary, but the final required review still applies whenever code changed.
  • In this repo, the subagent definitions live under .codex/agents/*.toml (including .codex/agents/reaper.toml and .codex/agents/heckler.toml).
  • heckler is the enforcement surface for $libreqos-anti-slop.

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

Files

SKILL.md and 1 other file in .agents/skills/libreqos-review-subagents-workflow of LibreQoE/LibreQoS.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 3eeaf94

Compare with similar skills

Libreqos Review Subagents Workflow 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.

Libreqos Review Subagents Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Libreqos Review Subagents Workflow this skillLibreQoE/LibreQoS718—~1.2kAutomated safety check: PassGPL-2.0
Dev ReviewFHIR/fhir-codegen154—~5kAutomated safety check: PassMIT
Ds Test Componentbaloise/design-system114—~2.1kAutomated safety check: PassApache-2.0
Find Untested Sourcesdotnet/skills5.6k1 repos~3.3kAutomated safety check: PassMIT
Reviewgetsentry/sentry-react-native1.8k—~1.9kAutomated safety check: PassMIT
Reviewwebern/cargo-readme385—~2kAutomated safety check: NotesApache-2.0

Similar skills

  • Dev Review

    FHIR/fhir-codegen

    Performs a two-track code-quality and QA review in the roles of a staff-level Engineering Lead and QA Lead, then synthesizes both critiques into a single analysis.md.

    154 GitHub stars~5k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Ds Test Component

    baloise/design-system

    Auto-generate all test files for DS components including visual, a11y, component, page object, and unit tests.

    114 GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Find Untested Sources

    dotnet/skills

    Official

    Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.

    5.6k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed

  • Review

    getsentry/sentry-react-native

    Official

    Three-axis review of the branch diff — Standards (this repo's documented standards + public API/bridge surface), Spec (the originating Linear/GitHub issue or PR), and Correctness (runtime bugs + the…

    1.8k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Review

    webern/cargo-readme

    Reviews a GitHub pull request for correctness, architecture, security, backward compatibility, and test coverage.

    385 GitHub stars~2k tokensUpdated 11 days ago
    Testing & QAAuto-check: notes

  • Supercov

    supercorp-ai/supercov

    Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.

    148 GitHub starsUsed in 1 repo~415 tokens
    Testing & QAAuto-check passed

More from LibreQoE/LibreQoS

All 8 skills in this repo

  • Libreqos Anti Slop

    LibreQoE/LibreQoS

    Anti-slop workflow for LibreQoS. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~820 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Packaging Release

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for packaging, release, and shipped-file changes.

    718 GitHub stars~781 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Python Workflow

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for Python orchestration, scheduler, integrations, and helper scripts under src/.

    718 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Git Workflow

    LibreQoE/LibreQoS

    Shared LibreQoS git workflow. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~479 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Lqos Sys Ebpf

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for lqossys eBPF, C wrapper, bindgen, and pinned-map ABI work.

    718 GitHub stars~793 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Node Manager Frontend

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for nodemanager frontend work. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~915 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Libreqos Review Subagents Workflow

What does Libreqos Review Subagents Workflow do?

Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions. Libreqos Review Subagents Workflow is an agent skill from LibreQoE/LibreQoS. Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

When should I use Libreqos Review Subagents Workflow?

Libreqos Review Subagents Workflow fits situations like: code changes need recent-diff review for DRY/duplication; algorithmic sanity.

How do I install Libreqos Review Subagents Workflow in Claude Code?

Run `npx skills add LibreQoE/LibreQoS --skill libreqos-review-subagents-workflow -a claude-code`. Or copy the skill folder (.agents/skills/libreqos-review-subagents-workflow in LibreQoE/LibreQoS) into .claude/skills/libreqos-review-subagents-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Libreqos Review Subagents Workflow in Codex?

Run `npx skills add LibreQoE/LibreQoS --skill libreqos-review-subagents-workflow -a codex`. Or copy the skill folder (.agents/skills/libreqos-review-subagents-workflow in LibreQoE/LibreQoS) into .agents/skills/libreqos-review-subagents-workflow in your project. Codex loads it when a task matches its description.

Can I use Libreqos Review Subagents Workflow 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 LibreQoE/LibreQoS --skill libreqos-review-subagents-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/libreqos-review-subagents-workflow, .gemini/skills/libreqos-review-subagents-workflow, .github/skills/libreqos-review-subagents-workflow and .opencode/skills/libreqos-review-subagents-workflow in your project.

What does Libreqos Review Subagents Workflow need to run?

Going by SKILL.md and its folder, Libreqos Review Subagents Workflow needs the command-line tools its instructions call (cargo).

Does Libreqos Review Subagents Workflow 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 Libreqos Review Subagents Workflow 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 Libreqos Review Subagents Workflow use?

Libreqos Review Subagents Workflow is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Libreqos Review Subagents Workflow use?

About 1.2k tokens (SKILL.md is roughly 5k 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 Libreqos Review Subagents Workflow?

Skills that share tags, products or a category with Libreqos Review Subagents Workflow: Dev Review (FHIR/fhir-codegen, 154 stars), Ds Test Component (baloise/design-system, 114 stars), Find Untested Sources (dotnet/skills, 5.6k stars) and Review (getsentry/sentry-react-native, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Libreqos Review Subagents Workflow?

LibreQoE (a GitHub organization) maintains it in LibreQoE/LibreQoS, which has 718 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 4, 2026.

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