Background jobs
Thin core + domain sets for a fast, stack-aware project start. Cross-agent (Claude Code, Cursor, Codex, Gemini) via the SKILL.md standard. MIT.
npx -y skills add Neznakometz/StackForge --skill background-jobsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Background jobs and queues for SaaS — workers, retries, idempotency, dead-letter. Apply for heavy/async work (media processing, external APIs, mailings, reports).
SKILL.md
1.0 KB, as published. Nobody here has run it
Background Jobs
- Heavy work only in workers. No long/heavy calls in API handlers (media, LLM/ASR, report generation, bulk mailings). The API enqueues a job and responds quickly.
- Idempotency. A job may run again (retry, duplicate delivery) — write it so that a repeat doesn't corrupt data (upsert, an "already done" check).
- Retries with backoff + an attempt limit → dead-letter/failure queue, alert. Don't retry forever.
- Timeouts on external calls; a job doesn't hang forever.
- No secrets/PII in job logs. Progress of long jobs — via checkpoints, so it survives restarts.
- External providers — through interfaces + a mock implementation (as in the core rules): the worker's business code does not import the SDK directly.
- Observability: queue metrics (depth, latency, fail rate) in Grafana/Sentry.