background-jobs skillA
background-jobs is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Design queued and scheduled work so it survives duplicates, retries, crashes and restarts — job contract, idempotency, transactional enqueue, backoff, dead letters, leases and the ordering guarantees you actually have. Use when moving work off a request path, adding a worker or cron, or debugging a job that ran twice, never ran, ran out of order, or is stuck retrying forever. Not for in-request async concurrency, and not for stream processing topology design..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Background jobs Every queue gives you at-least-once delivery and no useful ordering. Everything else — exactly once, in order, eventually — is something you build on top, or something you are assuming and will be paged about. Design for the guarantee you have, not the one you want. ## When this fires Work is being moved out of a request path; a queue, worker, scheduler or cron entry is being added or changed; or a job misbehaved — ran twice, silently vanished, processed stale data, or filled a dead-letter queue. It does not fire for concurrency inside a single request, and not for designing a streaming topology. ## Procedure 1. **Check it belongs off the request path.** If the caller needs the result to respond, it is not a job — making it one just moves the wait somewhere the user cannot see. Enqueue work that is slow, retryable, and whose completion the caller can learn about later. 2. **Define the job contract.** Small, serializable payload. Prefer passing an identifier and re-reading current state in the worker over embedding a snapshot — with one exception: when the job must act on the values as they were at enqueue time, embed them and say why. Never …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/background-jobs@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/background-jobs@sha256:1e07371adc47ef3dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_acd3yt6l63up6oqs)
1 badge views in 30 days
Versions
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 (8126 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_acd3yt6l63up6oqs GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/background-jobs GET https://markdownregistry.com/api/v1/blob/1e07371adc47ef3d71d39e3ba3cf8ddb2cd3f9d3bb5726e4c0a04df19f0dcf4d
Your agent 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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher