
from dotfiles9
Safety-focused workflow for local dbt development that prevents accidental use of production BigQuery schemas by redirecting schemas and enforcing pre-commit ch
This skill provides a safety-oriented compatibility trigger and runbook for local dbt work that must avoid touching production BigQuery schemas. It guides the agent to apply temporary schema overrides, run focused checks, and follow preserved guidance in the repository's reference document. The goal is to enable safe, minimal-scoped changes while preventing accidental production writes or broad data-platform actions.
Use this skill when a user requests dbt or BigQuery changes that should be isolated from production — for example, spinning up local testing schemas, redirecting queries to a sandbox dataset, running pre-commit removal checks, or verifying schema migrations in a safe environment. Do NOT use it for broad data-platform work; prefer the repository-level data-platform skill in those cases.
skills/data-platform/references/restricted-bigquery-dbt.md which contains the durable implementation notes.skills/data-platform/references/restricted-bigquery-dbt.md (detailed runbook and checks).{}
Skill listed as 'Restricted BigQuery/dbt Environment' — a safety-focused workflow for local dbt development preventing accidental production BigQuery usage. However, the SKILL.md content is completely missing (null in DB, 404 on GitHub) and no scripts were bundled. Cannot evaluate substance; the skill appears to have been deleted or moved from the source repo.
Skill body is null/empty and source URL returns 404. The short_description mentions schema redirection and pre-commit checks, which is a reasonable safety concept for dbt/BigQuery, but there is zero verifiable content. Scored security at 65 only because there's nothing malicious visible — but also nothing to audit. Code quality and architecture are at floor because there is no content. Usefulness is null because no content exists to evaluate. Recommend marking this skill as broken/unavailable.