Skills in Harvey
How Harvey's equivalent of skills works — and how to bring a Skillagram skill into it.
The short version
Harvey doesn't have a portable "skill" file you import or export. What it has is Agent Builder (you may have known it as Workflow Builder), where you create Workflow agents — reusable, multi-step agents that capture how your firm does a task. You share them within your Harvey workspace; you don't move them between firms or other tools as files.
So on Skillagram, a Harvey skill is shared as instructions you rebuild in Agent Builder, not a file you drop in.
What Harvey calls a "skill"
| Skillagram term | Harvey's equivalent |
|---|---|
| A skill | A Workflow agent built in Agent Builder |
| A clause bank / reference | Embedded sources inside the workflow |
| Standardized review method | A Playbook |
Workflow agents can run multiple steps, pull from your Vault or DMS, choose models per step, and apply your firm's precedent and logic.
Building a skill in Harvey (the realistic "import")
When you find a skill on Skillagram you want in Harvey, you recreate it in Agent Builder:
- Open Agent Builder in your Harvey workspace.
- Describe the workflow in plain language, or use the no-code interface to lay out steps by connecting blocks — following the skill's instructions from Skillagram.
- Add your firm's know-how: inputs, precedent examples, branching logic, and any embedded sources (e.g. a clause bank the skill references).
- Pick the model for each step, or let Harvey optimize automatically.
- Test it on a sample document and compare against the skill's expected output.
- Submit for approval, then have an admin grant run access — to specific users or the whole workspace.
Heads-up on permissions: publishing a Workflow agent activates it, but people still can't see or run it until an admin sets run access under workspace settings. If a colleague says "I can't find the agent you shared," this is almost always why.
Sharing a skill you built in Harvey
Sharing happens inside your workspace, governed by permissions:
- Agent Builders can create agents, collaborate on drafts, and submit for admin approval.
- Admins approve publication and grant view/run access.
- Once live, teammates run it from the Library — no rebuilding on their end.
To share outside your firm — e.g. to publish on Skillagram — you export the human-readable instructions: the steps, the logic, the sources it relies on, and a sample input/output. That's what another firm rebuilds on their side.
What "export" does not mean in Harvey
Harvey's Export button refers to exporting an output — a finished draft as Word, Excel, or PowerPoint. It does not export the Workflow agent itself as a portable file. Worth knowing, because the wording trips people up.
The portability reality
Harvey is investing in MCP and DMS integrations (iManage, SharePoint), but that connectivity is about feeding agents the right documents and matter context — not about importing or exporting skill definitions across vendors. For now, a Harvey skill stays in Harvey. Skillagram bridges the gap by carrying the method so it can be rebuilt anywhere.
Product features change quickly. If Harvey's interface has moved since this was written, check Harvey Academy or your firm's Harvey admin for the current steps.