Skip to content
Back to skills

Public Records Plan

ASecurity

Research, draft, and track a jurisdiction-specific public-records request without legal conclusions or automated submission.

  • 211 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 21, 2026
ai-agentsrails

Security analysis

A100/100

Scanned September 21, 2026

npx -y skills add jmagly/ai-writing-guide --skill public-records-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Public Records Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Public Records Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jmagly-public-records-plan-aiwg/badge)](https://www.skillsdirectory.com/skills/jmagly-public-records-plan-aiwg)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
namespace: aiwg
platforms: [all]
name: public-records-plan
description: Research, draft, and track a jurisdiction-specific public-records request without legal conclusions or automated submission.
triggers:
  - plan a public records request
  - draft a FOIA request for human review
  - track a records request and response
---

# Public Records Plan

## Process

1. Check already-published sources, then resolve a current official jurisdiction
   and agency profile. Never fall back from state/local law to federal FOIA.
2. Describe records, custodians, systems, dates, formats, exclusions, fee
   ceiling, urgency, privacy minimization, and source-linked contact details.
3. Mark calculated dates as estimates derived from an approved profile; preserve
   agency-provided dates separately.
4. Produce a versioned draft marked `NOT REVIEWED — DO NOT SEND` until a named
   human approves the exact version. Submission is always manual.
5. Hash and quarantine responses; preserve originals and label OCR/extraction as
   derived. Do not reverse redactions or construct personal dossiers.
6. Track sent and observed/calculated due dates separately, status/fees,
   response artifact hashes, revision and appeal windows, and the linked
   investigation. Support PDF, scan, email, spreadsheet, and attachment inputs.

## Output

A `public-records-plan` artifact, evidence checklist, and pending human action.

## References

- `templates/public-records-plan.md`
- `schemas/public-records-plan.schema.json`
- `docs/research/legal-ethics-guardrails.md`
- `docs/research/control-source-matrix.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.