opl-pack-admission-reviewer

Review OPL pack admission candidates for registry fit and contract compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing OPL pack admission candidates for registry fit, contract compliance, evidence coverage, and boundary clarity is time-consuming and error-prone for teams managing OPL pack registries and associated programs.

Core Features & Use Cases

  • Standardized Gap Classification: Categorizes review findings into 8 predefined gap types including registry fit gaps, contract gaps, capability ABI gaps, authority ABI gaps, evidence gaps, owner route gaps, overclaim gaps, or no issues found.
  • Actionable Route-Back Recommendations: Suggests the minimal required fix (schema adjustment, pack field correction, source reference update, owner route clarification, admission hold, or no change) for each identified gap.
  • Boundary-Compliant Operation: Functions strictly as an AI-first reviewer, never mutating registry state, creating typed blockers, signing owner receipts, or declaring pack readiness. Use Case: An OPL program owner can use this skill to quickly assess a new pack submission, identify missing evidence or unauthorized authority claims, and send a structured route-back brief to the pack owner to resolve gaps before formal admission.

Quick Start

Use the opl-pack-admission-reviewer skill to review the submitted OPL pack candidate 'clinical-research-tools-pack' against the core medical research program registry and generate a route-back brief for any identified gaps.

Frequently Asked Questions about opl-pack-admission-reviewer

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

FAQPage Schema
How do I review OPL pack admission candidates for registry fit and contract compliance?

To review OPL pack admission candidates, you need a source-only, refs-only evaluation that checks registry fit, contract compliance, capability and authority ABI alignment, and evidence coverage prior to formal admission.

What is gap classification in OPL pack admission reviews?

Gap classification in OPL pack admission reviews categorizes findings into 8 standardized types: registry fit gaps, contract gaps, capability ABI gaps, authority ABI gaps, evidence gaps, owner route gaps, overclaim gaps, or no issues found.

How do I generate route-back recommendations for OPL pack submission gaps?

You generate route-back recommendations by identifying gaps in declarative fields and boundaries, then suggesting minimal required fixes like schema adjustments, pack field corrections, or source reference updates for each classified gap.

Can an AI reviewer mutate registry state during OPL pack admission evaluation?

No, an AI reviewer for OPL pack admission must function strictly as a boundary-compliant evaluator, never mutating registry state, creating typed blockers, signing owner receipts, or declaring pack readiness.

When do I need to check authority ABI alignment for an OPL pack submission?

You need to check authority ABI alignment when evaluating new OPL pack submissions to identify unauthorized authority claims and ensure evidence coverage before generating a structured route-back brief to the pack owner.

Does OPL pack admission review work without external dependencies?

Yes, OPL pack admission review operates as a source-only, refs-only review process that classifies findings and generates actionable route-back recommendations without requiring external dependencies or mutating registry state.