On a check-in call this week, Chris Salamé-Albrigo described the exact problem this release kills. Chris is the fractional CRO at Flisk, and he runs contracts for the bootstrapped AI startup and a stack of consulting clients. He’d just spent part of a day wrestling an agent that forgot everything it knew about his business the moment the model underneath it changed.
“What I don’t want to do every time is copy and paste in a part of the prompt of like, hey, remember it’s this business, dummy. This is what they do. I don’t need terms on X, Y and Z.”
Chris Salamé-Albrigo, Fractional CRO at Flisk
Chris has a workaround. When he starts with a new AI tool, he uploads his own skill files in markdown and tells the tool to commit them to memory. It works until the model changes or a teammate starts a fresh chat. Then the context is gone and the output slides back to generic “best practice” that doesn’t fit the deal in front of him.
AI Skills fix that. A skill packages how your team handles a task, like marking up an NDA or hunting down renewal terms, so it runs the same way for everyone, whichever model is doing the work.
The GitHub sync is the part that changes how a legal team works. The way your sharpest reviewer handles a returned MSA gets written down in a file instead of living in their head or a stale chat thread. Your team reviews changes to that file, Aline pulls the update overnight, and the next morning everyone runs the new version with one keystroke.
Saved prompts are now AI Skills. If you saved prompts in Aline before, they’ve already been converted. A skill carries your team’s steps for a task, along with the templates and fallback language that go with it, and it runs those steps in order.
Skills come in two groups:
When you update a skill, everyone who runs it gets the new version automatically.
Import skills from GitHub. Admins can connect a public GitHub repository and bring its skills into Aline:
| What happens | How it works |
|---|---|
| Selection | Aline lists every skill in the repo. You pick which ones to import. Nothing comes in automatically. |
| Daily sync | With automatic sync on, Aline checks the repo once a day for new and updated skills. |
| Local edits | Importing the GitHub version replaces edits made in Aline. Earlier versions are kept, so nothing is lost. |
| Removed skills | If a skill is deleted from the repo, you decide whether to delete it from Aline. |
The repo can be your own or a public library. awesome-legal-skills, for example, lists 276 skills across 28 practice areas, contributed by practicing lawyers, in-house counsel and legal technologists. Connect it and you can run NDA triage, GDPR breach assessment and EU AI Act screening the same afternoon without writing a line yourself, then tune each one to your positions.
202
ready-to-run legal skills imported from one public GitHub repo in a single pass, with 79 more flagged as invalid instead of slipping through
Aline demo workspace connected to lawve-ai/awesome-legal-skills, November 2026
Those are the numbers from our own workspace. Anthropic’s claude-for-legal repo connects the same way, so the skills Anthropic publishes for legal work can sit right next to your team’s.
We’re most excited about this part. A legal team turning on AI used to start from an empty prompt box. With a connected repo, it starts from skills that practicing lawyers and in-house counsel have already written for the same tasks.
The first time you run a skill someone else wrote, open it and read it. Imported skills carry their author’s assumptions, and those may not match your matter.
From then on, edit the skill in GitHub. A pull request becomes the sign-off for changing how your team marks up a contract, the commit history shows who changed what and why, and the next sync puts the new version in front of everyone. We think that’s the fun part.
Here’s the whole flow in two and a half minutes:
These are skills our customer success team built with customers on onboarding calls in the last few weeks:
| Skill | What it does | Who built it |
|---|---|---|
| NDA review, first or second pass | Asks at the start whether this is a first-pass review or a review of returned redlines, then runs the matching steps | In-house legal team at a public tech company |
| Auto-renewal check | Flags any automatic-renewal clause of 12 months or longer across a set of agreements | Operations team at an auto dealership group |
| Plain-English margin comments | Runs after first-pass review and explains each redline in plain English for the business stakeholder | In-house legal team |
| Repository agreement updater | Searches the repository for matching agreements, proposes the templates needed, flags duplicates and asks for approval before generating anything | Same team as above |
We treat skills and playbooks as different tools, and we think teams get better results when they keep them separate.
A playbook is a checklist of positions. It’s structured and predictable, and it’s the right tool for a first-pass review of an agreement type you see every week.
A skill is a sequence of steps with judgment in between. Use it for the unusual agreement, the one-off analysis, or anything that isn’t a list of positions. It is also the better tool for returned redlines, because a playbook re-examines the whole document while a skill can focus on what the counterparty changed.
A skill can’t tag a playbook, so if you want a skill to apply your playbook rules, ask the chat to list the rules and build them into the skill.
Putting skills in GitHub follows from that view. Your playbook positions change slowly. Your skills will change every time a partner, GC or ops lead finds a better way to run a task, and that kind of change deserves the same review and history your engineers get for code.
AI Skills and GitHub import are live in every Aline workspace today. Type / in AI Chat to see the community skills, or have an admin connect your first repo under Settings → Skills. The full walkthrough is in the help center: Using the AI Chat to Review & Redline Contracts.
If you’re not on Aline yet, start a 14-day free trial, no credit card required, and bring the skills you already wrote for other tools. Or book a demo and get 2 months free.
