Skip to content

feat(skills): add dq-job-from-data-contract skill + behavioral evals - #138

Open
BethHoffmann wants to merge 1 commit into
collibra:mainfrom
BethHoffmann:feat/dq-job-from-data-contract-skill
Open

feat(skills): add dq-job-from-data-contract skill + behavioral evals#138
BethHoffmann wants to merge 1 commit into
collibra:mainfrom
BethHoffmann:feat/dq-job-from-data-contract-skill

Conversation

@BethHoffmann

Copy link
Copy Markdown

Summary

  • Adds a new collibra/dq-job-from-data-contract skill that turns a Collibra Data Contract's manifest clauses into an enforcing Data Quality job plus tolerance-0 rules (monitors), reusing collibra/dq-rules / collibra/dq-rule-workbench for the per-rule mechanics.
  • Registers the skill in SKILLS.md and the collibra/index navigator, and cross-links it from collibra/dq-rules / collibra/dq-rule-workbench.
  • Ports the skill's test plan into chip's existing Python behavioral-eval harness as a new skill-level suite: evals/dq_job_from_data_contract/ — 5 task scenarios (full flow, existing-job reuse, verify-and-results, impossible time-slice, referential-integrity clause blocked) plus 20 trigger scenarios (10 should-trigger / 10 should-not-trigger), all graded deterministically off the tool-call transcript against a dedicated mock Collibra fixture (EMPLOYEES table + data contract). No LLM-graded rubrics, matching this repo's existing convention.
  • Every task scenario enforces dry-run only (no tool call may ever set confirm=true), since the underlying skill performs live writes in Collibra.

Known simplifications are called out in evals/dq_job_from_data_contract/README.md's "Known simplifications" section (e.g. prompts pass the fixture's data contract ID directly rather than exercising asset-search discovery, which is out of scope for this skill and already covered by collibra/discovery).

Test plan

  • go build ./...
  • go vet ./...
  • go test ./pkg/skills/...
  • python3 -m py_compile on every new eval Python file
  • YAML-parsed scenarios.yaml / trigger_scenarios.yaml and confirmed scenario counts (5 task, 20 trigger — 10/10 split)
  • Run evals/dq_job_from_data_contract/runner.py against a live model (ANTHROPIC_API_KEY) — not run as part of this PR, same as other suites in evals/

🤖 Generated with Claude Code

Adds a new collibra/dq-job-from-data-contract skill that turns a Data
Contract's manifest clauses into an enforcing DQ job and tolerance-0
rules, and ports its test plan into chip's existing Python behavioral
eval harness as a new skill-level suite (5 task scenarios + 20 trigger
scenarios covering when the skill should/shouldn't load).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@BethHoffmann
BethHoffmann requested a review from a team as a code owner September 8, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant