opl-connect-source-and-skill-router

Route OPL Connect source and skill tasks while enforcing domain authority boundaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with OPL Connect to integrate external sources, connectors, or Codex Skills, it's easy to overstep domain authority boundaries, sync unnecessary full external libraries by default, or make unsubstantiated claims about external content's quality or readiness. This Skill eliminates those risks by providing a structured routing workflow that keeps domain truth with the correct owner and enforces minimal, intentional sync scope.

Core Features & Use Cases

  • Structured Request Routing: Classifies OPL Connect tasks into 6 standardized workflow types (source search, skill search, candidate inspection, single-skill sync, connector receipt debugging, refs-only review) to ensure consistent, low-risk handling.
  • Authority Boundary Enforcement: Prevents unsubstantiated claims about external content's domain truth, quality, or readiness, and ensures all candidate references are handed off to the correct domain owner for validation.
  • Use Case: If you need to add a new external research dataset to OPL Connect, use this Skill to search for candidate sources, inspect their sync scope and authority boundaries, debug any connector receipt errors, and hand the validated source reference to the research domain owner for approval without making unverified claims about the dataset's quality.

Quick Start

Use the opl-connect-source-and-skill-router skill to search for candidate external research data sources, inspect their sync scope and authority boundaries, and hand the validated source reference to the research domain owner for approval.

Frequently Asked Questions about opl-connect-source-and-skill-router

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

FAQPage Schema
How do I route OPL Connect external source tasks without overstepping domain authority boundaries?

To enforce domain authority during external source integration, use a structured routing workflow that classifies OPL Connect tasks into standardized types and prevents unsubstantiated claims about external content's domain truth, quality, or readiness.

What is the best way to inspect a candidate external source before syncing it to OPL Connect?

Inspecting a candidate external source involves evaluating its sync scope and authority boundaries, then handing the validated candidate reference to the correct domain owner for approval without making unverified claims about the dataset's quality.

How do I debug connector receipt errors marked with no-authority flags in OPL Connect?

Debugging connector receipt errors marked with no-authority flags requires routing the task through a specialized connector receipt debugging workflow that reviews metadata while preventing unsubstantiated domain truth claims from external connector outputs.

Can I sync a single external skill to OPL Connect instead of a full external library?

Yes, you can perform a single-skill sync by routing the task through a selective sync workflow, which ensures minimal-risk external resource integration by enforcing intentional, minimal sync scope rather than syncing unnecessary full external libraries by default.

When do I need to use a structured routing workflow for OPL Connect source and skill tasks?

You need structured routing when evaluating candidate external sources or skills, making single-skill sync decisions, reviewing connector metadata, or handing off validated candidate references to domain owners to ensure minimal-risk external resource integration.

Why should I avoid making unsubstantiated domain truth claims from external connector outputs?

Avoiding unsubstantiated domain truth claims prevents overstepping authority boundaries, ensuring that all candidate references from external connector outputs are handed off to the correct domain owner for validation before any integration decisions are finalized.