vendor-gov-forms

Acquire official government forms from issuing authorities with byte-level provenance tracking.

Updated Aug 27, 2026

Search Tags:#provenance #checksum #canonical-source #government-forms #pdf-vendoring #legal-filing #form-templates

Ready to run

npx skills add https://github.com/neon-law-foundation/navigator --skill vendor-gov-forms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vendor-gov-forms
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/vendor-gov-forms
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill vendor-gov-forms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that government forms and other official documents are acquired from the issuing authority’s own source, preserved as exact bytes, and tracked with provenance that can be verified later from repository history.

Core Features & Use Cases

Canonical sourcing: Pull forms, instructions, and cited official documents only from the authority’s domain.
Byte-level preservation: Commit the exact PDF or document bytes before building field maps, overlays, or templates.
Provenance tracking: Record source URL, retrieval date, revision, and checksum so refreshes are auditable.
Use case: A legal team needs a Nevada filing form or IRS document vendored correctly before automation can be built, and this Skill enforces that workflow.

Quick Start

Ask me to vendor the canonical government form from its issuing authority, and I will verify the source, save the exact bytes, and update the provenance ledger.

Frequently Asked Questions about vendor-gov-forms

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

FAQPage Schema

How do I vendor government forms with verifiable provenance for legal filings?▼

Vendoring government forms with verifiable provenance requires acquiring official PDFs directly from the issuing authority's canonical source, preserving exact bytes on-disk, and recording the source URL, retrieval date, revision, and checksum in a ledger for auditable refreshes.

Why do I need byte-level preservation and checksum tracking for official form templates?▼

Byte-level preservation and checksum tracking ensure that vendored government forms match the issuing authority's canonical source exactly, providing an auditable provenance ledger that prevents unauthorized alterations before any field mapping or template overlay is authored.

Can I build form-field classification and overlays before saving the canonical PDF?▼

No, form-field classification and template overlays must be authored only after committing the exact PDF bytes from the canonical government source, ensuring the original document's integrity is preserved and tracked in the provenance ledger.

What's the best way to track revisions and source URLs for court and IRS form refreshes?▼

Tracking revisions and source URLs for court and IRS form refreshes requires a provenance ledger that records the canonical source domain, retrieval date, revision number, and checksum, ensuring any automated legal workflow updates remain fully auditable.

Does this approach to PDF vendoring work for county agencies and secretaries of state?▼

Yes, canonical sourcing applies to form-backed legal workflows across courts, secretaries of state, IRS, and county agencies, requiring only that forms are pulled exclusively from the specific issuing authority's own domain.

When should I not use canonical source vendoring for government documents?▼

Canonical source vendoring should not be used when a government form cannot be acquired directly from the issuing authority's domain, as the provenance workflow requires exact byte-level preservation and ledgered source URLs to maintain legal auditability.