Index of every page on this site: llms.txt
All skills
qoderai avatar

/skill-review

@c6240a8
by qoderaiqoderai/better-harness2.5k stars
208
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/qoderai/better-harness/skill-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈68 tokens for metadata: the name and description. ≈726 when used: this file. ≈1.5k more on demand in 3 files.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈274 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

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:

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill provides a structured workflow for auditing and improving other AI agent skills within a repository. It utilizes common command-line utilities for repository inspection and is designed to patch identified issues. The identified behaviors, such as shell command execution and file editing, are consistent with its stated purpose as a developer tool.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at c6240a8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago

README badge

README badge for qoderai/better-harness/skill-review