OrgX — skill deviation reporting

SkillFiles & storage

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.

Use OrgX — skill deviation reporting in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add OrgX — skill deviation reporting and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the OrgX skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

OrgX — skill deviation reportingStart free

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/useorgx/orgx-codex-plugin/skills/orgx-deviation-reporting/SKILL.md and read by ahel’s review.

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

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

Signals

GitHub stars
1k
Forks
316
Last commit
Oct 2026
Advanced
Item type
skill
Key
orgx-deviation-reporting
Source
github.com/hashgraph-online/awesome-codex-plugins