Skip to content

maxwellokumu/okaudit-claude-skills / compliance-controls/policy-writer

policy-writer

Verified

Draft security and compliance policy documents aligned to common frameworks so Claude can turn user requirements into professional, review-ready policy text.

FileKindSize
README.mdmarkdown1.8 KB
SKILL.mdskill md1.7 KB
main.pyscript26.5 KB
skill.yamlconfig1.2 KB
# policy-writer

Generate professional, framework-aligned security policy documents ready for
review and adoption. Each policy includes all standard sections with numbered,
enforceable policy statements enriched with framework-specific references.

---

## Requirements

```bash
pip install python-dotenv
```

---

## Usage

```bash
# ISO 27001 Access Control Policy
python main.py --framework ISO27001 --topic access --org-name "Acme Corp"

# PCI-DSS Password Policy
python main.py \
  --framework PCI-DSS \
  --topic password \
  --org-name "PaymentCo Ltd" \
  --review-cycle "Semi-Annual"

# GDPR Incident Response Policy
python main.py --framework GDPR --topic incident-response --org-name "DataCo"

# NIST Encryption Policy
python main.py --framework NIST --topic encryption

# CIS Acceptable Use Policy
python main.py --framework CIS --topic acceptable-use --org-name "TechOrg"
```

---

## Available Topics

| Topic | Description |
|-------|-------------|
| `password` | Password creation, complexity, rotation, and storage |
| `access` | Access provisioning, least privilege, reviews, and off-boarding |
| `encryption` | Encryption standards, key management, prohibited algorithms |
| `incident-response` | Incident detection, response SLAs, breach notification |
| `acceptable-use` | System use rules, prohibited activities, monitoring notice |

---

## Supported Frameworks

`SOC2` · `ISO27001` · `NIST` · `CIS` · `PCI-DSS` · `GDPR`

Other framework names are accepted but will use generic best-practice language.

---

## Policy Sections

Every generated policy includes:
1. Title and metadata table (version, date, owner, review cycle, framework reference)
2. Purpose
3. Scope
4. Policy Statements (8–10 numbered, enforceable statements)
5. Roles and Responsibilities
6. Compliance and Enforcement
7. Exceptions Process
8. Review and Revision History
9. Related Documents
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall