hor-post-worker SKILL.md skillA
hor-post-worker from openreachtech/hora-skills-ort-renchan is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openreachtech/hora-skills-ort-renchan/hor-post-worker@git:20260922.a2004baPins git:20260922.a2004ba in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openreachtech/hora-skills-ort-renchan
- Path
kit/skills/hor-post-worker/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260922.a2004ba, committed Sep 22, 2026
- First version recorded
- Sep 5, 2026
- Size
- 14,525 bytes
- Repository stars
- 32
- License
- Apache-2.0
Implement a GraphQL post-worker: a hook that fires after a query/mutation resolver has resolved and the response has been sent, to run a side effect that is not part of the API's main processing (send a welcome email after signup, emit an audit log, invalidate a cache). Use this skill whenever the user asks to add or edit a post-worker, wants "run something after this resolver / after the response", or needs to fire-and-forget a side effect right after an API call.
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
# Post-Worker (a post-response side-effect hook) A skill for implementing `BaseGraphqlPostWorker`, a hook that runs a side effect — one that is *not* part of the API's main processing — **after** the resolver has resolved (after the response has been sent). It handles requirements of the form "after this operation, also run …" as a follow-up, without polluting the resolver itself. Deciding the placement itself (whether a post-worker is even the right choice, versus enqueuing inside the resolver) is settled in section 2.2 of `hor-execution-placement-pattern`. This skill covers "once you've decided on a post-worker, how to implement it". The implementation of the worker body you dispatch to belongs to `hor-renchan-job-bullmq`. ## Grand principle: a post-worker is a thin layer that only dispatches — the real work always lives in the worker The only things you may write in a post-worker's `onResolved()` are **the dispatch to a background worker and the branching that precedes it**. **Write no real work at all** — no email-body assembly, no external API calls, no DB updates, no heavy loops. …
Read the whole file at its exact version.
How to install
mdr add openreachtech/hora-skills-ort-renchan/hor-post-worker@sha256:8d3687a8d272fa70The line at the top of this page pins the label git:20260922.a2004ba, 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_oldhjzornem7tl3l)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 5, 2026 and Sep 22, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.a2004ba latest | 2026-09-22 | a2004ba | 14,525 B | A | view · diff |
| git:20260905.5a04969 | 2026-09-05 | 5a04969 | 14,434 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 (14525 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
openreachtech/hora-skills-ort-renchan · 32 stars · license Apache-2.0 · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oldhjzornem7tl3l GET https://markdownregistry.com/api/v1/resolve?ref=openreachtech/hora-skills-ort-renchan/hor-post-worker GET https://markdownregistry.com/api/v1/blob/8d3687a8d272fa70cf896c8b72cc49b7aee995ed9b5af450d9ce82810c2f65ea
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.