Best use case
audit-archive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Phase 6: Archive URLs via perma.cc
Teams using audit-archive 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-archive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audit-archive Compares
| Feature / Agent | audit-archive | 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 6: Archive URLs via perma.cc
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 6: Archive
Archive all non-permanent URLs in footnotes via perma.cc API.
## What This Phase Does
1. Extract URL inventory from footnotes data
2. Deduplicate URLs (same URL across multiple footnotes)
3. Archive each URL via perma.cc API
4. Write perma.cc links back to DOCX footnotes
5. Save progress after each successful archive
## Prerequisites
- Perma.cc API key in `.env` file (project-level or user home directory)
- For institutional accounts: organization folder ID (unlimited archives)
- Free accounts: 10 links/month limit
## Script
```bash
uv run python3 "${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/scripts/permacc_archive.py" --docx <path> --data scratch/footnotes_data.json
```
## Institutional Account Setup
```bash
# Find your organization and folder ID
curl -H "Authorization: ApiKey YOUR_KEY" https://api.perma.cc/v1/organizations/
```
Use the `folder` parameter when creating archives:
```python
requests.post("https://api.perma.cc/v1/archives/", json={
"url": url,
"folder": FOLDER_ID, # enables institutional limits
})
```
## Gate: Exit Archive
- [ ] All non-perma.cc URLs archived
- [ ] perma.cc links written to DOCX
- [ ] `scratch/permacc_archives.json` contains all mappings
## Next Phase
Read `${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-crossrefs/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-extract
Phase 1: Extract footnotes from DOCX with formatting annotations
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
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.