kilo-org/dataplex-and-bigquery-governance
skills/dataplex-and-bigquery-governance/SKILL.md
Guides agents through GCP-native data governance workflows with Dataplex and BigQuery. Use when designing lakes, zones, policy tags, metadata quality, lineage, discovery, and governed publishing across Cloud Storage, BigQuery, Dataflow, Dataproc, and Google Cloud analytics platforms.
$ install --global
skillsauthnpx skillsauth add kilo-org/kilo-marketplace dataplex-and-bigquery-governanceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 27, 2026, 6:49 AM113.3s1 file scanned
SKILL.md
- name:
- dataplex-and-bigquery-governance
- description:
- >-
- category:
- data
- repository:
- https://github.com/vaquarkhan/data-engineering-agent-skills
- path:
- skills/dataplex-and-bigquery-governance
- license_path:
- LICENSE
- commit:
- 421ef57e8d42c464b29339193c18dd5bd2946bc2
Dataplex And BigQuery Governance
Overview
Use this skill when governance on GCP is centered on Dataplex, BigQuery, and related Google Cloud metadata controls. It helps agents define governance zones, policy-tag boundaries, lineage expectations, and trusted publishing patterns for warehouse and lake platforms.
When to Use
- designing
Dataplexlakes, zones, or governance domains - defining
BigQuerypolicy tags and governed publish boundaries - improving metadata quality, lineage, and discovery on
GCP - aligning warehouse and lake governance across
Cloud Storage,BigQuery,Dataflow, andDataproc - making governed analytics delivery work with regional or regulated-data controls
Do not treat BigQuery governance as only a permissions problem. Trusted publishing also needs metadata, ownership, and policy boundaries.
Workflow
-
Define the governance boundary. Decide:
- lakes and zones
- datasets and domains
- producer versus consumer boundaries
- ownership expectations
-
Define metadata and policy controls. Include:
- policy tags
- classifications
- lineage coverage
- discovery metadata
- trusted versus exploratory asset signaling
-
Align lake and warehouse governance. Make explicit how
Cloud Storage,BigQuery, and processing services fit the same control model. -
Design governed publish behavior. Require:
- clear serving boundaries
- ownership visibility
- release or validation evidence where needed
- rules for schema and policy change
-
Validate day-2 operations. Review whether onboarding, schema evolution, and new domains remain manageable under the governance model.
Common Rationalizations
| Rationalization | Reality | | --- | --- | | "Policy tags are the whole governance design." | Tags help, but they do not replace ownership, zone design, trusted publishing, or metadata quality. | | "Dataplex is only for lake governance." | Many teams need a joined governance model across storage, warehouse, and processing surfaces. | | "Discovery will happen automatically once assets are scanned." | Useful discovery requires curated metadata and trust signals. |
Red Flags
- lake, dataset, and domain boundaries are inconsistent
- policy tags exist without ownership or publish context
- warehouse and lake governance behave differently with no clear rule
- certification or trusted-asset behavior is missing
- schema and policy changes are operationally unclear
Verification
- [ ] Governance boundaries are explicit across lake and warehouse surfaces
- [ ] Policy tags, metadata, and lineage expectations are defined
- [ ] Publish behavior is governed and reviewable
- [ ] Ownership and discovery expectations are visible
- [ ] Day-2 operations fit the governance design
Related Skills
kilo-org/oracle-database
development
VerifiedTrustedCommunity
Oracle Database guidance for SQL, PL/SQL, SQLcl, ORDS, administration, app development, performance, security, migrations, and agent-safe database workflows. Use when the user asks to write, edit, rewrite, review, format, debug, tune, or explain SQL; create or refactor PL/SQL; use SQLcl, Liquibase, ORDS, JDBC, node-oracledb, Python, Java, .NET, or database frameworks; troubleshoot queries, sessions, locks, waits, indexes, optimizer plans, AWR, ASH, migrations, schemas, users, roles, privileges, backup, recovery, Data Guard, RAC, multitenant, containers, monitoring, auditing, encryption, VPD, or safe agent database operations.
161SKILL.mdUpdated Jul 21, 2026
kilo-org/oleander-iceberg-catalog
documentation
VerifiedTrustedCommunity
Patterns for reading and writing oleander Iceberg catalog tables in Spark jobs, including naming conventions, write modes, and catalog hierarchy.
161SKILL.mdUpdated Jul 21, 2026
kilo-org/okta-identity-integration-patterns
data-ai
VerifiedTrustedCommunity
Integrate Okta for enterprise identity workflows including OIDC login, group claims, and policy-based access controls. Use when implementing workforce or B2B identity scenarios.
161SKILL.mdUpdated Jul 21, 2026
kilo-org/nifi-flow-layout
documentation
VerifiedTrustedCommunity
Use when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.
161SKILL.mdUpdated Jul 21, 2026