Policy writing
Write clear internal policies people can follow under time pressure. Use whenever the user asks for a company policy, acceptable use policy, security policy draft, travel policy, or HR/process policy that needs plain language.From its SKILL.md
npx -y skills add shinzoxD/knackbox --skill policy-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.3 KB, 186 tokens by cl100k_base, as published. Nobody here has run it
Policy Writing
Policies state rules, scope, exceptions, and enforcement. Prefer short sentences and testable requirements over corporate fog.
Structure
# Policy: <title>
**Owner:** …
**Effective:** …
**Applies to:** …
## Purpose
## Scope
## Requirements
## Exceptions
## Enforcement / consequences
## Related docs
## Revision history
Rules
- Requirements use must/should carefully and consistently.
- Do not invent legal obligations; use provided constraints.
- Define terms once; avoid undefined acronyms.
- Separate procedure (how) from policy (must).
- Include exception path and owner.
- Make enforcement realistic.
Edge cases
- Regulated industries: flag need for legal review.
- Global companies: locale variations.
- Security policies: pair with runbooks, not only prose.
What ships with it: 1 file
1.1 KB alongside SKILL.md
benchmarks/
- prompts.json1.1 KB