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 halves

The craft, and your facts.

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. The craft, how to approach the task and word it, is drafted by AI and reviewed by an expert, because the model is good at that and review catches the gaps. The facts it must be right about, the deadline, the statute, the exemption, come from you or a source you cite, never the model's memory, because that is where a made-up fact would hide.

the skill The craft

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

  • Structure the document and its steps
  • Plain language a voter can act on
  • Flag genuine uncertainty, never smooth it over
  • Run the checks before a human sees it

Drafted by AI, reviewed by an expert

you The facts

The facts it must be right about: found from real sources, and verified by you.

  • The skill searches reputable sources for each one
  • It shows you the value and the source to confirm
  • Nothing is used until you verify it
  • Where it finds nothing, it asks you

Researched, then verified by you

More than a faster way to write.

A vanilla model can already write in an expert voice. What it cannot be trusted to do 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: address every part of the request, write for a real reader, and stop to flag what is uncertain. This part is the craft, and it works today.

Researched, then verified

For anything legal, the deadline, the statute, the exemption, the skill searches reputable sources, shows you the value and the source, and uses it only once you confirm. What it can't find, it asks you for. It never supplies a fact from the model's memory. That discipline is what instructions alone can't add to a plain model.

See the difference

The same standard on every request.

A plain model writes a clean-looking notice, but it builds the load-bearing fact, the cure deadline, from memory or arithmetic and states it with full confidence even when it lands on the wrong day. The skill refuses to be the source of that fact: it researches the deadline, shows you the value and the source to verify, and won't draft until you confirm it.

The request

“A vote-by-mail ballot’s signature didn’t match the voter’s record. Draft the cure notice.” The cure deadline is the one fact that decides whether the ballot counts. Watch where each gets it.

Plain AI invents the fact
Your mail-in ballot’s signature didn’t match our records. Complete the enclosed Cure Form and make sure the county board receives it by November 15, 2025 — 11 days after the election. Return it in person, by mail, fax, or email.

What you can’t rely on

  • States the deadline as November 15 — confidently, from an “11 days after the election” rule of thumb, with no source you can check. It can be the wrong day, and nothing warns you.
  • Invents the return methods and contacts the same way: plausible, unsourced, impossible to verify.
  • Different every run; you can’t tell which draft quietly got a fact wrong.
With the skill researches, you verify

It searches reputable sources for the deadline, then shows you what it found, to confirm before drafting:

“Cure deadline: Nov 14, 5 p.m. — from the state election calendar. Correct?”

You verify (or correct) it. It does the same for the methods and contacts, asks for anything it can’t find, then writes the complete notice.

What holds, every time

  • It researches each fact and shows you the value and its source, so you can fact-check before a word is drafted.
  • Nothing is used until you confirm it; what it can’t find, it asks you for. Then it writes a complete notice.
  • The wording, structure, and tone are the skill’s. Every legal fact is researched and verified.

The skill does the legwork but is never the source of truth: it researches each fact, exposes the source, and uses it only once you’ve fact-checked it. The wording is the skill’s; every deadline, method, and citation is found in a real source and verified by you.

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 verified sources. 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. Works on any plan, Free through Enterprise.
  2. First turn on code execution: open Settings → Capabilities and enable Code execution and file creation. Skills need it.
  3. Open Customize → Skills.
  4. Click +, then Create skill, and choose Upload a skill. Select the skill’s .zip.
  5. Toggle the skill on in your skills list. Claude then uses it on its own when a request matches what it describes.

Custom skills are private to your account, not shared across an organization. On Team or Enterprise, an admin enables code execution and Skills under Organization settings → Skills. 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.

Get the most out of a skill.

Name your jurisdiction

The skill brings the method and does the research; your job is to verify. Tell it your state and county, and it will find the deadline, statute, and contacts, show you each with its source to confirm, and ask for anything it can’t find before it drafts a word.

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