cross-cutting

Enforce cross-cutting rules and default-on contracts across the skill corpus.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/guyman-tr/Databricks_Knowledge --skill cross-cutting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-cutting
Source: https://github.com/guyman-tr/Databricks_Knowledge/tree/main/knowledge/skills/cross-cutting
Command: npx skills add https://github.com/guyman-tr/Databricks_Knowledge --skill cross-cutting

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures consistent application of cross-cutting rules across the entire skill corpus, reducing ambiguity and maintaining data integrity.

Core Features & Use Cases

  • Default-On Contracts: Implements default-on contracts for common data handling rules.
  • Advisory Notes: Provides advisory notes for scenarios where the default behavior should be explicitly disclosed.
  • Correctness Enforcement: Enforces correctness contracts for critical business concepts like real vs. CFD settlement.
  • Routing Disambiguation: Manages the routing of requests across different skill hubs, avoiding conflicts.

Quick Start

Load the cross-cutting hub to ensure adherence to default-on rules and to handle routing conflicts.

Frequently Asked Questions about cross-cutting

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

FAQPage Schema
How do I enforce data integrity rules across multiple data processing workflows?

Data integrity rules are enforced across workflows using default-on contracts that apply correctness checks automatically. This ensures consistent application of business logic, like real vs. CFD settlement, across your entire skill corpus without manual intervention.

What are default-on contracts in business intelligence data handling?

Default-on contracts in business intelligence data handling automatically apply common data rules across the corpus. They provide advisory notes when default behavior requires explicit disclosure, ensuring transparency and reducing ambiguity in data processing.

How do I resolve routing conflicts between different data skill hubs?

Routing conflicts between data skill hubs are resolved through routing disambiguation. This mechanism manages request routing across different hubs, avoiding conflicts and ensuring requests reach the correct processing logic.

Can I apply correctness enforcement for critical financial settlement concepts using this Skill?

Correctness enforcement for critical financial settlement concepts is supported natively. The Skill enforces correctness contracts specifically distinguishing real vs. CFD settlement, maintaining data integrity across business intelligence workflows.

What is the best way to manage routing disambiguation for data processing tasks?

Routing disambiguation for data processing tasks is managed by loading the cross-cutting hub. This centralizes routing protocols and ensures requests are directed correctly, avoiding conflicts across different skill hubs.

Do I need explicit adherence to routing protocols for cross-cutting data rules?

Explicit adherence to routing protocols and default-on rules is required for cross-cutting data rules. The system mandates strict compliance to manage routing conflicts and ensure data integrity across the skill corpus.