isms-document-cleanup
From the author
Use this skill when an ISMS document (policy, procedure, statement of applicability or register) reads badly and someone asks "clean up this policy", "make this readable for the auditor", "this reads like AI wrote it", "deslop this document", "too much technical detail in the policy", "the revision history is a mess" or "tidy our ISMS documents before the audit". Rewrites the document so it reads like a competent person wrote it for an auditor, keeps every fact and obligation, proposes where lower-level detail should live, and lists every change for approval.
Install
npx skills add better-isms/grcskills --skill isms-document-cleanup -a claude-code
Installs to .claude/skills/isms-document-cleanup/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- document-consistency-checkbetter-isms/grcskillsUse this skill when a set of policies, procedures, plans and registers has grown in pieces and someone asks "check our documents for contradictions", "are our policies consistent", "the retention periods don't match", "which severity scale is right", "harmonise our ISMS documents", "cross-check the incident plan against the policy" or "clean up our documentation before the audit". Extracts the checkable facts from every document (periods, deadlines, scales, roles, labels, references), finds contradictions, naming drift and broken references, proposes which document owns each fact, and drafts a glossary and a fix list for the owners.Planning★ 53
- security-policy-draftingbetter-isms/grcskillsUse this skill when a company needs its information security policy set written or rebuilt, or asks "write our security policies", "draft the information security policy", "we need policies for the audit", "policy pack for a startup", "our template policies are 40 documents nobody reads" or "which policies do we actually need". Maps the policy set to the company's size and owners, drafts the top-level policy and the topic policies in testable language that reflects what the company does, flags commitments that need a decision, and prepares the approval and communication record for leadership.Security★ 53
- better-writingforjd/better-writingRewrite, draft, and review prose so it is clear, specific, human, and fits its context. Use when improving emails, reports, documentation, marketing copy, UI text, or posts that sound generic, AI-written, verbose, salesy, or formulaic, and when the user asks to humanise/humanize, de-AI, fix text that sounds like ChatGPT, light edit, copy edit, proofread, or keep my voice. Covers voice calibration, anti-slop audits, and preflight checks.Writing★ 50
- policy-review-cycle-refreshbetter-isms/grcskillsUse this skill when the periodic policy review is due or overdue, or someone asks "run the annual policy review", "our policies are out of date", "re-approve the policies before the audit", "what changed since the last review", "policy version history" or "who needs to sign off which policy". Collects what changed since each policy was last approved (incidents, findings, exceptions, new systems, law), proposes the edits per policy, separates editorial from substantive changes, drafts the version history and approval record, and plans the communication to staff.Engineering★ 53
- clean-codewondelai/skillsWrite readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.Engineering★ 2.5K
- simplify-docstobihagemann/turboRun a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers comments that misdescribe the code, what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "fix stale comments", "reduce doc noise", or "run simplify-docs".Writing★ 417
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in