borghei/Claude-Skills / documents/docx-toolkit
docx-toolkit
VerifiedAudit Microsoft Word (.docx) documents for heading hierarchy, comments, tracked changes, and style consistency. Use when reviewing a contract draft, preparing a document for handoff, or enforcing a style guide.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| assets/handoff_checklist_template.md | markdown | 1.4 KB |
| assets/style_compliance_template.md | markdown | 1.8 KB |
| references/docx_review_checklist.md | markdown | 2.5 KB |
| scripts/docx_auditor.py | script | 6.7 KB |
assets/style_compliance_template.md
View on GitHub# Allowed Paragraph Styles (Style Guide)
Use this template to declare which paragraph styles your team allows. Run the auditor against any candidate document; flag any document using styles outside this list.
---
## Allowed Styles
| Style name (in Word) | Use for | Notes |
|---------------------|---------|-------|
| `Normal` | Body text | Default; do not modify |
| `Heading 1` | Major sections | One per document or major part |
| `Heading 2` | Subsections | Required between H1 and H3 |
| `Heading 3` | Sub-subsections | Avoid going deeper |
| `List Paragraph` | Bulleted / numbered lists | Standard list style |
| `Quote` | Block quotations | Indented, italicized |
| `Caption` | Figure / table captions | Auto-numbered |
| `Footer` | Page footer content | Includes confidentiality marking |
---
## Disallowed Styles
Anything not on the allowed list. Common drift offenders:
- `Body Text 2`, `Body Text 3` — collapse to `Normal`
- `Heading 4`, `Heading 5` — restructure or use `Heading 3`
- Inline overrides (bold, color) instead of named styles
- Custom named styles inherited from older templates
---
## Validation Workflow
1. Run auditor: `python scripts/docx_auditor.py document.docx`
2. Compare `styles_used` output against this template
3. Any style not on the allowed list → reformat the offending paragraphs
4. Re-run audit until `styles_used` is a subset of the allowed list
---
## Tips
- **Lock the template.** Distribute a `.dotx` template containing only allowed styles. New documents start clean.
- **Train, then enforce.** Style sprawl usually comes from copy-paste from email or other documents. A short style-guide deck plus the audit-as-gate prevents most of it.
- **Don't fight the brand team.** If marketing says the heading color is `#1A47BC`, use it via the named style, not inline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |