dashboard-acceptance-pilot

Validate external dashboard sync workflows from source registration through reconcile.

108|27|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/diegosouzapw/omni-skills --skill dashboard-acceptance-pilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-acceptance-pilot
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/dashboard-acceptance-pilot
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill dashboard-acceptance-pilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Dashboard Acceptance Pilot provides a native intake and packaging of an upstream external-dashboard workflow, preserving provenance, a packaged support pack, and context to guide reviewers and operators through the import, review, and handoff process.

Core Features & Use Cases

  • Packages upstream workflow artifacts into a native, auditable skill shape suitable for downstream validation.
  • Includes a bundled support pack with an operator checklist, rubric, playbook, prompt template, and provenance links to enable thorough review.
  • Provides routing guidance and references to assist handoffs to stronger native capabilities when scope drifts or improvements are needed.

Quick Start

Activate the Dashboard Acceptance Pilot by loading the upstream workflow artifacts and starting with the import playbook.

Frequently Asked Questions about dashboard-acceptance-pilot

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

FAQPage Schema
How do I validate external dashboard workflows for auditable imports?

To validate external dashboard workflows for auditable imports, you package upstream artifacts into a native skill shape, verifying provenance from source registration through reconcile to ensure a fully auditable handoff.

What is dashboard provenance verification and when do I need it?

Dashboard provenance verification is the process of tracking external sync workflows from source registration through reconcile. You need it when onboarding external dashboard sources to ensure auditable imports and reviewer accountability.

How do I package upstream dashboards for reviewer handoff?

You package upstream dashboards for reviewer handoff by loading the upstream workflow artifacts and starting with the import playbook, which assembles a bundled support pack with an operator checklist, rubric, and provenance links.

Can I use this workflow to onboard external sync dashboards without dependencies?

Yes, you can onboard external sync dashboards without dependencies. The workflow operates as a standalone packaged pilot that bundles references, scripts, and assets to validate and import external sources natively.

What is the best way to handle scope drift during dashboard source onboarding?

The best way to handle scope drift during dashboard source onboarding is to follow the included routing guidance, which references stronger native capabilities to assist handoffs when scope drifts or improvements are needed.

Why does my external dashboard import lack auditable provenance links?

External dashboard imports lack auditable provenance links when upstream artifacts are not packaged using a structured workflow. Applying a packaged intake process with a reference pack and provenance links ensures auditable imports.