Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ferroxlabs/wayland-contract-review
Triage a contract end-to-end: identify the contract type, run a clause-by-clause risk review with severity flags, propose red-lines, and produce a counsel-routing list of clauses that require attorney sign-off before execution.
Passed 20 of 23 test cases with the skill, and 12 of 23 without it.
and 11 more in the full report
9 fixed11 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need help reviewing an upcoming commercial lease agreement with Westside Holdings in Texas involving $500k in total commitments. I'm particularly worried about indemnification and early termination penalties. Please run a full risk triage on this document: classify the agreement type, rate each clause's risk level, draft paste-ready redlines for any clauses that need negotiation, and build an attorney escalation list for final legal gatekeeping.
| Checked | Without skill | With skill |
|---|---|---|
| Prompts the user to supply the contract body text before running the review steps. | Missed | Passed |
| Refrains from outputting clause risk ratings or redline revisions prior to receiving the agreement text. | Missed | Passed |
The instructions your model reads when the skill loads.
Estimated time: 20-30 minutes
This workflow triages a contract before it is signed. It identifies the contract type, performs a clause-by-clause review with red/yellow/green severity flags, proposes concrete red-lines, and builds a counsel-routing list naming every clause that requires attorney sign-off before execution.
This is triage and drafting support. It does not replace a licensed attorney. The final deliverable is a Contract Review Memo whose counsel-routing section is a required gate before the contract is executed.
Step 1: Intake the Contract (uses: legal-contract)
Ask the user to paste the full contract text (or provide a path to the file). Request the specifics that change the risk profile: the counterparty, the governing jurisdiction, the dollar value at stake, and any specific concerns the user already has. Do not proceed until you have the contract body and at least the jurisdiction and counterparty.
Step 2: Identify the Contract Type (uses: legal-contract)
Infer the contract type (e.g. MSA, SOW, license, vendor agreement, employment, lease) and the standard structure baseline a contract of that type should follow. State the inferred type plainly, give the reasoning, and ask the user to confirm
test cases passed, vs 12 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.