.claude/skills/qubrics-email-for-agentsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Give OpenClaw agents a Qubrics inbox to receive, triage, route, reply to, and send email with owner approval and scoped credentials.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/qubrics-email-for-agentsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/qubrics-email-for-agentsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/qubrics-email-for-agentsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @roshanjonah/qubrics-email-for-agentsclawhub inspect @roshanjonah/qubrics-email-for-agents --version 2.0.4This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:c502b6d3874b3e4c7f0c8aab5e6002709c6d71f0ccf7fe07f335313525d13461skill-card.mdSKILL.mdVersion 2.0.4 clarifies setup, identity checks, and safe routing for agent email workflows. - Requires isolated CLI processes with inherited credentials cleared, and identity verification before mailbox access or task handoff. - Clarifies routes for self-registration, existing OAuth accounts, owner-managed provisioning, mailbox tasks, and attachment workflows. - Reinforces protections for secrets and untrusted email content, and requires user confirmation before sending. - Specifies that approval-bound drafts must retain their stable ID and revision; only the approved revision may be sent.