Agent skill

Skill Review

by QoderAI in QoderAI/better-harness

A skill your agent uses when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template…

MITAuto-check passedWriting & Content

Install Skill Review

skills CLI
$ npx skills add QoderAI/better-harness --skill skill-review -a claude-code

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

GitHub CLI
$ gh skill install QoderAI/better-harness skill-review --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/QoderAI/better-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/skill-review .claude/skills/skill-review && 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
skill-review
GitHub stars
2.4k
Token cost
~802 tokens
SKILL.md length
354 words
Files
4 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template…

  • Works in 6 steps: Resolve the target skill or prompt… → Read repo instructions first: nearest… → Trace the chain from entrypoint to… → …
  • Reviewing Codex
  • SKILL.md covers Review Workflow, Review Lenses, Finding Severity and Report Shape
  • Calls git

What it does

Skill Review is an agent skill from QoderAI/better-harness. Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/audit-checklist.md`, `references/inspection-commands.md` and `references/reference-patterns.md`).

It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: An open-source Harness Engineering platform for coding agents—define harnesses as code, run controlled experiments, inspect evidence, and compare outcomes. Turn task evidence… The licence is MIT.

When your agent uses it

  • Reviewing Codex
  • Repo-local skills and their prompt chains for trigger quality
  • Workflow clarity
  • Progressive disclosure

Example prompts

  • “/skill-review”

Workflow steps

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

  1. Resolve the target skill or prompt chain. If the user names a path, stay on
  2. Read repo instructions first: nearest AGENTS.md, plugin manifests, and the
  3. Trace the chain from entrypoint to references, templates, scripts, detectors,
  4. Audit the contract before editing. Use Audit Checklist
  5. If the user asked for changes, patch only the smallest owning files. Keep
  6. Validate with the lightest real gate available: skill validator, repo tests,

What it can do on your machine

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

    • git

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

  • Network

    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.

  • 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

Skill Review loads about 802 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 354 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~802
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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 QoderAI/better-harness at commit 34899f3, republished under its MIT licence (© QoderAI). 354 words, ~802 tokens.

Download SKILL.mdSave it as .claude/skills/skill-review/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
skill-review
description
Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.

Skill Review

Review a skill as an execution contract, not as prose. Trace how an agent would enter, load, delegate, produce artifacts, and verify results; then report the smallest changes that would improve that chain.

Review Workflow

  1. Resolve the target skill or prompt chain. If the user names a path, stay on that path and its directly linked resources.
  2. Read repo instructions first: nearest AGENTS.md, plugin manifests, and the target SKILL.md frontmatter/body.
  3. Trace the chain from entrypoint to references, templates, scripts, detectors, tests, generated artifacts, and validation commands. Build an ownership map: what file owns workflow, output structure, runtime rules, style, and tests.
  4. Audit the contract before editing. Use Audit Checklist and Reference Patterns as lenses.
  5. If the user asked for changes, patch only the smallest owning files. Keep generated helpers, smoke scripts, and local experiments outside SKILL.md unless they are durable resources the skill must use.
  6. Validate with the lightest real gate available: skill validator, repo tests, plugin validation, or a bounded agent smoke. State any gate that could not be run.

Use subagents only as an evaluation surface or for independent broad research. The lead agent owns the review, final calibration, and file edits. Pass raw artifacts and task-local scope to subagents; do not pass the intended answer.

Show full SKILL.md (138 more words)Show less

Review Lenses

  • Audit Checklist: trigger contract, progressive disclosure, workflow/delegation, template ownership, readability, evidence.
  • Reference Patterns: reusable design lenses such as Trigger/Protocol split, Gate Function, and Output Contract Slots.
  • Fast Inspection Commands: starting rg, wc, and git diff --check probes adapted to the repo.

Finding Severity

  • P0: The skill points to missing, empty, contradictory, or invalid resources; an agent can follow the instructions and fail.
  • P1: The skill works but wastes context, duplicates ownership, hides key constraints, or produces unreadable output.
  • P2: Style, naming, wording, or organization issues that reduce scanability without breaking the workflow.

Report Shape

Lead with findings, ordered by severity. Keep each finding concrete:

text
P1 - <short title>
File: <path>:<line>
Why it matters: <execution or output risk>
Evidence: <quoted phrase, command result, or linked resource>
Fix: <smallest owning-file change>
Validation: <command or smoke that should prove it>

After findings, add open questions only when they block a safe change. If the user asked for edits, include changed files and validation results after the findings. Default to the user's language.

© QoderAI, MIT. 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 3 other files (references) in .agents/skills/skill-review of QoderAI/better-harness.

  • SKILL.md
  • references/audit-checklist.md
  • references/inspection-commands.md
  • references/reference-patterns.md

Open the folder on GitHubat commit 34899f3

Compare with similar skills

Skill Review 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 Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Review this skillQoderAI/better-harness2.4k—~802Automated safety check: PassMIT
Explanation Guidancetestdouble/han279—~949Automated safety check: PassMIT
Stakeholder Summarytestdouble/han279—~6.3kAutomated safety check: PassMIT
Blueprint Style Rulesreceptron/mulmoterminal236—~1.4kAutomated safety check: PassMIT
Kkirikkirifivetaku/gptaku-plugins-codex128—~12kAutomated safety check: PassMIT
Asd Ste100danyuchn/asd-ste100-skill4k—~4.1kAutomated safety check: PassMIT

Similar skills

  • Explanation Guidance

    testdouble/han

    Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and…

    279 GitHub stars~949 tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Stakeholder Summary

    testdouble/han

    Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off.

    279 GitHub stars~6.3k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Blueprint Style Rules

    receptron/mulmoterminal

    Measure the models with chaff, then write the style twice: chaff.yaml for what a machine checks, STYLE.md for what the writer reads — with a reason for every decision.

    236 GitHub stars~1.4k tokensUpdated today
    Writing & ContentAuto-check passed
  • Kkirikkiri

    fivetaku/gptaku-plugins-codex

    Assemble and run a Codex-native agent team from one plain-language request.

    128 GitHub stars~12k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4k GitHub stars~4.1k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Simple Issue Description

    every-app/open-seo

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.

    23k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed

More from QoderAI/better-harness

All 11 skills in this repo
  • Intent Correlation Analysis

    QoderAI/better-harness

    Analyze a bounded IntentCorrelationPacketV1 and propose reviewable links among user inputs, execution slices, change units, commits, artifacts, and validation outcomes.

    2.4k GitHub stars~1.2k tokensUpdated 10 days ago
    Auto-check passed
  • Better Harness

    QoderAI/better-harness

    A skill your agent uses when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable…

    2.4k GitHub stars~3k tokensUpdated 10 days ago
    Auto-check passed
  • Generate Harness Dsl

    QoderAI/better-harness

    Generate, revise, or review complete Harness as Code .harness files when a coding-agent workflow, agent role, skill, tool contract, MCP connection, runtime, or deployment must be compiler-valid and…

    2.4k GitHub stars~761 tokensUpdated 10 days ago
    Auto-check passed
  • Harness Skill Creator

    QoderAI/better-harness

    A skill your agent uses when bootstrapping or tightening the smallest harness-oriented skill from an existing repository, workflow, evaluation corpus, or harness-analysis chain.

    2.4k GitHub stars~844 tokensUpdated 10 days ago
    Auto-check passed
  • Diagnose Backend Bug

    QoderAI/better-harness

    Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records.

    2.4k GitHub stars~1.2k tokensUpdated 10 days ago
    Auto-check passed
  • Reproduce Frontend Bug

    QoderAI/better-harness

    Build a bounded, replayable browser or UI bug reproduction from GitHub Issues, Jira, Aone, user-provided exports, screenshots, videos, comments, or attachments.

    2.4k GitHub stars~1.3k tokensUpdated 10 days ago
    Auto-check passed

Questions about Skill Review

What does Skill Review do?

A skill your agent uses when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template…. Skill Review is an agent skill from QoderAI/better-harness. Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.

When should I use Skill Review?

Skill Review fits situations like: reviewing Codex; repo-local skills and their prompt chains for trigger quality; workflow clarity; progressive disclosure.

How do I install Skill Review in Claude Code?

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

How do I install Skill Review in Codex?

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

Can I use Skill Review 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 QoderAI/better-harness --skill skill-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-review, .gemini/skills/skill-review, .github/skills/skill-review and .opencode/skills/skill-review in your project.

What does Skill Review need to run?

Going by SKILL.md and its folder, Skill Review needs the command-line tools its instructions call (git).

Does Skill Review access the network?

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.

Is Skill Review 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 Skill Review use?

Skill Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skill Review use?

About 802 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Skill Review?

Skills that share tags, products or a category with Skill Review: Explanation Guidance (testdouble/han, 279 stars), Stakeholder Summary (testdouble/han, 279 stars), Blueprint Style Rules (receptron/mulmoterminal, 236 stars) and Kkirikkiri (fivetaku/gptaku-plugins-codex, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Review?

QoderAI (a GitHub organization) maintains it in QoderAI/better-harness, which has 2,364 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 28, 2026.

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