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

Brooks Harness

by sickn33 in sickn33/agentic-awesome-skills

Maintenance orchestrator for the brooks-lint plugin itself. An agent skill from sickn33/agentic-awesome-skills.

MITAuto-check passedDevelopment

Install Brooks Harness

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill brooks-harness -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills brooks-harness --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brooks-harness .claude/skills/brooks-harness && 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
brooks-harness
GitHub stars
47k
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
798 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Maintenance orchestrator for the brooks-lint plugin itself. An agent skill from sickn33/agentic-awesome-skills.

  • Works in 4 steps: Context check → Classify the request → Run the pipeline → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers When to Use, Pipeline, Phase 0 — Context check and Phase 1 — Classify the request, plus 6 more sections
  • Calls npm

What it does

Brooks Harness is an agent skill from sickn33/agentic-awesome-skills. Maintenance orchestrator for the brooks-lint plugin itself.

Its SKILL.md is about 1.8k 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 Development, covering Linting and formatting. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Linting and formatting

Example prompts

  • “/brooks-harness”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Context check
  2. Classify the request
  3. Run the pipeline
  4. Report & feedback

What it can do on your machine

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

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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

Brooks Harness loads about 1.8k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 798 words of instructions outside code blocks.

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

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 sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 798 words, ~1,774 tokens.

Download SKILL.mdSave it as .claude/skills/brooks-harness/SKILL.md (or your agent's skills folder).
name
brooks-harness
description
Maintenance orchestrator for the brooks-lint plugin itself.
risk
critical
source
https://github.com/hyhmrright/brooks-lint/tree/main/.claude/skills/brooks-harness
source_repo
hyhmrright/brooks-lint
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/hyhmrright/brooks-lint/blob/main/LICENSE

brooks-lint — Maintenance Harness (Orchestrator)

When to Use

Use this skill when you need maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + README + CHANGELOG + AGENTS/GEMINI in sync, audit trigger...

This skill orchestrates work on the brooks-lint repo itself. It runs a sequential subagent pipeline: each stage is a dedicated agent defined in .claude/agents/. Spawn each with the Agent tool, subagent_type set to the agent name, and always model: "opus". Stages depend on each other in order, so this is a pipeline, not a parallel team.

Pipeline

[orchestrator]
   Phase 0  context check
   Phase 1  classify request → select stages
   Phase 2  run selected stages in order, with a QA loop-back:
            skill-author → eval-curator → consistency-qa ─(FAIL)→ back to author
                                              │ PASS
                                              ▼
                            trigger-boundary-auditor   (only if a description changed)
                                              ▼
                                      release-manager  (only if release requested)
   Phase 3  report + collect feedback

Phase 0 — Context check

Determine the run mode before doing anything:

  • _workspace/brooks-harness/ exists + maintainer asks to redo part of a prior run → partial re-run: invoke only the affected stage(s), reusing prior notes.
  • _workspace/brooks-harness/ exists + a fresh request → new run: move the old folder to _workspace/brooks-harness_prev/, start clean.
  • No _workspace/brooks-harness/ → initial run: create it.

Run notes and the QA report live under _workspace/brooks-harness/. The real artifacts are the repo files themselves — agents edit skills/, evals/, manifests directly; _workspace/ only holds the run's notes and the PASS/FAIL verdict for audit.

Phase 1 — Classify the request

Pick the minimal set of stages. The QA stage is never skipped — every change is gated.

RequestauthorevalQAtrigger-auditrelease
Add a new skill✓ (via new-skill scaffold)✓✓✓—
Edit skill / guide content✓if codes changed✓if description changed—
Edit _shared/ framework✓if risk defs changed✓——
Eval suite only—✓✓——
Fix trigger descriptions✓—✓✓—
Release——✓—✓
Full: change + release✓as needed✓if applicable✓

Phase 2 — Run the pipeline

Spawn each selected stage as a subagent in order. Pass each agent (a) the task contract and (b) the previous stage's summary. Agents write their summaries to _workspace/brooks-harness/; read them between stages.

  1. skill-author — creates/edits the content. For a brand-new skill it invokes the new-skill scaffold. Returns the list of files touched + convention-relevant choices (new risk codes, new Step numbers, changed description trigger phrases).
  2. eval-curator — if skill-author reported new/changed risk codes or modes, adds the paired happy-path + false-positive scenarios and runs npm run evals.
  3. consistency-qa (gate — never skipped) — runs npm run validate + npm test + npm run evals, then the cross-document sync checks (manifests, README badge, CHANGELOG, AGENTS/GEMINI book count, eval count). Writes a PASS/FAIL verdict. On FAIL: loop back to the agent named in the verdict (author or eval-curator), fix, then re-run QA. Repeat once; if it still fails, stop and report to the maintainer.
  4. trigger-boundary-auditor — run only if a description field changed. It read-only audits the six shipped skills' trigger surfaces for false-triggering and routing collisions. Surface its findings; if it flags a real collision, loop back to skill-author.
  5. release-manager — run only if a release was requested, and only after QA PASS. Cuts the release via the release skill.
Show full SKILL.md (328 more words)Show less

Phase 3 — Report & feedback

Report: stages run, files changed, QA verdict, trigger-audit findings (if any), and the release URL (if any). Then offer the maintainer a feedback opening: "Anything to adjust in the result, the agent roles, or the pipeline order?" Record accepted changes in the CLAUDE.md harness change-log table.

Conventions this harness enforces

  • All Agent calls use model: "opus" — harness quality tracks agent reasoning.
  • consistency-qa must be general-purpose (it runs npm scripts); the trigger-boundary-auditor is read-only.
  • No slash commands are created — short forms are auto-installed by the session-start hook.
  • Direct-to-main: changes push to main without a PR (per repo CLAUDE.md); the global simplify→review→commit gate still applies to non-doc edits, but skill/guide content is markdown and follows the validate gate instead.

Error handling

  • A stage that fails once is retried once with its error as input; a second failure stops the pipeline and reports to the maintainer (no silent skip).
  • QA FAIL never proceeds to release.
  • Conflicting data is reported with provenance, not deleted.
  • High-risk git ops (--no-verify, --force, history rewrites) require explicit maintainer authorization — release-manager stops and asks.

Test scenarios

Normal flow — "add a brooks-security skill": Phase 1 selects author+eval+QA+audit. skill-author runs new-skill brooks-security, creates SKILL.md (with a sibling-carving "Do NOT trigger for:" clause) + guide; eval-curator adds an S-code happy-path + a false-positive scenario; consistency-qa runs the gate → PASS; trigger-boundary-auditor confirms no collision with brooks-review/audit. Report lists files + PASS.

Error flow — QA FAIL on book-count drift: maintainer adds a thirteenth book but edits only source-coverage.md. consistency-qa's cross-doc check finds README still says "twelve" → FAIL, attributed to skill-author. Orchestrator loops back; skill-author updates README/AGENTS/GEMINI wording; QA re-runs → PASS. No release was requested, so the pipeline ends at Phase 3.

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. 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 skills/brooks-harness of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Brooks Harness 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.

Brooks Harness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brooks Harness this skillsickn33/agentic-awesome-skills47k1 repos~1.8kAutomated safety check: PassMIT
Minimizing Ty Ecosystem Changesastral-sh/ruff50k—~4.6kAutomated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.4k—~2.2kAutomated safety check: PassMIT
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Minimizing Ty Ecosystem Changes

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…

    50k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Install Anti-Slop Oxlint Rules

    dmmulroy/anti-slop

    Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.4k GitHub stars~2.2k tokensUpdated 29 days ago
    DevelopmentAuto-check passed

  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Summarise Ecosystem Results

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Brooks Harness

What does Brooks Harness do?

Maintenance orchestrator for the brooks-lint plugin itself. An agent skill from sickn33/agentic-awesome-skills. Brooks Harness is an agent skill from sickn33/agentic-awesome-skills. Maintenance orchestrator for the brooks-lint plugin itself.

When should I use Brooks Harness?

Brooks Harness fits situations like: tasks that involve Linting and formatting.

How do I install Brooks Harness in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill brooks-harness -a claude-code`. Or copy the skill folder (skills/brooks-harness in sickn33/agentic-awesome-skills) into .claude/skills/brooks-harness in your project. Claude Code loads it when a task matches its description.

How do I install Brooks Harness in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill brooks-harness -a codex`. Or copy the skill folder (skills/brooks-harness in sickn33/agentic-awesome-skills) into .agents/skills/brooks-harness in your project. Codex loads it when a task matches its description.

Can I use Brooks Harness 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 sickn33/agentic-awesome-skills --skill brooks-harness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brooks-harness, .gemini/skills/brooks-harness, .github/skills/brooks-harness and .opencode/skills/brooks-harness in your project.

What does Brooks Harness need to run?

Going by SKILL.md and its folder, Brooks Harness needs the command-line tools its instructions call (npm).

Does Brooks Harness access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Brooks Harness 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 Brooks Harness use?

Brooks Harness is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brooks Harness use?

About 1.8k tokens (SKILL.md is roughly 7.1k 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 Brooks Harness?

Skills that share tags, products or a category with Brooks Harness: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars) and Rust Best Practices (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brooks Harness?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.