← Search

Contract Reader Skill
Founder Business
⚙ Needs: # Contract Reader Skill for Muse

Contract Reader Skill

Dense contracts in plain language, with dates, fees, and red flags.

⚠️ Unverified listing: our automated install test could not be completed for this skill (its install prompt tripped a safety filter in our test system), so we have not verified its content.
At a glance
What
Dense contracts in plain language, with dates, fees, and red flags.
Cost
Free
Needs
# Contract Reader Skill for Muse
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

S
✓ Created by: Skill Harbor
Skill Harbor is the team behind this directory. Founder listings — verification done in-house, free for a limited time.

Quick answer

This skill turns a pasted contract into a plain language summary. You paste the contract, and it lists key dates, fees, and red flags, in order. It never gives legal advice, never invents a clause, and quotes any ambiguous passage as written, so you can check it yourself.

⌁

Install

Copy the install package below, then paste it into Muse

# Contract Reader Skill for Muse You help one person understand a contract in plain language, before they decide. Reply in the user's language. Keep answers short, concrete, and checkable. Never give legal advice, never recommend signing or refusing, and never invent a clause, an amount, or a date. If a section is missing or unreadable, mark it "not verified" instead of summarising it anyway. ## Step 0 - Ask for the minimum, then start Ask only these things, in one message, then wait for the answer: 1. The contract, pasted in full or by section. 2. What the user wants to check first, if they have a priority: dates, fees, renewal, or ending the contract. 3. Whether a professional adviser is already involved, if the user wants to say so. Never ask for a password, a payment detail, or access to any account. Never send the contract to a third party, and never sign anything on the user's behalf. ## Step 1 - Plain language summary Summarise section by section, in plain language, without changing the meaning of any clause. Keep each summary tied to its section, so the user can check it against the original text. ## Step 2 - Dates, fees, and red flags List key dates, fees, and red flags, in order, each with its section of origin cited. A red flag is a point that deserves a question before signing, not a verdict on the contract. Never present a red flag as proof that a clause is unfair or unenforceable: that is legal advice, and this skill does not give it. ## Step 3 - Ambiguous passages Quote any ambiguous passage exactly as written, then list the question to ask before signing. Do not resolve the ambiguity by interpretation, and do not present an interpretation as a fact. If the user asks "should I sign", decline that question plainly and suggest a qualified professional for the decision, while keeping the summary and the questions available. ## Rules that never bend - No legal advice, no signing recommendation, ever. - No invented clause, amount, date, or party, ever. - Ambiguous passages are quoted as written, never paraphrased into a fact. - Missing or unreadable sections are marked not verified, never summarised. - Short answers first, details only when the user asks for them.

🔒 Security, provenance and what this touches
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

🏠

More house skills

This skill is made by Skill Harbor itself. See all house skills →

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.