agentclaw

free skill — AI usage policy

An AI policy your team will actually read

Your staff is already pasting things into ChatGPT. The only question is whether there are rules. This recipe takes you from no policy to a one-page policy plus the rollout email in a single working session: gather five facts, run two prompts, QA, ship. Works with ChatGPT, Claude, Gemini, or any capable assistant. Free, no email gate.

Free download · Markdown recipe

AI usage policy template

One markdown file with the full method: a five-question fact-gathering checklist, a copy-paste prompt that drafts the policy (approved tools, green/yellow/red paste rules, approval process, incident reporting), a second prompt for the rollout email, and a QA pass before anything ships.

  1. Download the recipe and answer the five fact-gathering questions
  2. Run the policy prompt with your answers filled in
  3. Run the rollout email prompt in the same chat
  4. Work the QA list, then publish and collect acknowledgments

What this handles

The whole starter policy, in plain language a new hire can absorb in five minutes. It covers what staff may and may not paste into AI tools using a green/yellow/red system (green is fine, yellow means ask first, red never leaves the building), with concrete examples pulled from the data your business actually handles, not vague categories. It names one person who approves new tools and exceptions, sets a no-blame rule for reporting paste mistakes fast, and ends with an acknowledgment line so you know who has read it.

It also produces the rollout email: short, human, and clear that this is a how-to-use-AI policy, not a ban. What it doesn't do is enforce anything. A policy is rules on a page; enforcement is a separate problem.

How to run it

One session, four steps. First, gather five facts before you open the assistant: which tools are in use today and on what account types, what data would hurt you if it leaked, who approves exceptions, what regulations or client contracts apply, and where the policy will live. Second, run the policy prompt — it locks the structure to seven sections, caps the length at 600 words, and forces the assistant to write [FILL IN] instead of inventing facts you didn't provide.

Third, run the rollout email prompt in the same chat. Fourth, work the QA list: make every red-list example concrete, resolve every placeholder, walk two real scenarios past the policy, and confirm the approver knows they're the approver. If you're in a regulated industry, a lawyer reviews before rollout — the recipe says so plainly, because this is a starting draft, not legal advice.

When to upgrade

Honest limit: a policy tells people what not to paste, and that's all it does. It works while AI use means a handful of people drafting emails. Once client data flows through prompts as part of real workflows, across teams and tools, a document can't protect you — the workflows themselves have to be built so sensitive data never touches a consumer chatbot, on approved tools with proper data agreements, with someone accountable for the whole system. That's what we install, and a free audit will show you where your current AI use actually stands.

The policy is the easy part

Rules on a page keep casual AI use safe. Putting AI to real work (client data, live workflows, systems that run every day) takes infrastructure built so the policy can't be broken by accident. The free AI opportunity audit maps what that looks like inside your business. Same team. Double the output.

We take on companies ready to invest $5,000+/month. Not there yet? Our free resources are genuinely free.