What problem does it solve?
When handing off OPL Connect connector receipt candidates to owning programs, missing evidence, unclassified gaps, or overclaimed authority can lead to invalid domain truth, failed integrations, or incorrect readiness declarations. This Skill eliminates that risk by performing a strict refs-only audit of receipt candidates before owner consumption.
Core Features & Use Cases
- Refs-Only Audit: Validates receipt candidates against source references, provider identity, request/result scope, error records, no-authority flags, and freshness signals without treating the receipt as ground truth.
- Structured Gap Classification: Categorizes identified issues into 8 distinct classes (including registry_gap, access_gap, authority_overclaim, and no_issue_found) for clear, actionable reporting.
- Minimal Route Recommendation: Suggests the smallest appropriate fix path, such as a Connect receipt update, provider retry, owner consumption request, or route-back for missing evidence.
- Use Case: For example, if a connector receipt candidate hides failed provider records inside a successful summary, this Skill flags the failed_provider_gap and routes it back to Connect for correction before the owner consumes the invalid receipt.
Quick Start
Use the opl-connect-connector-receipt-auditor skill to audit the connector receipt candidate for your OPL Connect data source before passing it to the owning program for consumption.
