opl-pack-capability-reviewer

Review OPL declarative packs for boundary defects and ABI mismatches.

8|5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-pack-capability-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opl-pack-capability-reviewer
Source: https://github.com/gaofeng21cn/one-person-lab/tree/main/plugins/opl-foundation-skills/skills/opl-pack-capability-reviewer
Command: npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-pack-capability-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OPL declarative packs often contain boundary defects such as mismatched capability or authority ABIs, improperly hardcoded professional methods, incorrect tool affordance definitions, and invalid surface inputs. These defects cause pack validation failures, broken generated surfaces, incorrect authority routing, and misalignment with the pack compiler, schema, and validator authority.

Core Features & Use Cases

  • Capability ABI Review: Validates that pack inputs and outputs are explicit references, required and optional fields have clear ownership and lifecycle, and generated/hosted surfaces have sufficient source references without becoming secondary truth sources.
  • Authority ABI Review: Ensures mutation, receipt, blocker, and owner-decision surfaces route to the correct authority owner, with no pack field implying unauthorized permission to write owner truth or sign acceptance.
  • Defect Classification and Fix Routing: Identifies and classifies findings into standardized gap categories (schema gap, capability ABI gap, authority ABI gap, tool affordance gap, method hardcode gap, surface input gap) and recommends the smallest corrective delta.
  • Use Case: When developing a new OPL pack for a medical research agent, use this skill to catch if the pack incorrectly hardcodes a grant review rubric instead of referencing the owner's playbook, or if a tool's side effect is misrepresented as a completed owner action instead of a requested action.

Quick Start

Use the opl-pack-capability-reviewer skill to review the latest version of the medical-research-agent declarative pack and list all identified boundary defects with recommended fixes.

Frequently Asked Questions about opl-pack-capability-reviewer

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

FAQPage Schema
How do I validate capability and authority ABI compliance in an OPL pack?

An OPL pack capability review audits declarative packs for boundary defects, capability and authority ABI mismatches, tool affordance errors, and improper hardcoding of professional methods. It ensures pack contracts adhere to compiler, schema, and validator authority boundaries.

What is an OPL pack authority ABI mismatch?

An OPL pack authority ABI mismatch occurs when mutation, receipt, blocker, or owner-decision surfaces route to the incorrect authority owner. This defect is identified when a pack field implies unauthorized permission to write owner truth or sign acceptance.

Why does my OPL pack validation fail with tool affordance errors?

OPL pack validation fails with tool affordance errors when side effects are misrepresented as completed owner actions instead of requested actions. The review classifies these as tool affordance gaps and recommends the minimal corrective delta.

Can I use this review to catch hardcoded professional methods in declarative packs?

Yes, you can use the review to catch hardcoded professional methods in declarative packs. It identifies when a pack incorrectly hardcodes a professional rubric instead of referencing the owner's playbook, classifying this as a method hardcode gap.

What are the standardized gap categories for OPL pack boundary defects?

The standardized gap categories for OPL pack boundary defects are schema gap, capability ABI gap, authority ABI gap, tool affordance gap, method hardcode gap, and surface input gap. Each finding receives a recommended minimal corrective delta.

When do I need to run an OPL pack boundary review?

You need to run an OPL pack boundary review during OPL pack development, delta review, and validation workflows. It is required for capability design, authority routing, surface input definition, and ensuring alignment with the pack compiler.