eeg-audit

Validate EEG analysis claims across plan, stats, and report artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dengzhe-hou/auto-eeg-analysis --skill eeg-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eeg-audit
Source: https://github.com/dengzhe-hou/auto-eeg-analysis/tree/main/skills/eeg-audit
Command: npx skills add https://github.com/dengzhe-hou/auto-eeg-analysis --skill eeg-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__codex__codex, mcp__codex__codex-reply.

What problem does it solve?

It prevents incorrect EEG claims from slipping into a report by independently re-checking plan traceability, statistical reporting, figure integrity, and COBIDAS-MEEG method completeness.

Core Features & Use Cases

  • Cross-file numeric consistency auditing: Confirms p-values, effect sizes, permutation counts, seeds, and tails match across the analysis plan, stats JSON outputs, and the report text.
  • Integrity guardrails via deterministic checks: Runs an mtime verification to detect post-hoc edits of the frozen analysis plan relative to stats generation.
  • External “hostile” methods review: Hands the bundled evidence to an external LLM reviewer (Codex MCP, GPT-5.4 xhigh by default) with no prior context to produce per-claim verdicts and action items.

Quick Start

Run the eeg-audit skill against your project directory after the analysis stages finish so it can generate an audit verdict and actionable fixes in audit-stage/.

Frequently Asked Questions about eeg-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit EEG analysis claims for p-value and effect size consistency?

You validate EEG claims by cross-checking analysis-plan traceability, stats JSON numeric integrity, and report or figure consistency. This process detects post-hoc edits and confirms p-values, effect sizes, and permutation counts match across all pipeline artifact directories.

What is COBIDAS-MEEG compliance and how do I check it in my report?

COBIDAS-MEEG compliance ensures method completeness in EEG research reports. You check it by auditing your end-to-end EEG pipeline outputs, which generates a structured JSON output contract highlighting compliance gaps and missing methodological details.

Can I use an external LLM reviewer to verify statistical reporting in EEG pipelines?

Yes, you can invoke an external Codex MCP reviewer with no prior context to perform a hostile methods review. This independent LLM reviewer evaluates your bundled audit inputs and generates per-claim verdicts alongside action items for statistical validation.

How do I detect post-hoc edits in my frozen EEG analysis plan?

You detect post-hoc edits by running deterministic mtime integrity checks against your frozen analysis plan and stats generation. This guardrail verifies that the analysis plan was not modified after statistical outputs were generated, ensuring reproducibility.

Does the EEG audit skill work with permutation counts and seeds from stats JSON files?

Yes, the skill validates permutation counts, seeds, and tails by cross-referencing them across the analysis plan, stats JSON outputs, and report text. This ensures cross-file numeric consistency and verifies that reported statistical parameters match the actual computed values.

When should I run an EEG statistical validation audit on my project directory?

You should run the audit after your end-to-end EEG analysis stages finish and claims are generated. Running it at this point ensures the tool can effectively cross-check plan traceability, stats JSON integrity, and report consistency, producing actionable fixes in the audit-stage directory.