acceptable-use-policy-drafting SKILL.md skillA
acceptable-use-policy-drafting from better-isms/grcskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add better-isms/grcskills/acceptable-use-policy-drafting@git:20261027.94f7f3ePins git:20261027.94f7f3e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- better-isms/grcskills
- Path
skills/tristan-roth/acceptable-use-policy-drafting/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.94f7f3e, committed Oct 27, 2026
- First version recorded
- Oct 19, 2026
- Size
- 8,526 bytes
- Repository stars
- 56
- License
- MIT
Use this skill when a company needs rules for how staff use company systems, data, devices and AI tools, or asks "write our acceptable use policy", "AUP for employees", "can staff use ChatGPT at work", "AI usage policy", "BYOD rules", "remote work security rules" or "a policy people will actually read". Finds how people really work (devices, apps, AI tools, travel), puts the choices to the reader as decisions, drafts a short plain-language policy with concrete do and do not examples, and adds…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Use this when there is no acceptable use policy, or when the current one predates AI tools, remote work or personal devices. You get three documents in a new folder, `./acceptable-use-policy-drafting/`: the staff policy itself, two to three pages in plain language (`acceptable-use-policy.md`); a note of the choices leadership made and how people really work today, for the people who own the policy rather than staff (`decisions.md`); and five quiz questions to check that a colleague understood it after one read (`comprehension-check.md`). This skill drafts for a human to review and sign; this skill never marks a control effective. HR and leadership approve the policy, and HR or legal confirm anything touching employment terms or monitoring. End `acceptable-use-policy.md` with `## Not checked`: what this run did not read or could not open, what it assumed and what it did not verify, specific to this run. Then add a blank `## Review record` for the approver: reviewer role and competence basis, items sampled and the source each was traced to, what was changed or rejected, one item the draft did not flag and what checking it showed, decision, date and draft version reviewed. …
Read the whole file at its exact version.
How to install
mdr add better-isms/grcskills/acceptable-use-policy-drafting@sha256:d7741d1724a74a6dThe line at the top of this page pins the label git:20261027.94f7f3e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pwjc5fanqbhkd7dx)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 19, 2026 and Oct 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.94f7f3e latest | 2026-10-27 | 94f7f3e | 8,526 B | A | view · diff |
| git:20261019.20937b5 | 2026-10-19 | 20937b5 | 7,959 B | A | view · diff |
| git:20261019.3c6cd53 | 2026-10-19 | 3c6cd53 | 7,823 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8526 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
better-isms/grcskills · 56 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pwjc5fanqbhkd7dx GET https://markdownregistry.com/api/v1/resolve?ref=better-isms/grcskills/acceptable-use-policy-drafting GET https://markdownregistry.com/api/v1/blob/d7741d1724a74a6db228c577524cb4a683496b5ea8249b3cdef9c537e2f3718d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.