qubrics-email-for-agents SKILL.md skillA
qubrics-email-for-agents from sendmux/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sendmux/skills/qubrics-email-for-agents@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sendmux/skills
- Path
plugins/qubrics/skills/qubrics-email-for-agents/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0, committed Nov 10, 2026
- First version recorded
- Nov 10, 2026
- Size
- 19,566 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Use when a user wants to design or plan how an AI agent gets and uses email — giving an agent its own inbox, deciding between owner-managed vs self-registered provisioning, building a receive/triage/reply loop, sending notifications with human approval, or choosing which credential/surface to use — especially when they're unsure how to architect this, even if Qubrics isn't named. Do NOT use for a user who already knows their setup and just wants a specific low-level command, code snippet, or…
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
# Qubrics email for agents Use this skill when the user describes the agent-email problem: an AI agent needs an inbox, mailbox identity, outbound email, triage loop, reply workflow, or human approval path. Before any CLI setup, connection validation or task command, start an isolated child process with inherited `QUBRICS_API_KEY`, `SENDMUX_API_KEY`, `QUBRICS_ACCESS_TOKEN`, `SENDMUX_ACCESS_TOKEN`, `QUBRICS_PROFILE`, `SENDMUX_PROFILE`, `QUBRICS_BASE_URL` and `SENDMUX_BASE_URL` cleared. Load only the intended credential from the user's secret store; for an existing profile, leave direct credentials unset and select the intended `--profile`. Use the authorised endpoint and keep credentials out of arguments and output. This also applies when an authenticated profile is already configured and login/setup is skipped. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2in5edsto3qgvq6l/8ca44ee32dba3bd66edd2543341f79999fdcbecab19e8181466ad39ffb4365a9.json
Then /plugin install qubrics-email-for-agents@markdownregistry-2in5edsto3qgvq6l in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add sendmux/skills/qubrics-email-for-agents@sha256:8ca44ee32dba3bd6The line at the top of this page pins the label v1.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_2in5edsto3qgvq6l)
2 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 sendmux/skills/qubrics-email-for-agents 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 qubrics-email-for-agents from somewhere else? Ask it: where did my qubrics-email-for-agents 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 2 versions of this file, all committed on Nov 10, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-11-10 | 92b566d | 19,566 B | A | view · diff |
| v1.0 | 2026-11-10 | 846e49f | 19,566 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/qubrics-email-for-agents/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 (19566 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
sendmux/skills · 15 stars · license a license file GitHub does not identify · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2in5edsto3qgvq6l GET https://markdownregistry.com/api/v1/resolve?ref=sendmux/skills/qubrics-email-for-agents GET https://markdownregistry.com/api/v1/blob/8ca44ee32dba3bd66edd2543341f79999fdcbecab19e8181466ad39ffb4365a9
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.