Menu

Individual skill

explain-decision

Fetch the full reasoning behind an AxonFlow policy decision — matched policies, risk level, override availability, recent hit count

plugins/getaxonflow/axonflow-codex-plugin/skills/explain-decision/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use this skill when a user asks "why was that blocked?", "what policy fired?", or wants the context behind an allow/deny before retrying or requesting an override.

Call the `explain_decision` MCP tool with the `decision_id` returned in the original policy-check response (e.g. `decision_id` on a `check_policy` response or in the deny block reason).

The response includes:

- `policy_matches[]` — every matched policy with `policy_id`, `policy_name`, `risk_level`, and `allow_override`
- `decision` — `"allow"` or `"deny"`
- `reason` — human-readable summary
- `risk_level` — `critical`, `high`, `medium`, `low`
- `override_available` — whether the caller can request a session override
- `historical_hit_count_session` — how often this exact decision_id pattern has fired in the rolling 24h window

Present the result as a short summary: which policy fired, the risk level, whether an override is available, and (if so) suggest the user invoke `create-override` with a justification.