loop-inspector

Score agent loops against a verifiable contract and gap checklist.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-inspector
Source: https://github.com/SollanSystems/loop-engineer/tree/main/skills/loop-inspector
Command: npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you evaluate an existing agent loop or harness and determine whether it is actually robust, verifiable, and safe against false completion claims.

Core Features & Use Cases

  • Gap Scoring: Reads a foreign loop directory in a read-only way and produces a scored report against the prime-directive checklist.
  • Verification Audit: Checks for verifiable success criteria, independent verification, approval gates, terminal-state coverage, and false-completion defenses.
  • Use Case: Use it when you inherit a harness, want to compare two loop designs, or need a final audit before trusting a long-running agent workflow.

Quick Start

Ask the skill to inspect the target loop directory and return a scored gap report with the missing defenses clearly listed.

Frequently Asked Questions about loop-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit an agent loop for false completion claims?

You can audit an agent loop for false completion by scoring it against a verifiable contract and gap checklist. This read-only inspection evaluates terminal-state coverage, approval gates, and false-completion defenses to ensure the harness only reports success when independently verified.

What is gap analysis for agent loop harnesses?

Gap analysis for agent loop harnesses is a read-only inspection that scores an existing loop directory against a prime-directive checklist. It verifies independent verification criteria, terminal-state coverage, and false-completion defenses to determine if a long-running workflow is robust and safe to adopt.

How do I check terminal-state coverage in a third-party agent harness?

You check terminal-state coverage in a third-party agent harness by performing a read-only inspection of named contract files. The audit verifies approval gates and false-completion defenses, producing a scored gap report that clearly lists any missing terminal states.

Does agent loop verification require modifying the existing harness code?

Agent loop verification does not require modifying existing harness code. The inspection is strictly read-only, reviewing named contract files, approval gates, and terminal-state coverage against a gap checklist without altering the inherited loop directory.

When do I need to run a verification audit on an inherited agent workflow?

You need to run a verification audit on an inherited agent workflow before adoption to ensure it is robust and safe. Run the gap analysis when inheriting a harness, comparing loop designs, or doing a final review of long-running agent workflows to catch false-completion vulnerabilities.