scheduled-fallback-check-cites-stale-task-id SKILL.md skillA
scheduled-fallback-check-cites-stale-task-id 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/scheduled-fallback-check-cites-stale-task-id@v1.0.0Pins v1.0.0 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/scheduled-fallback-check-cites-stale-task-id/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 17, 2026
- Size
- 11,615 bytes
- Repository stars
- 3
- License
- MIT
Don't act on a background-task ID embedded in an incoming check-in message (a self-scheduled fallback wakeup, a peer's "did it finish?" ping, a cron reminder) without first verifying it's still the CURRENT run. Use when: (1) you dispatched a long-running background task (a local CI-equivalent gate run, a build, a deploy watcher) under task ID A; (2) while it was in flight, new work landed that required restarting the SAME class of task under a fresh ID B…
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
# Scheduled fallback check cites a stale, superseded task ID ## Problem You dispatch a long-running background task — a local gate run, a build, a deploy-verification watcher — under some task ID. Before it (or its successor) is expected to finish, a check-in message arrives asking you to look at that ID and, if it's finished green, take a consequential next step: > "Check whether the fresh gate_receipt.py run (background task `b5eomsgw3`, > output at `.../tasks/b5eomsgw3.output`) has finished. If it finished > green, publish the receipt ... then push." The trap: between when that check was WRITTEN/SCHEDULED and when it FIRES, the world moved. You found a bug, fixed it, and had to re-run the same class of task from scratch — under a brand-new task ID. The cited ID didn't update; it's a snapshot frozen at scheduling time. By firing time it may refer to a run that: - already finished (against an OLDER, now-superseded tree), or - was killed/abandoned, or - never existed under that exact ID at all (a copy/paste from an earlier turn). Acting on the cited ID at face value — reading its output, treating "exit 0" …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/scheduled-fallback-check-cites-stale-task-id@sha256:3fbc9ff89351ce96The line at the top of this page pins the label v1.0.0, 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_gmz7ozmb2cfyjxgf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 17, 2026.
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 (11615 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_gmz7ozmb2cfyjxgf GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/scheduled-fallback-check-cites-stale-task-id GET https://markdownregistry.com/api/v1/blob/3fbc9ff89351ce9639c024d5bca1a6bfffa3c7b431f1e4086c992206466eceb0
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.