inherited-scope-doc-names-may-not-exist SKILL.md skillA
inherited-scope-doc-names-may-not-exist from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/inherited-scope-doc-names-may-not-exist@v1.1.2Pins v1.1.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/inherited-scope-doc-names-may-not-exist/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.2, committed Sep 17, 2026
- First version recorded
- Aug 10, 2026
- Size
- 14,182 bytes
- Repository stars
- 3
- License
- MIT
A scope or plan doc from a prior session references dataset paths, table and column names that may not exist. Verify every `project.dataset.table` and column name exists, with a fast schema probe, before a multi hour dispatch of parallel subagents or batch jobs. NOT enum VALUES.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pre-Dispatch Schema Probe ## Problem Scope docs and plan docs authored by predecessor sessions routinely cite specific BigQuery paths, table names, and column names as if they were verified facts. Often they're not — authors write from memory, from stale schema snapshots, or from hypothetical schemas that never landed. When you mechanically copy those references into 7 parallel agent prompts and fire them against production data, you burn the entire wallclock window discovering the errors one at a time, mid-run. The failure mode is costly because: 1. **Multi-agent dispatches amplify the blast radius.** 1 wrong table path × 7 agents × 10 min before each tap-out = 70 agent-minutes of wasted compute before anyone notices. 2. **Predecessor scope docs carry authority.** A scope doc that went through multiple review rounds, PR approvals, and handoff sessions LOOKS authoritative. No one re-checks the dataset paths because "surely someone already did." 3. **Plausible-wrong > obviously-wrong.** `target_2025` looks like exactly the kind of column name a training-features table would have. `analytics.predictions_daily.predictions_daily` …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/inherited-scope-doc-names-may-not-exist@sha256:506b643b8ab6023eThe line at the top of this page pins the label v1.1.2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4zmhphymofcqnkny)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 10, 2026 and Sep 17, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.2 latest | 2026-09-17 | 95260a8 | 14,182 B | A | view · diff |
| v1.1.2 | 2026-09-17 | 5d21938 | 13,647 B | A | view · diff |
| v1.1.2 | 2026-08-11 | f274e4b | 13,126 B | A | view · diff |
| v1.1.2 | 2026-08-10 | 5b6d8a2 | 13,147 B | A | view · diff |
| v1.1.2 | 2026-08-10 | a58c34c | 13,127 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14182 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4zmhphymofcqnkny GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/inherited-scope-doc-names-may-not-exist GET https://markdownregistry.com/api/v1/blob/506b643b8ab6023ee47114ea979995713ae3402062be3ad5bf03c7da06ad8e8e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.