Redlines against your playbook
Check a counterparty's redlines against your own contract playbook: accept what is inside your terms, hold what is not with the reason, and draft the reply for a person to review.
In Lobstack: Skills › Library › Add
What your agent will do.
A contract comes back marked up and someone wants to know what is fine, what is not, and what to say back.
- 01
Read the playbook first: each clause you care about, what you accept, your fallback, and what you never accept. With no playbook, stop and ask for one rather than inventing positions.
- 02
List every change in the redline with its clause and page.
- 03
For each, say accept, counter or reject, and quote the playbook line that decides it. A change the playbook does not cover is held for a person, not decided.
- 04
Draft the reply: what is accepted, each counter with proposed wording, and each rejection with a short reason.
- 05
Lead with anything touching liability, indemnity, payment, term or IP.
Draft only; nothing is signed or sent. Not legal advice.
The whole SKILL.md: 28 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: playbook-redline-checkdescription: "Check a counterparty's redlines against your own contract playbook: accept what is inside your terms, hold what is not with the reason, and draft the reply for a person to review."metadata: title: "Redlines against your playbook" category: legal tags: [legal, contracts]--- ## When to use this A contract comes back marked up and someone wants to know what is fine,what is not, and what to say back. ## How 1. Read the playbook first: each clause you care about, what you accept, your fallback, and what you never accept. With no playbook, stop and ask for one rather than inventing positions.2. List every change in the redline with its clause and page.3. For each, say accept, counter or reject, and quote the playbook line that decides it. A change the playbook does not cover is held for a person, not decided.4. Draft the reply: what is accepted, each counter with proposed wording, and each rejection with a short reason.5. Lead with anything touching liability, indemnity, payment, term or IP. Draft only; nothing is signed or sent. Not legal advice.
- Legal
Contract in plain words
Summarise a contract in plain words: who owes what, money and dates, renewal and exit, the clauses to look at twice. Not legal advice.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App - OperationsFeatured
Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
SKILL.md · App