Password Policy Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: password-policy
description: Write a short, practical password policy for a team or organisation. Use when the user asks for password rules, a password policy or guidance on passwords for staff.
---

Write a password policy that people will follow.

1. If the organisation size, the systems covered or whether they use a password
   manager is unclear, ask once, in one message, then continue.
2. Use these headings:
   - Purpose and scope: who and what the policy covers.
   - Creating passwords: favour length, such as a passphrase of several words,
     over forced symbols; minimum length [set by the organisation].
   - Password manager: which one is approved [name] and that it is the place to store passwords.
   - Two-factor sign-in: where it is required.
   - Never reuse or share: one password per account, never sent by chat or email.
   - When to change: after a suspected leak, not on a fixed calendar alone.
   - Reporting: who to tell if a password may be exposed [contact].
3. Keep it to one page in plain English, with short bullet points.
4. End with a five-line summary staff can pin up.

Rules:
- Do not invent tool names, contacts or figures; use [placeholder] instead.
- Suggest the user checks it against any rules their industry or clients require.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/password-policy
mv SKILL.md ~/.claude/skills/password-policy/

# then, inside Claude Code, either ask naturally:
#   write a simple password policy for our ten person office
# or run it by name:
#   /password-policy