Skills in Legora
How Legora's equivalent of skills works — and how to bring a Skillagram skill into it.
The short version
Legora doesn't have a portable "skill" file you import or export. Its equivalents are Workflows (multi-step agentic tasks) and Playbooks (your firm's standards the AI checks against). You build them in plain language, share them within your firm, and can push them to clients through Portal. None of that moves between vendors as a file.
So on Skillagram, a Legora skill is shared as instructions you rebuild in Legora, not a file you drop in.
What Legora calls a "skill"
| Skillagram term | Legora's equivalent |
|---|---|
| A skill (a task method) | A Workflow |
| Firm standards / fallback positions | A Playbook |
| A skill shared to a client | A workflow exposed via Portal |
Legora Workflows are agentic: you give a high-level goal in natural language, and the system plans and executes step by step — and a single workflow can call multiple tools (tabular review, web search for case law, citation checks against a legal database) in one run.
Building a skill in Legora (the realistic "import")
When you find a skill on Skillagram you want in Legora, you recreate it as a Workflow:
- Open Workflows and choose to build a new one — in plain language or the visual builder.
- Lay out the steps from the skill's instructions: extractions, conditionals, role-based permissions, the tools each step should call.
- Attach the relevant Playbook if the skill checks documents against firm standards (e.g. against your GTC/DPA).
- Run it on a sample document set and compare against the skill's expected output.
- Iterate based on your own testing and team feedback, then save it to your firm's library.
Tip: Legora ships a collection of pre-built workflows alongside your firm's own. Before rebuilding a skill from scratch, check whether a close pre-built match already exists that you can adapt — it's often faster than starting clean.
Sharing a skill you built in Legora
Two directions:
- Within your firm — save it to the library; teammates run it without rebuilding.
- To clients — via Portal, Legora's firm-to-client layer. Firms can build a custom workflow (say, contract review against a firm playbook) and let clients run it directly in a secure, branded space. This is genuinely useful and genuinely Legora-only — the client needs Legora access; it isn't a portable file.
To publish on Skillagram, export the human-readable instructions: the steps, the tools each calls, the playbook logic, and a sample input/output. That's what another firm rebuilds.
What "export" does not mean in Legora
Legora's Export refers to exporting an output — to Word, PDF, or straight to your DMS. It does not export the Workflow definition as a portable file. Different thing.
The portability reality
Legora has staked out the "agentic OS" / orchestration position and is moving on MCP, but — as with its peers — that's about connectivity to documents and data sources, not exporting skill definitions to other tools. A Legora workflow stays in Legora (or reaches a client through Portal). Skillagram carries the method so it can live anywhere.
Product features change quickly. If Legora's interface has moved since this was written, check Legora's in-app help or your firm's Legora contact for the current steps.