4What You Can Do Now

With the tools you actually have.

Most offices have, at best, a licensed Copilot tenant. That is enough to borrow the logic of the best legal skills, and enough to use AI to check your own work.

From Claude skills to Copilot

Copilot can’t install a skill. It can follow one.

Claude for Legal publishes its skills as plain-text instructions: about 100 open-source skills on GitHub (Apache 2.0), each a readable SKILL.md file. Of the three big legal offerings, only Claude publishes its skills this way. None ships a prosecution workflow, but the litigation and verification skills port well because they are mostly written instructions.

Skills worth borrowing
chronology→Case chronology, every entry sourced
claim-chart→Offense elements chart with strength ratings
deposition-prep→Direct / cross examination outline
privilege-log-review→Brady / Giglio discovery log
research-start→Research roadmap of leads, each tagged “unverified”

Start in the litigation-legal folder at github.com/anthropics/claude-for-legal.

How to move a skill
1

Find it in Claude

Open the SKILL.md. It reads like a procedure, because it is one.

2

Keep the logic

  • Keep: the rules, the step order, the output table.
  • Drop: file-system steps, connectors, scheduled agents.
3

Rebuild it in Copilot

  • A saved prompt for one-off tasks
  • An Agent Builder agent (about 8,000 characters of instructions)
  • Copilot in Word for open drafts
Five rules that travel into any Copilot prompt

Keep these, whatever tool you paste them into.

Click a rule for the sentence to put in the prompt.

Before any of thisUse only the office’s licensed, enterprise-protected Copilot tenant for case material, never a personal account. Confirm with IT or your AOC contact what data Copilot can see.
The same design in Copilot Studio

One parent agent and two connected agents.

The three-skill design from Part 3 maps onto Copilot Studio’s multi-agent pattern without changing the instructions.

In ClaudeIn Copilot Studio
Prosecutor’s analysis skillParent agent holding the same instructions
General Statutes skillChild agent grounded on a SharePoint library of statute files
Pattern Jury Instructions skillChild agent grounded on a second library of instruction files
One skill calling anotherParent hands off to a connected agent by its description
Build order
  1. Load the files into two SharePoint libraries
  2. Create a child agent for each library
  3. Create the parent agent with the analysis instructions
  4. Connect both child agents and test on a real report
What to check
  • Give each child agent its own library; Microsoft advises against sharing sources.
  • Describe each child agent clearly; the parent routes by its description.
  • Test that retrieval returns element text verbatim.

Source: Microsoft Learn, Copilot Studio multi-agent patterns and knowledge sources documentation (2026).

Analyze your own work

Claude found my prior mistakes.

I ran a 404(b) motion I wrote as an ADA through two tools: a tabular review skill that builds a table of every authority cited, and a CourtListener connector that pulls each opinion to verify the citation. The motion was State v. Sellers (2013): human-drafted, granted, and upheld on appeal, with each of these errors in it.

01 · Claude for Legalcorporate-legal: tabular-review

Builds an Excel table from a set of data. Similar tabular reviews are available in most legal AI products.

02 · CourtListenerVerify the case law

Uses the CourtListener connector to pull opinions and check citations, when possible.

Four serious citation errors, and what fixes them
Misattributed quoteState v. WilliamsA real case, a real-sounding quote, the wrong source.+
What the brief said

The Supreme Court “has held only that ‘the trial court must find the evidence to be substantial.’” Williams, 307 N.C. 452, 454 (1983).

What the source shows

That sentence is from State v. Haskins, a Court of Appeals case (104 N.C. App. at 680). Williams is a heroin-possession sufficiency case with no 404(b) discussion.

The fix

Attribute the quote to Haskins. For the Supreme Court standard, cite State v. Stager, 329 N.C. 278, 303 (1991).

Case holds the oppositeState v. WardCited “See also” for a rule the court rejected on those facts.+
What the brief said

Cited “See also” for the rule that a dismissed prior charge does not bar 404(b) evidence of the act.

What the source shows

Ward’s prior charges were dismissed by the judge for insufficient evidence. The court treated that as an acquittal, excluded the evidence, and ordered a new trial.

The fix

Cut it, or cite “But see” and distinguish: the Sellers prior was a DA dismissal, which Flaugher allows.

Wrong cite for the reversalState v. ElliottQuoting a dissent without the history that made it the law.+
What the brief said

Quotes Judge Lewis’s dissent at 288, then cites the Supreme Court’s reversal as “Id. at 644.”

What the source shows

“Id.” points back to the Court of Appeals opinion; the reversal is a separate case at 352 N.C. 663. The first dissent quote is at 287.

The fix

137 N.C. App. 282, 287–88 (2000) (Lewis, J., dissenting), rev’d per curiam, 352 N.C. 663, 664 (2000).

Wrong yearState v. CoffeyEasy to miss. Easy for opposing counsel or the court to catch.+
What the brief said

326 N.C. 268, 278 (1980), cited twice for the “rule of inclusion.”

What the source shows

Decided in 1990. The quote runs across pages 278–79, and the S.E.2d parallel is missing.

The fix

326 N.C. 268, 278–79, 389 S.E.2d 48, 54 (1990).

Why it mattersThese are the errors courts flag in AI-drafted briefs. People make them too. None of these would have been caught by checking that the case exists. They are caught only by reading the cited page.

Source: citations checked against opinion text on CourtListener, September 2026.