inbox SKILL.md skillA
inbox from gricha/inbox is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gricha/inbox/inbox@git:20261117.89ffc7ePins git:20261117.89ffc7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gricha/inbox
- Path
skills/inbox/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261117.89ffc7e, committed Nov 17, 2026
- First version recorded
- Nov 16, 2026
- Size
- 36,035 bytes
- Repository stars
- 53
- License
- none declared
Use when the user mentions Inbox (their GitHub desk app for reviews) or their desk, asks what needs them on GitHub, what to review next, why a PR or issue is in their queue (or isn't), or wants to add a PR or issue to their review or desk, snooze, mute, clear or re-sort their review work, change their rules (or how much one counts), urgency criteria or automations, hand off a review, get a quick brief on a PR, write a review document, or run as their coordinator getting the PRs they handed off…
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
# Inbox
Inbox is a desktop app on the user's machine that turns their GitHub review load (PRs to review, their own PRs, issues) into one queue.
Rules sort each item into a bucket, the user's agent (the judge) weighs every rule that matches and makes the call, and urgency criteria order what's left into Urgent, Standard and FYI.
## The desk in brief
- **Pages.** The Inbox (sections Urgent, Standard, FYI; agents' questions and sessions that need the user lead Urgent). Blocked: the user's own PRs that wait on another PR or on reviewers. Merging: their PRs handed off to the coordinator, never on the Inbox. The Archive: done, resolved, snoozed, muted and hidden items.
- **Rules.** `~/.inbox/config.toml` holds boards (GitHub searches) with ordered rules; the first rule whose `when` matches sets the bucket (`now`, `today`, `blocked`, `later`, `fyi`, `hide`) and a `why`. A plugin's built-in rules come after the board's own. An item on several boards shows once, at its most urgent placement. Caps (`caps = { now = 3 }`) push overflow down a bucket. Flags: `hard` (a floor: never sorted below its bucket), `final` (the judge never re-sorts it), `nocap`, and `weight` (0 to 10, 5 unless set…
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jbtpdz5wwu4cuvk2/0b1a54a65249524a75084617380543b9ac359930b319ecd41f495e034358192e.json
Then /plugin install inbox@markdownregistry-jbtpdz5wwu4cuvk2 in Claude Code. It installs git:20261117.89ffc7e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gricha/inbox/inbox@sha256:0b1a54a65249524aThe line at the top of this page pins the label git:20261117.89ffc7e, 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_jbtpdz5wwu4cuvk2)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in gricha/inbox/inbox since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of inbox from somewhere else? Ask it: where did my inbox come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 16, 2026 and Nov 17, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.89ffc7e latest | 2026-11-17 | 89ffc7e | 36,035 B | A | view · diff |
| git:20261117.ed86cf8 | 2026-11-17 | ed86cf8 | 36,033 B | A | view · diff |
| git:20261117.29116cd | 2026-11-17 | 29116cd | 35,923 B | A | view · diff |
| git:20261116.ffa832f | 2026-11-16 | ffa832f | 35,875 B | A | view · diff |
| git:20261116.6ec693a | 2026-11-16 | 6ec693a | 34,793 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/inbox/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (36035 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
gricha/inbox · 53 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jbtpdz5wwu4cuvk2 GET https://markdownregistry.com/api/v1/resolve?ref=gricha/inbox/inbox GET https://markdownregistry.com/api/v1/blob/0b1a54a65249524a75084617380543b9ac359930b319ecd41f495e034358192e
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.