Resources
Short, honest guides for bringing skills into the tool you actually work in. What you import as-is, what you rebuild, and why.
Essentials
What a skill really is, in plain English for lawyers — and the two flavors that decide whether it travels.
Read →The distinction that tells you, for any tool, whether a skill gets imported or rebuilt.
Read →What .md is and why we prefer it — plain text, open, portable.
Read →Open an .md as a text file or with Obsidian.
Read →For your practice
A proportionate, defensible AI setup for a small firm: what Claude Team's DPA does (and doesn't) cover, what it costs, and what stays on you.
Read →Citations checked against real databases, not invented: what MCP is, and how BuddaLaw and Simpliciter power source verification.
Read →Tools
The native home of the format: a Skillagram skill already is a Claude skill — import it and go, nothing to rebuild.
Read →How Harvey’s equivalent of skills works — and how to rebuild a Skillagram skill inside it.
Read →Workflows and Playbooks: Legora’s take on skills, and how to bring yours in.
Read →No import/export: in Lexroom a “skill” is a repeatable way of working you set up by hand.
Read →Open, native format — and since July 2026 Codex lives inside ChatGPT too (Chat / Work / Codex).
Read →Gemini doesn’t import skills: rebuild them as a Gem — a custom assistant that starts out already briefed for your task.
Read →How Microsoft 365 Copilot’s equivalent of skills works — and how to rebuild a Skillagram skill inside it.
Read →Answers with sources cited: in Perplexity a skill is a repeatable Space you rebuild by hand.
Read →A consistent firm method from a European provider: in Le Chat a skill is rebuilt as an Agent — no import/export.
Read →