Best use case
audit-extract is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Phase 1: Extract footnotes from DOCX with formatting annotations
Teams using audit-extract should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/audit-extract/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audit-extract Compares
| Feature / Agent | audit-extract | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Phase 1: Extract footnotes from DOCX with formatting annotations
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Phase 1: Extract Footnotes
Parse the DOCX file and build structured data for all subsequent phases.
## What This Phase Does
1. Parse `word/footnotes.xml` via lxml
2. Extract each footnote's runs with formatting flags (italic, small caps, bold)
3. Parse `word/_rels/footnotes.xml.rels` for hyperlink URLs
4. Build citation registry (hereinafter definitions, author-to-first-cite mapping)
5. Resolve cross-references (`supra note [_]` placeholders)
6. Extract all URLs for archiving inventory
## Script
```bash
uv run python3 "${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/scripts/extract_footnotes.py" --docx <path>
```
Output: `scratch/footnotes_data.json`
## Gate: Exit Extract
Before proceeding to Check phase:
- [ ] `scratch/footnotes_data.json` exists
- [ ] Contains entries for ALL footnotes in the document (verify count)
- [ ] Each entry has `formatted_text` field with inline markup
- [ ] Citation registry has hereinafter definitions
- [ ] URL inventory extracted
**If footnote count doesn't match document:** STOP. Investigate missing footnotes before proceeding.
## Next Phase
Read `${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-check/SKILL.md` and follow its instructions.Related Skills
audit-verify
Phase 5: Verify all corrections were applied correctly
audit-report
Phase 3: Generate and present audit report for user review
audit-crossrefs
Phase 7: Convert hardcoded cross-references to auto-updating NOTEREF fields
audit-correct
Phase 4: Apply corrections to DOCX
audit-check
Phase 2: Run mechanical checks and Gemini formatted audit
audit-archive
Phase 6: Archive URLs via perma.cc
bluebook-audit
This skill should be used when the user asks to 'audit footnotes', 'check Bluebook formatting', 'audit citations', 'run footnote audit', 'check my footnotes', 'bluebook audit', or needs systematic Bluebook compliance checking of a law review manuscript.
audit-fix-loop
Canonical doctrine for scored iterative improvement, and the generic fallback for ad-hoc 'iteratively improve / audit and fix / grade and improve / hill-climb quality / score and fix' requests that don't map to a domain workflow.
writing
This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.
writing-validate
Validate draft sections cover all PRECIS claims before review.
writing-setup
Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.
writing-revise
This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.