Agent skill

Inspect Quality

by danielvm-git in danielvm-git/bigpowers

Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema.

MITAuto-check passed

Install Inspect Quality

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a claude-code

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

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality --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/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inspect-quality .claude/skills/inspect-quality && 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/

Paste into Claude Code

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .claude/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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

$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality

Type 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.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/inspect-quality .agents/skills/inspect-quality && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .agents/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/inspect-quality .cursor/skills/inspect-quality && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .cursor/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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

$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/inspect-quality

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/inspect-quality .gemini/skills/inspect-quality && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .gemini/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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.

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality

Installs 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).

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/inspect-quality .github/skills/inspect-quality && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .github/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill inspect-quality -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers inspect-quality --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/inspect-quality .opencode/skills/inspect-quality && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "inspect-quality" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/inspect-quality into .opencode/skills/inspect-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspect-quality", 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.

Facts

Skill name: inspect-quality
GitHub stars: 256
Token cost: ~1.1k tokens
SKILL.md length: 499 words
Files: 1
Skills in repo: 39
Repo updated: Sep 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema.

Works in 5 steps: Listen and lightly clarify → Explore the codebase in the background → Assess scope: single issue or breakdown? → …
User wants to report bugs
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Mentions QA session

What it does

Inspect Quality is an agent skill from danielvm-git/bigpowers. Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, or mentions "QA session".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

User wants to report bugs
Mentions QA session

Example prompts

“QA session”
“/inspect-quality”

Workflow steps

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

Listen and lightly clarify
Explore the codebase in the background
Assess scope: single issue or breakdown?
Log to specs/bugs/registry.yaml
Continue the session

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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

Inspect Quality loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 499 words of instructions outside code blocks.

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

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 danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 499 words, ~1,117 tokens.

Download SKILL.mdSave it as .claude/skills/inspect-quality/SKILL.md (or your agent's skills folder).

name: inspect-quality
description: Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, or mentions "QA session".
model: sonnet
effort: standard

Inspect Quality

HARD GATE — HARD GATE — Quality metrics (coverage, lint, cyclomatic complexity, security scans) must be monitored. If a metric degrades, surface it as a blocker. Do NOT accept regressions.

Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and log each issue to specs/bugs/registry.yaml with a structured, durable format.

For each issue the user raises

1. Listen and lightly clarify

Let the user describe the problem in their own words. Ask at most 2–3 short clarifying questions focused on:

What they expected vs what actually happened
Steps to reproduce (if not obvious)
Whether it's consistent or intermittent

Do NOT over-interview. If the description is clear enough to log, move on.

2. Explore the codebase in the background

Kick off an Agent (subagent_type=Explore) to understand the relevant area. The goal is NOT to find a fix — it's to:

Learn the domain language used in that area (check specs/UBIQUITOUS_LANGUAGE_LATEST.md if present)
Understand what the feature is supposed to do
Identify the user-facing behavior boundary

3. Assess scope: single issue or breakdown?

Break down when:

The fix spans multiple independent areas
There are clearly separable concerns that could be worked on in parallel
The user describes something with multiple distinct failure modes

Keep as a single issue when:

It's one behavior that's wrong in one place
The symptoms are all caused by the same root behavior

4. Log to specs/bugs/registry.yaml

Append the issue to specs/bugs/registry.yaml. Create the specs/bugs/ directory if it doesn't exist.

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

registry.yaml format

The file maintains a Markdown table with the following columns (derived from structured audit practice):

Field	Description
`bug_id`	`BUG-YYYY-MM-DDTHHMMSS`
`date`	`YYYY-MM-DD`
`severity`	`critical` / `high` / `medium` / `low`
`priority`	`p0` / `p1` / `p2` / `p3`
`scope`	kebab-case area (e.g. `auth`, `checkout`)
`what_happened`	actual behavior (user-facing terms)
`what_expected`	expected behavior
`steps_to_reproduce`	numbered steps
`root_cause`	one-line hypothesis
`files_changed`	filled in after fix
`approach`	filled in after fix
`risk_level`	`low` / `medium` / `high`
`new_tests`	count (filled in after fix)
`type_check`	`pass` / `fail` (filled in after fix)
`lint`	`pass` / `fail` (filled in after fix)
`commit_type`	`fix` / `fix!` / `feat` (filled in after fix)
`release_type`	`patch` / `minor` / `major` (filled in after fix)
`commit_message`	Conventional Commits message (filled in after fix)
`follow_ups`	semicolon-separated follow-up items
`file`	path to detailed `specs/bugs/BUG-*.md` (filled in by investigate-bug)
`status`	`open` / `in-progress` / `fixed` / `wont-fix`

When a bug is fixed (via validate-fix), update the relevant row with the resolution fields.

Issue body (for context below the table)

For each bug, also append a detail section:

markdown

### BUG-YYYY-MM-DDTHHMMSS: [short title]

**What happened:** [actual behavior, plain language]
**What I expected:** [expected behavior]
**Steps to reproduce:**
1. [Step 1]
2. [Step 2]

**Additional context:** [domain-language observations, no file paths]

Rules for all entries

bug_id uses full timestamp: BUG-YYYY-MM-DDTHHMMSS — matches the individual bug file name in specs/bugs/
No file paths or line numbers — these go stale
Use the project's domain language (check specs/UBIQUITOUS_LANGUAGE_LATEST.md if it exists)
Describe behaviors, not code — "the sync service fails to apply the patch" not "applyPatch() throws"
Reproduction steps are mandatory — if you can't determine them, ask the user

5. Continue the session

After logging, ask: "Next issue, or are we done?" Keep going until the user says done. Each issue is independent — don't batch them.

Files

Just SKILL.md in skills/inspect-quality of danielvm-git/bigpowers.

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Inspect Quality 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.

Inspect Quality compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Inspect Quality this skilldanielvm-git/bigpowers	256	—	~1.1k	Automated safety check: Pass	MIT	16 days ago
Mole Bug Patternstw93/Mole	69k	—	~2k	Automated safety check: Pass	GPL-3.0	yesterday
Add Bugremotion-dev/remotion	62k	—	~215	Automated safety check: Pass	Custom licence	today
Bugccch1mneyyy/dsh-TUI	4.1k	—	~342	Automated safety check: Pass	MIT	today
Bug Bountysickn33/agentic-awesome-skills	47k	1 repos	~5k	Automated safety check: Notes	MIT	yesterday
Remotion Interactivityremotion-dev/remotion	62k	5 repos	~4.7k	Automated safety check: Pass	Custom licence	today

Similar skills

Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
69k GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Add Bug
remotion-dev/remotion
Official
Add a new Remotion bug entry to packages/bugs/api/[v].ts. An agent skill from remotion-dev/remotion.
62k GitHub stars~215 tokensUpdated today
Media & CreativeAuto-check passed
Bug
ccch1mneyyy/dsh-TUI
Turn a reported defect into an actionable bug report or issue draft.
4.1k GitHub stars~342 tokensUpdated today
Testing & QAAuto-check passed
Bug Bounty
sickn33/agentic-awesome-skills
Complete bug bounty workflow
47k GitHub starsUsed in 1 repo~5k tokens
SecurityAuto-check: notes
Remotion Interactivity
remotion-dev/remotion
Official
Structure Remotion markup for interactivity. An agent skill from remotion-dev/remotion.
62k GitHub starsUsed in 5 repos~4.7k tokens
Media & CreativeAuto-check passed
Add Webcodecs Bug
remotion-dev/remotion
Official
Add a browser WebCodecs bug to the Remotion Mediabunny WebCodecs bugs docs page.
62k GitHub stars~411 tokensUpdated today
Media & CreativeAuto-check passed

Questions about Inspect Quality

What does Inspect Quality do?

Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema. Inspect Quality is an agent skill from danielvm-git/bigpowers.yaml with a structured audit schema.

When should I use Inspect Quality?

Inspect Quality fits situations like: user wants to report bugs; mentions QA session.

How do I install Inspect Quality in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill inspect-quality -a claude-code`. Or copy the skill folder (skills/inspect-quality in danielvm-git/bigpowers) into .claude/skills/inspect-quality in your project. Claude Code loads it when a task matches its description.

How do I install Inspect Quality in Codex?

Run `npx skills add danielvm-git/bigpowers --skill inspect-quality -a codex`. Or copy the skill folder (skills/inspect-quality in danielvm-git/bigpowers) into .agents/skills/inspect-quality in your project. Codex loads it when a task matches its description.

Can I use Inspect Quality 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 danielvm-git/bigpowers --skill inspect-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inspect-quality, .gemini/skills/inspect-quality, .github/skills/inspect-quality and .opencode/skills/inspect-quality in your project.

What does Inspect Quality need to run?

SKILL.md names no scripts, command-line tools or credentials: Inspect Quality is instructions for the agent only.

Does Inspect Quality 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 Inspect Quality 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 Inspect Quality use?

Inspect Quality 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 Inspect Quality use?

About 1.1k tokens (SKILL.md is roughly 4.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 Inspect Quality?

Skills that share tags, products or a category with Inspect Quality: Mole Bug Patterns (tw93/Mole, 69k stars), Add Bug (remotion-dev/remotion, 62k stars), Bug (ccch1mneyyy/dsh-TUI, 4.1k stars) and Bug Bounty (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inspect Quality?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

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

Install Inspect Quality

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Inspect Quality

For each issue the user raises

1. Listen and lightly clarify

2. Explore the codebase in the background

3. Assess scope: single issue or breakdown?

4. Log to specs/bugs/registry.yaml

registry.yaml format

Issue body (for context below the table)

Rules for all entries

5. Continue the session

Files

Compare with similar skills

Similar skills

More from danielvm-git/bigpowers

Questions about Inspect Quality