Agent skill · Security

xai-check

Explainability (XAI) audit for products containing AI components. Five-stage tier-scaled check: risk classification, stakeholder×question matrix, fidelity audit, system card, recourse path. Honest about what was validated functionally vs what needs user testing.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill xai-check-haabe-mycelium --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/ai-ml/xai-check-haabe-mycelium/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# XAI Check Skill Operational gate for the Explainability Theory Gate (Gate 13). Audits whether a product's AI components meet a defensible XAI bar — disclosure, decision-explanation, recourse, fidelity, system card — scaled to the AI Act risk tier. This skill is **functionally-grounded** in Doshi-Velez & Kim's (2017) sense: it operates on artifacts and configuration, not on real users with real tasks. Output explicitly distinguishes `validated_functionally` from `needs_user_testing`. The honest tag is what passes Gate 13; user-grounded validation is recommended but not blocking. ## When to Use - L3 Define→Develop or Develop→Deliver, **only when `active-stack.yml :: ai_components.detected: true`** - L4 Develop→Deliver — required when AI components reach user-affecting decisions (deny, recommend, rank, generate user-shown content) - L5 Develop→Deliver — required for any user-facing AI feature at launch - After any change to AI components, prompts, or surfaces that affect user-facing decisions - When Gate 13 is checked during `/mycelium:diamond-progress` ## Precondition: AI components detected Read `${CLAUDE_PLUGIN_ROOT}/jit-tooling/active-stack.yml` (Step 1c output of `delivery-boot

What's inside
Steps it walks through
  1. When to Use
  2. Precondition: AI components detected
  3. Workflow (5 stages)
  4. Stage 1 — Risk tier classification
  5. Stage 2 — Stakeholder × question matrix
  6. Stage 3 — Fidelity audit
  7. Stage 4 — System card check
  8. Stage 5 — Recourse path test (limited+ tiers only)
  9. Output
  10. Display to user
  11. Composition with other gates / skills
  12. What this skill does NOT do
  13. Theory citations
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the xai-check skill do?

Explainability (XAI) audit for products containing AI components. Five-stage tier-scaled check: risk classification, stakeholder×question matrix, fidelity audit, system card, recourse path. Honest about what was validated functionally vs what needs user testing.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill xai-check-haabe-mycelium --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going