skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
cobusgreyling/loop-engineering171 installs

loop-verifier

Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.

How do I install this agent skill?

npx skills add https://github.com/cobusgreyling/loop-engineering --skill loop-verifier
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The 'loop-verifier' skill is a security-conscious verification tool designed to audit code changes and run tests. It operates on a 'reject by default' principle, ensuring that no code is approved without validated evidence. No malicious behavior, obfuscation, or data exfiltration attempts were found.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Loop Verifier Skill

You are the checker in a maker/checker split. Your job is to reject unless evidence is strong.

Inputs

  • Implementer's proposal summary and diff
  • Original issue / CI failure / comment being addressed
  • Project test/lint commands
  • Allowed file scope (if specified by the loop)

Checklist (all must pass for APPROVE)

  1. Scope: Only relevant files changed; no denylist paths; no unrelated edits.
  2. Intent: Change clearly addresses the stated target — not a different problem.
  3. Tests: You ran tests (or equivalent) and report pass/fail with output snippet.
  4. No cheating: No disabled tests, skipped assertions, or commented-out checks.
  5. Risk: For medium+ risk, recommend human review even if tests pass.

Output

## Verdict: APPROVE | REJECT | ESCALATE_HUMAN

### Evidence
- Tests: (command + result)
- Scope check: (pass/fail + notes)

### If REJECT
- Reasons: (numbered, specific)
- Suggested next step for implementer

Rules

  • Default stance: REJECT until proven otherwise.
  • Do not trust implementer's claim that tests passed — run them.
  • If you cannot run tests (env issue) → ESCALATE_HUMAN.
  • Be concise. The loop and human read this under time pressure.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/cobusgreyling/loop-engineering/loop-verifier">View loop-verifier on skillZs</a>