agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/ai-audit/SKILL.md

ai-audit

Skill4 starsChanged 6 days agoMITView on GitHub

Audits AI/ML/LLM components: benchmarks, leakage, calibration, explainability, bias, red-team, confidentiality, monitoring.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 27
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 29
  3. Distinctive:

    Check data splits for leakage and benchmark fairness

    line 49
  4. Distinctive:

    Check calibration, uncertainty and stability across seeds, windows and versions

    line 51
  5. Distinctive:

    After scope: confirm depth and benchmarks

    line 58
  6. Distinctive:

    Before the verdict: review conditions and owners

    line 59
  7. Distinctive:

    Every finding cites evidence and has an owner

    line 74

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated from .claude/skills/ai-audit/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/ai-audit — AI Audit

Category: Validation & QA · Primary agent: model-risk-governance-specialist

Audits AI/ML/LLM components: benchmarks, leakage, calibration, explainability, bias, red-team, confidentiality, monitoring.

Arguments: whatever the user wrote after the command name.

Purpose

Audit an AI, machine-learning or LLM component before it is used in analysis or advice: whether its evaluation is honest (no leakage, fair benchmarks), whether its uncertainty is calibrated and stable, whether what it learned makes economic sense, whether it performs fairly across country groups, whether it resists red-team attacks, and whether confidentiality and human oversight are in place. The output is a verdict that can block release.

Use it when any AI component (forecaster, classifier, solver, RL policy, LLM pipeline, RAG system) is about to be used in production or published work.

Do not use it when the component is a traditional econometric or structural model (/validate-model).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Experiment log
    • Model code
    • Evaluation card If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • model-risk-governance-specialist — primary agent; coordinates the work and integrates results
  • ai-ethics-fairness-specialist — Reviews AI ethics and fairness
  • llm-red-team-specialist — Red-teams LLM systems
  • interpretable-ml-specialist — Makes AI models explainable
  • model-validation-specialist — Performs independent model validation

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Key design decisions (present options, let the user choose)

DecisionTypical optionsWhat it changes
Depthlight review, full auditEffort and assurance
Benchmarkssimple econometric models, previous versionBar for added value
Fairness groupscountry groups, income levels, regionsDisaggregated results
LLM testsfactuality sets, injection, leakage, version regressionSecurity coverage

Workflow

  1. Check data splits for leakage and benchmark fairness
    • Time-aware splits; preprocessing fitted on training data only; benchmarks given equal tuning effort
  2. Check calibration, uncertainty and stability across seeds, windows and versions
  3. Review explainability and economic plausibility of learned relationships
    • Flag counterintuitive relationships for economic review
  4. Review bias by country group and income level; for LLMs run the red-team harness
  5. Review confidentiality and human-oversight design; define monitoring

Checkpoints with the user

  • After scope: confirm depth and benchmarks
  • Before the verdict: review conditions and owners

Common pitfalls

  • Accepting reported scores without rerunning
  • Benchmarks tuned less carefully than the AI model
  • Average performance hiding failures for some groups
  • Oversight that exists only on paper

Output

validation/<model>/ai-audit.md

The audit report covers leakage, benchmarks, calibration, stability, plausibility, fairness, red-team results, confidentiality and oversight, with findings, conditions, owners and the verdict.

Gate / verdict

  • Verdict: PASS / PASS WITH CONDITIONS / FAIL; failures block release
  • Every finding cites evidence and has an owner

Suggested next steps

  • /validate-model
  • /model-risk-review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.