Menu
Retrieve the approved clause, its variants and the fallback position.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vstorm-co/agenticos --skill contract-clause-libraryThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | Contract clause library |
| description | Retrieve the approved clause, its variants and the fallback position. |
| category | legal |
The point of a clause library is that people stop drafting from memory. That only works if retrieval gives the whole position.
The preferred clause, verbatim · the approved variants, with when each is used · the fallback position and the floor below which it goes to a partner · the drafting notes — why it is worded that way, and what breaks if it is changed.
"Approved down to a 12-month cap; below that, partner sign-off" is the useful part. A clause without its negotiating range gets conceded.
Say which version this is, when it was last reviewed, and which jurisdictions it was approved for. A clause approved for one jurisdiction is not automatically right in another.
Say so. Do not adapt the nearest one — that is drafting, and it needs a fee earner.
Return a clause from a previous matter as though it were approved, or a variant whose review date has passed without saying so.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.