How it works

Built to be trusted, and built to travel.

A confidently wrong legal answer is worse than no tool at all. Everything about how these skills are made, and how you use them, follows from that one fact.

The two layers

Judgment, and the law it stands on.

A plain language model can sound authoritative and cite sources, which makes a wrong fact more damaging, not less. So every skill keeps two things separate and holds each to its own standard. The judgment is drafted by AI and reviewed by an expert, because the model is good at knowing how to approach a task and review catches the gaps. The authority comes from real law and is verified by an expert, because that is where a made-up statute would hide.

SKILL.md Judgment layer

How to approach the task, the way an election expert would.

  • Identify the governing jurisdiction first
  • Cite the controlling law for every claim
  • Flag genuine uncertainty, never smooth it over
  • Draft in plain language, for human review

Expert-reviewed

references/ Authoritative layer

The actual law, the facts the judgment grounds itself in.

  • Specific statutes & administrative rules
  • Deadlines, cure windows, exemptions
  • Dated to the day the law was verified
  • Never AI-generated from memory

Sourced from real law · expert-verified

Where the value comes from

More than a faster way to write.

A vanilla model can already write in an expert voice. What it cannot do on its own is be right about your law. Two things close that gap.

Encoded method

The skill makes the model work through the task the way an experienced official would: identify the governing rule, address every part of the request, write for a real reader, and stop to flag what is uncertain. This part works today.

Grounded facts

The skill carries the actual law, sourced and dated, so the answer rests on something real instead of the model's memory. Instructions alone cannot do this. It takes verified references, and an expert to check them.

See the difference

The same standard on every request.

Ask a plain model the same kind of question twice and you get two slightly different answers, with no way to know which one dropped a required element or misremembered a deadline. A skill removes that variance: it runs the same expert-checked discipline every time and binds the facts that matter to cited, dated law.

The request

“Make this ballot-return instruction readable for voters.” Now imagine the same kind of ask a hundred times over, across notices and staff.

Plain AI different every run
Sign your ballot certificate, seal it inside both envelopes, and mail it back by Election Day. Your signature is required for your vote to count.

What you can’t rely on

  • Worded a little differently every run, so you can’t tell which draft quietly dropped a required element.
  • The 8 p.m. receipt deadline is recalled from memory, not tied to a source you can check.
  • No flag when the law is unclear; it just commits to an answer.
With the skill same standard every time
Return your ballot so the county board receives it by 8:00 p.m. on Election Day. Ballots that arrive after that are not counted (unless the law says otherwise). Then: sign the inner envelope, seal your ballot inside it, and place it in the outer envelope.

What holds, every time

  • The same expert-checked checklist runs on every request: all required elements, in order, every time.
  • The deadline is bound to cited, dated law, not the model’s memory.
  • When the law is unclear it flags for review instead of guessing, consistently.

Run it once or a thousand times, by anyone on staff: the skill applies the same verified discipline and grounds the facts in cited law. That repeatability is the point, not the keystrokes it saves.

Checking the work

Some skills check themselves before they answer.

For certain tasks, a model is a better reviewer than it is a writer. Those skills draft a response, test it against a short list of explicit, expert approved criteria, revise, and only show you what passes. A records response is checked for completeness, correct classification, and grounding in cited law. A plain language rewrite is checked for preserved meaning, retained requirements, and reading level. The loop is only added where a real test exists, because agreeing with yourself is not the same as being right.

Putting it to work

Use a skill three ways.

A skill is portable expertise, not an app. It goes wherever you already work. Pick whichever fits how you use AI today.

01

Paste into any tooluniversal

Copy the skill’s contents into Claude, ChatGPT, Copilot, or Gemini, then ask your question. Works everywhere, no setup.

02

Add it to your tool

Set it up as a Claude skill, a custom GPT, a Copilot agent, or a Gemini Gem so it is ready whenever you need it.

03

Download the package

Grab the whole folder (SKILL.md, references, checks, examples), versioned and dated. Yours to keep and review.

Step by step

Adding a skill to your tool.

The download is a Claude skill: a SKILL.md file plus its reference material. Claude takes it as is. For the other tools you paste the contents of SKILL.md as the instructions and add the reference files as knowledge. Here is the path in each.

Claude Native, upload the file as is
  1. Use Claude on a Pro, Max, Team, or Enterprise plan. Skills are not on the Free plan.
  2. Open Settings → Capabilities and turn on code execution (creating and editing files). Skills need it.
  3. Go to Settings → Features and find the Skills section.
  4. Choose Upload and select the skill’s .zip. Claude reads the SKILL.md and shows the name and description.
  5. That is it. Claude uses the skill on its own when your request matches what it describes.

Skills on claude.ai are per person, not shared across an organization. In Claude Code, drop the unzipped folder into ~/.claude/skills/ instead of uploading.

ChatGPT Adapt into a custom GPT
  1. On a paid plan (Plus or higher), go to chatgpt.com/create.
  2. Open the Configure tab.
  3. Set a name and description.
  4. Paste the contents of SKILL.md into Instructions. There is an 8,000-character limit, so if it runs long, move the rest into a knowledge file.
  5. Under Knowledge, upload the reference files from the skill folder.
  6. Save it. Keep it private or share it by link.

Building a custom GPT requires a paid ChatGPT plan.

Microsoft Copilot Adapt into an agent
  1. Open Microsoft 365 Copilot at microsoft365.com/chat or in Teams. You need a Microsoft 365 Copilot license.
  2. Select New agent, then Skip to configure.
  3. On the Configure tab, set the name and description, and paste SKILL.md into Instructions.
  4. Add the reference files as Knowledge. Copilot reads from SharePoint or OneDrive rather than loose uploads, so put the files there first and point the agent at them.
  5. Test on the Try it tab, then create the agent.

Copilot is the one tool that will not take loose file uploads as knowledge. The reference files have to live in SharePoint or OneDrive.

Gemini Adapt into a Gem
  1. Go to gemini.google.com and sign in.
  2. Open the sidebar and select Gems, then New Gem.
  3. Name it and paste SKILL.md into the instructions.
  4. Under Knowledge, add the reference files (up to 10).
  5. Use Preview to test it, then Save.

For a large set of reference files, Google suggests building a NotebookLM notebook and connecting it to the Gem.

Three habits

Get the most out of a skill.

Name your jurisdiction

A grounded skill is only correct for the place whose law it cites. Tell it your state and county. When a skill is marked as working in any jurisdiction, it brings the method and leaves the local facts to you.

Read the flags

These skills are built to surface what they are unsure about: a date to confirm, an exemption to verify, a question for a lawyer. When a draft raises a flag, that is the point. Resolve it before you act.

You decide

Every result is a draft for your review and signature. It does not send anything and it does not replace your judgment. You remain the authority on your office and your jurisdiction.

Find a skill for a task on your desk.

Browse the skills