audit-report-writing

Q: How do I install audit-report-writing?

Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-report-writing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/audit-report-writing/ (personal) or .claude/skills/audit-report-writing/ (project).

by mukul975Docs & Writing

Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.

Installs: 50
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-report-writing

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads audit-report-writing automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Privacy Audit Report Writing

Overview

Privacy audit report writing is the discipline of translating audit fieldwork into a structured, defensible written deliverable that communicates audit objectives, methodology, findings, and recommendations to stakeholders. A well-crafted audit report serves as the primary vehicle for communicating the state of privacy compliance to governance bodies, management, regulators, and data protection authorities.

Under GDPR Article 39(1)(b), the Data Protection Officer must monitor compliance including audits, meaning audit reports are a key instrument of DPO oversight. ISO 19011:2018 (Guidelines for auditing management systems) Section 6.6 provides the international standard framework for audit report content and distribution.

Report Structure

Standard Sections

Section	Purpose	Typical Length
Cover Page	Report identification, classification, distribution list	1 page
Executive Summary	High-level findings, overall opinion, critical issues	1-2 pages
Table of Contents	Navigation aid	1 page
Audit Scope and Objectives	What was audited, boundaries, exclusions	1-2 pages
Methodology	Audit approach, sampling, tools used	1-2 pages
Findings and Observations	Detailed findings with evidence, risk rating, root cause	5-20 pages
Recommendations	Prioritised corrective actions	2-5 pages
Management Response	Auditee agreement/disagreement, action plans, deadlines	2-5 pages
Appendices	Evidence references, sampling details, interview logs	Variable

Findings Classification

Severity Ratings

Rating	Definition	Response Timeline
Critical	Material non-compliance creating immediate risk of regulatory enforcement, data breach, or significant harm to data subjects	Immediate remediation; board notification within 24 hours
High	Significant control weakness or non-compliance that could lead to a breach or regulatory action if not addressed	Remediation plan within 14 days; completion within 60 days
Medium	Control deficiency that does not currently pose immediate risk but could deteriorate	Remediation within 90 days
Low	Opportunity for improvement; minor procedural gap	Remediation within 180 days or next audit cycle
Observation	Good practice note or suggestion; not a formal finding	No mandatory action

Finding Documentation Format

Each finding should include:

Element	Description
Finding ID	Unique identifier (e.g., AUDIT-2026-001)
Title	Concise descriptive title
Condition	What was observed (the current state)
Criteria	What was expected (the standard, policy, or regulation)
Cause	Root cause analysis (why the gap exists)
Effect	Impact or potential impact of the finding
Risk Rating	Critical / High / Medium / Low
Recommendation	Specific corrective action
Management Response	Auditee's response, action plan, responsible owner, deadline
Evidence Reference	Document IDs, screenshots, interview notes

Executive Summary Writing

The executive summary must:

State the audit scope, period, and objectives in one paragraph
Provide an overall compliance opinion (satisfactory, needs improvement, unsatisfactory)
Summarise the distribution of findings by severity
Highlight any critical or high findings requiring immediate attention
Note positive observations and areas of strong compliance
Conclude with the overall risk posture assessment

Evidence Referencing

Evidence Types

Type	Example	Reference Format
Documentary	Policy documents, procedures, records	DOC-001: "Data Retention Policy v3.2, dated 15-Jan-2026"
Testimonial	Interviews, walkthroughs	INT-001: "Interview with DPO, 10-Mar-2026, 14:00-15:00"
Analytical	Data analysis, sampling results	ANA-001: "DSAR response time analysis, Q4 2025"
Observational	System screenshots, process observation	OBS-001: "Screenshot of consent banner, captured 12-Mar-2026"

Report Quality Criteria

Criterion	Standard
Accuracy	All findings supported by verified evidence; factual errors corrected before issuance
Objectivity	Balanced presentation; positive observations included alongside findings
Clarity	Plain language; technical terms defined; avoid jargon
Completeness	All scope areas addressed; no material omissions
Constructiveness	Recommendations are actionable, specific, and proportionate
Timeliness	Draft report issued within 10 business days of fieldwork completion
Conciseness	No unnecessary repetition; findings are distinct

Distribution and Confidentiality

Classification	Recipients
Full Report	Chief Privacy Officer, DPO, Internal Audit Director, auditee management
Executive Summary Only	Board Audit Committee, C-suite
Redacted Version	External regulators (on request), external auditors
Finding-Specific Extracts	Individual finding owners for remediation tracking

GDPR and Regulatory Context

Regulation	Audit Report Relevance
GDPR Article 5(2)	Accountability principle — audit reports demonstrate compliance monitoring
GDPR Article 24	Controller must implement appropriate measures and be able to demonstrate compliance
GDPR Article 28(3)(h)	Processor must allow and contribute to audits conducted by the controller
GDPR Article 39(1)(b)	DPO must monitor compliance including assignments of responsibilities, awareness-raising, training, and related audits
GDPR Article 47(2)(j)	BCRs must include audit mechanisms
ISO 27701:2019 Section 5.2	PIMS-specific audit requirements
ISO 19011:2018 Section 6.6	Preparing and distributing the audit report

FAQ

What does the audit-report-writing skill do?

How do I install audit-report-writing?

Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-report-writing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/audit-report-writing/ (personal) or .claude/skills/audit-report-writing/ (project).

Which AI agents can use audit-report-writing?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is audit-report-writing safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains audit-report-writing?

It is published by mukul975 in mukul975/privacy-data-protection-skills. It has 50 recorded installs.