report-writer

Generate structured Markdown audit reports comparing resources against baseline definitions.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill report-writer-cogni-ai-ou
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: report-writer
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/report-writer
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill report-writer-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating reliable, repeatable system audit reports by discovering resources, comparing them to a baseline, and updating the authoritative documentation when discrepancies are found.

Core Features & Use Cases

  • Comprehensive discovery & inventory: Systematically explores each resource category and documents all discovered items so nothing important is missed.
  • Baseline diffing & inconsistency detection: Compares current discoveries against expected baseline definitions to identify missing, extra, moved, duplicated, miscategorized, or inconsistently named items.
  • State tracking & documentation updates: Compares results with previous snapshots, updates baseline/documentation in the repository, and creates a pull request with descriptive change details.

Quick Start

Use the report-writer skill to run a comprehensive system audit against the existing baseline and automatically produce a structured Markdown report plus updated documentation via a pull request.

Frequently Asked Questions about report-writer

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

FAQPage Schema
How do I generate a system audit report comparing current resources against a baseline?ā–¼

Run a comprehensive system audit by discovering available resources and comparing them against baseline definitions to document discrepancies. The process outputs a structured Markdown report detailing missing, extra, duplicated, or miscategorized items through persistent snapshot comparisons.

What is repository inventory change tracking and how does baseline diffing work?ā–¼

Baseline diffing compares current audit discoveries against previous snapshots to detect state changes. Repository inventory change tracking identifies missing, extra, moved, or inconsistently named items by systematically exploring each resource category and matching findings against expected baseline definitions.

Can I automatically create a pull request for documentation updates after a system audit?ā–¼

Yes, you can automatically create a pull request for documentation updates after a system audit. The workflow updates baseline definitions and authoritative documentation in the repository, then publishes a PR featuring descriptive change details and change-aware diffs.

How do I detect orphaned or duplicated resources during a repository inventory check?ā–¼

Detect orphaned or duplicated resources during a repository inventory check by systematically discovering all items and comparing them against baseline definitions. The audit identifies extras, duplicates, and miscategorized items, documenting each discrepancy in a structured Markdown report.

What is the best way to maintain governance reporting for system audits over time?ā–¼

Maintain governance reporting by comparing current audit runs against previous snapshots to track state changes. Update the baseline and documentation in the repository automatically, ensuring repeatable, reliable reports that reflect the authoritative system state through change-aware diffs.