Record a skill deviation with OrgX so it feeds tomorrow's Daily Brief. Use whenever an OrgX skill fires locally on a file edit, commit, PR, chat turn, or task output.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill orgx-deviation-reporting --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Orgx Deviation Reporting?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-orgx-deviation-reporting)More formats (shields.io, HTML) on the badges page.
---
name: orgx-deviation-reporting
description: "Record a skill deviation with OrgX so it feeds tomorrow's Daily Brief. Use whenever an OrgX skill fires locally on a file edit, commit, PR, chat turn, or task output."
allowed-tools: "mcp__orgx__*"
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/useorgx/orgx-codex-plugin/skills/orgx-deviation-reporting/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/useorgx/orgx-codex-plugin/skills/orgx-deviation-reporting/SKILL.md
---
# OrgX — skill deviation reporting
Every time an OrgX skill catches a deviation during your work, record it
with OrgX so the evidence shows up in tomorrow's Daily Brief and drives
the confidence trajectory for that skill.
## When to record
You should record a deviation when:
- A rule from an OrgX skill triggered on code or content you touched.
- You accepted or rejected a skill's suggestion (pass `outcome: confirmed`
or `outcome: rejected`).
- A skill surfaced a pattern in output you produced.
Do **not** record the same deviation more than once per 10-minute window —
the server dedupes on `dedupe_key` automatically; duplicate POSTs waste
tokens.
## How to record
Direct HTTP POST through the OpenClaw bridge or via `orgx.post_skill_deviation`
MCP tool:
```
POST /api/v1/skills/{skill_id}/deviations
Authorization: Bearer <OrgX API key>
Content-Type: application/json
{
"evidence_kind": "file_edit" | "commit" | "pr" | "chat_turn" | "task_output",
"evidence_ref": "<repo>#<pr>" | "<path>:<line>" | "<commit_sha>",
"summary": "<one-line description>",
"application_source": "plugin_codex",
"confidence": 0.0..1.0,
"outcome": "pending" | "confirmed" | "rejected" | "ignored",
"trigger_context": { "file_path": "...", "rule_matched": "..." },
"dedupe_key": "<sha1(skill_id | evidence_kind | evidence_ref | floor(epoch/600))>",
"captured_at": "2026-04-17T10:00:00Z"
}
```
### Computing `dedupe_key`
```ts
import { createHash } from "node:crypto";
const bucket = Math.floor(Date.now() / 1000 / 600);
const material = [skillId, evidenceKind, evidenceRef, String(bucket)].join("|");
const dedupe_key = createHash("sha1").update(material).digest("hex");
```
10-minute bucketing handles save-happy editors without losing legitimate
re-fires beyond that window.
## What happens next
Your deviation lands in `skill_deviations`. The nightly rollup feeds it
into the Daily Brief proof strip's "Deviations caught" tile + updates
the skill's confidence sparkline. Agents whose loadout doesn't include
the skill may get a cross-pollination proposal surfaced.
## Links
- Full contract: https://github.com/hopeatina/orgx/blob/main/orgx/docs/api-contracts/daily-brief-schema.md#04
- SDK reference implementation (Node): https://github.com/useorgx/openclaw-plugin/blob/main/src/deviations-sdk.ts
- Daily Brief surface: https://useorgx.com/today
---
**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/useorgx/orgx-codex-plugin/skills/orgx-deviation-reporting/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!