provenance-checker

Validate data provenance implementation across database migrations and frontend components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BruceTyndall/socelle-global --skill provenance-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provenance-checker
Source: https://github.com/BruceTyndall/socelle-global/tree/main/.agents/skills/provenance-checker
Command: npx skills add https://github.com/BruceTyndall/socelle-global --skill provenance-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all data signals in the system have proper source citations, meet freshness Service Level Agreements (SLAs), and that attribution is clearly displayed, adhering to data governance policies.

Core Features & Use Cases

  • Schema Validation: Checks for the presence of provenance-related columns in database migration scripts.
  • UI Attribution Check: Scans frontend components to ensure data sources and attributions are displayed.
  • Freshness SLA Monitoring: Identifies logic for detecting stale data or enforcing time-to-live (TTL) policies.
  • Missing Attribution Detection: Flags signals or components that render data without corresponding source information.
  • Use Case: Before deploying new features that display intelligence signals, run this skill to confirm that every signal is properly attributed and its data freshness is within acceptable limits.

Quick Start

Run a provenance check on the SOCELLE-WEB application's source code.

Frequently Asked Questions about provenance-checker

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

FAQPage Schema
How do I check data provenance and source attribution in my application?▼

To check data provenance, scan your database migrations for provenance columns and frontend components for attribution elements. This validates that every signal displays its source citation, ensuring compliance with data governance policies.

How do I verify freshness SLA compliance and detect stale data in my codebase?▼

Verify freshness SLA compliance by scanning your logic for stale data detection and time-to-live policy enforcement. This identifies whether your application properly flags or rejects data that exceeds acceptable freshness limits.

What is data provenance validation and when do I need it?▼

Data provenance validation ensures all data signals have proper source citations, meet freshness SLAs, and display attribution correctly. You need it before deploying features that render intelligence signals to adhere to data governance policies.

How do I find frontend components rendering data without source attribution?▼

Find components missing source attribution by scanning your frontend code for attribution elements. This process flags any signals or UI components that render data without corresponding source information attached.

Can I validate schema compliance for data governance in database migration scripts?▼

You can validate schema compliance by checking database migration scripts for the presence of provenance-related columns. This confirms your database schema enforces data governance requirements for source tracking.