ai-records-retention

Map AI prompts and outputs to city retention schedules and storage locations.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/BrianPillmore/MayorGPT --skill ai-records-retention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-records-retention
Source: https://github.com/BrianPillmore/MayorGPT/tree/main/skills/data-and-research/ai-records-retention
Command: npx skills add https://github.com/BrianPillmore/MayorGPT --skill ai-records-retention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify when AI prompts and outputs are public records, apply the correct retention schedule to AI-generated content, and produce a records retention map covering every AI use case in the city.

Core Features & Use Cases

  • Classify AI use cases by record type (administrative, official, legal, financial, etc.) and determine retention obligations.
  • Apply existing retention schedules to AI-produced content, and generate a city-wide retention map with storage locations and retrieval methods.
  • Flag AI prompts and logs that may be public records, and provide guidance on holds, vendor data, and legal review.

Quick Start

Follow the steps to map city AI use cases to retention rules and produce an actionable retention map.

Frequently Asked Questions about ai-records-retention

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

FAQPage Schema
Are AI prompts and outputs considered public records for city government compliance?

AI prompts and outputs can qualify as public records depending on their use case classification. This Skill identifies which AI-generated content meets public records criteria and flags prompts and logs that require retention scheduling.

How do I map AI use cases to a city records retention schedule?

You can map AI use cases by classifying each by record type, such as administrative, legal, or financial. The Skill applies existing retention schedules to AI-produced content and generates a city-wide retention map with storage locations and retrieval methods.

How do we manage vendor data logs for AI-generated public records?

Vendor data logs require careful consideration for AI-generated public records. The Skill flags vendor data-log considerations, identifies gaps in current retention coverage, and provides action items for attorneys and IT to implement proper vendor data management.

What happens when AI-generated records are subject to legal holds?

AI-generated records under legal holds must be flagged and managed separately from standard retention schedules. The Skill identifies records that may require holds and provides clear guidance for legal review and compliance action items.

Can this records retention approach work for all AI use cases in a city government?

Yes, the Skill produces a city-wide retention map covering all AI use cases. It applies retention rules by document type across administrative, official, legal, and financial categories, ensuring comprehensive coverage for municipal compliance.

What are the limitations of applying existing retention schedules to AI content?

Existing retention schedules may have gaps when applied to AI-generated content. The Skill flags these gaps, identifies prompts and logs that may not fit current categories, and provides action items for attorneys and IT to address retention coverage limitations.