How do I install the Induction Audit skill?

Run npx skillmds@latest add jmagly-ai-writing-guide/induction-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Induction Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Induction Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Induction Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Induction Audit?

jmagly (@jmagly-ai-writing-guide) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Induction Audit by jmagly-ai-writing-guide

Name: Induction Audit
Rating: 4.2 (5 reviews)
Author: jmagly

Induction Audit

Audit research-corpus induction quality — depth bands (stub/compact/good/full/deep), structural integrity (analysis doc + sidecar + PDF, honoring audit-exclude conventions), and per-source-type required sections (a blog isn't flagged for missing Benchmark Results). Plus additive frontmatter backfill for legacy docs. Runs via `aiwg corpus induction-audit` / `aiwg corpus frontmatter-backfill`.

jmagly Updated Sep 10, 2026

File contents

Induction Audit & Frontmatter Backfill

Quality + depth audit for inducted references, and an additive frontmatter backfill for legacy analysis docs. The audit is source-type-aware: required sections come from the source-type registry (source-types skill / #1509), so a blog is checked for "Practical Relevance" and a repo for "Architecture", not for "Benchmark Results".

How to run

# Audit a REF range
aiwg corpus induction-audit --start 599 --end 635

# Audit one REF
aiwg corpus induction-audit --ref REF-394

# Audit the whole corpus
aiwg corpus induction-audit

# Backfill minimal frontmatter (ref_id/title/year/pdf_hash) into legacy docs
aiwg corpus frontmatter-backfill            # dry-run
aiwg corpus frontmatter-backfill --write    # write (additive; skips docs that already have frontmatter)

What the audit reports

Structural issues (the actionable failures): MISSING-ANALYSIS-DOC, MISSING-SIDECAR, MISSING-PDF (honoring audit-exclude-missing-pdf + legacy excluded types redirect/gap-note/chapter), PDF-PRESENT-BUT-MARKED-EXCLUDED, below-80-line-stub-threshold.
Depth bands by analysis line count: STUB (<80), compact (80–149), good (150–249), full (250–399), deep (400+).
Per-type section completeness (informational): for each ref's normalized source type, which of that type's required sections are absent. This is a completeness signal, not a hard issue — the registry's required set is the type's full template, which real inductions don't always fill.

Reconciliation with the quality skills

Skill	Question it answers
`induction-audit` (this)	Is the induction structurally complete + deep enough, with the sections its source type expects?
`research-quality-audit`	How strong is the evidence (GRADE)?
`best-practices-audit`	Does the corpus follow framework best practices broadly?
`sidecar-lint`	Are the citation sidecars structurally valid?

They compose; none duplicates the others. Run induction-audit after a batch induction to catch stubs/missing artifacts and per-type section gaps; run the quality skills to assess evidence strength.

Triggers

"audit inductions"
"check induction depth / quality"
"find stub inductions"
"backfill frontmatter"
"induction audit"

Notes

TS-native (src/artifacts/corpus-tools/induction-audit.ts) — port of section9 audit_inductions.py + backfill_frontmatter.py.
The per-type required sections come from the source-type registry (aiwg corpus source-types); override types per-corpus at documentation/source-types.yaml.

---name: induction-auditdescription: Audit research-corpus induction quality — depth bands (stub/compact/good/full/deep), structural integrity (analysis doc + sidecar + PDF, honoring audit-exclude conventions), and per-source-type required sections (a blog isn't flagged for missing Benchmark Results). Plus additive frontmatter backfill for legacy docs. Runs via `aiwg corpus induction-audit` / `aiwg corpus frontmatter-backfill`.---# Induction Audit & Frontmatter BackfillQuality + depth audit for inducted references, and an additive frontmatterbackfill for legacy analysis docs. The audit is **source-type-aware**: requiredsections come from the source-type registry (`source-types` skill / #1509), so ablog is checked for "Practical Relevance" and a repo for "Architecture", not for"Benchmark Results".## How to run```bash# Audit a REF rangeaiwg corpus induction-audit --start 599 --end 635# Audit one REFaiwg corpus induction-audit --ref REF-394# Audit the whole corpusaiwg corpus induction-audit# Backfill minimal frontmatter (ref_id/title/year/pdf_hash) into legacy docsaiwg corpus frontmatter-backfill # dry-runaiwg corpus frontmatter-backfill --write # write (additive; skips docs that already have frontmatter)```## What the audit reports- **Structural issues** (the actionable failures): `MISSING-ANALYSIS-DOC`, `MISSING-SIDECAR`, `MISSING-PDF` (honoring `audit-exclude-missing-pdf` + legacy excluded types redirect/gap-note/chapter), `PDF-PRESENT-BUT-MARKED-EXCLUDED`, `below-80-line-stub-threshold`.- **Depth bands** by analysis line count: STUB (<80), compact (80–149), good (150–249), full (250–399), deep (400+).- **Per-type section completeness** (informational): for each ref's normalized source type, which of that type's required sections are absent. This is a completeness signal, not a hard issue — the registry's required set is the type's full template, which real inductions don't always fill.## Reconciliation with the quality skills| Skill | Question it answers ||-------|---------------------|| `induction-audit` (this) | Is the induction structurally complete + deep enough, with the sections its **source type** expects? || `research-quality-audit` | How strong is the **evidence** (GRADE)? || `best-practices-audit` | Does the corpus follow framework best practices broadly? || `sidecar-lint` | Are the **citation sidecars** structurally valid? |They compose; none duplicates the others. Run `induction-audit` after a batchinduction to catch stubs/missing artifacts and per-type section gaps; run thequality skills to assess evidence strength.## Triggers- "audit inductions"- "check induction depth / quality"- "find stub inductions"- "backfill frontmatter"- "induction audit"## Notes- TS-native (`src/artifacts/corpus-tools/induction-audit.ts`) — port of section9 `audit_inductions.py` + `backfill_frontmatter.py`.- The per-type required sections come from the source-type registry (`aiwg corpus source-types`); override types per-corpus at `documentation/source-types.yaml`.

Frequently asked questions