agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/ai-policy-writer/SKILL.md

ai-policy-writer

Skill1 starsChanged 26 days agoMITView on GitHub

Writes a practical AI acceptable-use policy when staff use AI tools without clear rules on data, approval and accountability.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when staff adopt AI tools informally, before rolling out a new AI tool, or after a data-handling concern or a client question about AI …

    line 9
  2. Distinctive:

    Write a one-page staff summary with practical do and do-not examples.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Policy Writer

When to use it

Use when staff adopt AI tools informally, before rolling out a new AI tool, or after a data-handling concern or a client question about AI use.

What Claude needs

  • client-context.md for business background
  • AI tools in use or planned
  • Data types handled, such as client, personal or confidential data
  • Client contract and regulatory obligations
  • Existing IT, security and privacy policies

Method

  1. Inventory current and planned AI use cases and the data each one touches.
  2. Classify data as allowed, restricted or prohibited for use with AI tools.
  3. Define approved tools, the approval route for new tools, and account and security requirements.
  4. Set rules for human review of AI output, accuracy checks and disclosure to clients.
  5. Assign owners for the policy, incident reporting and periodic review.
  6. Write a one-page staff summary with practical do and do-not examples.

Output format

Provide a policy with scope, data rules table, approved tools list, review and disclosure rules, roles and incident process, plus a one-page staff summary.

Quality checks

  • Written in plain language staff can follow
  • Consistent with existing privacy and security policies and client contracts
  • Legal and regulatory questions are flagged for professional review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.