---
name: paperwork-operator
description: Prepare, revise, organize and send real estate paperwork through the user's existing WebForms, SkySlope via REALM, or chosen paperwork portal, using their licensed forms, brokerage templates and native signing workflow. Use for offers, listings, representation, leases, amendments, notices, releases, signbacks and signing-status requests.
secrets: []
timeout_seconds: 30
params:
  type: object
  properties:
    section:
      type: string
      enum: [start, webforms, skyslope, fields-and-signing, harness]
      description: Load the relevant operator guide. This tool returns instructions; it does not operate the portal.
      default: start
---

# Paperwork operator

Work inside the realtor's existing paperwork system using the Homies browser. The portal holds the transaction, current licensed forms, templates, signing invitations and signed records. This skill supplies instructions and semantic checks; browser tools perform the work. Do not route this workflow through Homies Paperwork API, generate-offers, Homies esign, a provider API, or a replacement PDF generator. Other connected records may supply verified facts. Change document platforms only when the user explicitly chooses to.

## Begin with the user's task

Use the conversation, saved agent/brokerage profile and relevant existing file. Ask only for missing information, one simple question at a time. Default starter: “Help me with my paperwork.” If the task is unclear, offer a listing, offer, lease, representation, amendment/notice, cancellation/re-list, signing, or another document. Users do not need form numbers. Support any document available in their authorized library or existing file, including commercial and brokerage-specific work; do not promise every form or action is available.

Reuse a saved portal preference when it belongs to this user. Otherwise ask “Which paperwork system do you use?” with WebForms, SkySlope through REALM, or their chosen system. A named platform in the request takes precedence. Establish jurisdiction, party represented, property/transaction type and the existing file only where missing. New files do not require an MLS number.

Read [the harness guide](references/harness.md) for browser handoff, persistence and installation. For WebForms read [the WebForms guide](references/webforms.md); for SkySlope/REALM read [the SkySlope guide](references/skyslope.md). Load [fields and signing](references/fields-and-signing.md) before choosing execution fields or preparing a signing. The guide tool can return these references when file reading is unavailable. For a different portal, inspect its actual native workflow and apply the common steps below; do not substitute either known adapter's selectors or login.

## Prepare in the existing file

1. Open the user's supported persistent browser. Inspect the actual page and follow legitimate sign-in/SSO. For credentials, 2FA, CAPTCHA or security challenges, provide the secure live browser handoff; never ask for a password, PIN or code in chat. Resume the same file after authentication. A remembered device is provider-controlled, not a promise of uninterrupted login.
2. Confirm the active user/brokerage and locate the existing transaction by reliable identifiers before creating a new one. On retries, inspect what was saved; do not duplicate transactions, forms or envelopes. Retain a minimal private checkpoint: portal, transaction link/ID, current document revisions, last verified state and outstanding decisions. Never store cookies or credentials in a skill or checkpoint.
3. Prefer the user's transaction template, brokerage form set, approved clauses and signing template. Apply a copy to this file; preserve the source template. Inspect every carried-forward value and remove stale client facts from the new copy. Validate current library access, form number/title, printed revision, purpose and jurisdiction. Older printed years can still be current. A familiar form number does not prove suitability. Resolve uncertain legal effect with the realtor or their brokerage; do not invent a clause or waive a protection.
4. Read the selected forms and schedules before asking for terms. Maintain a private checklist of field meaning, source, proposed value, status and execution stage. Use explicit current instructions and the relevant executed agreement/amendments, then verified transaction records and saved profile. Surface conflicts. MLS data alone does not establish ownership, signing capacity, signing email or negotiated terms.
5. Fill verified values through native controls, imports and auto-population. Inspect labels, units, selections and actual saved values rather than trusting repeated field names. Preserve standard wording and execution blocks. Leave unknowns empty where allowed; never insert fake names, dummy email addresses or made-up dates to pass validation. Save useful partial drafts. Report the actual required field if the portal blocks saving.
6. Save and reopen/read back the changed forms. Inspect every page and schedule, including overflow, checkboxes, names, dates and signature blocks. Export to the user's private workspace if supported; verify the actual export before linking it. When only an in-portal draft is available, provide its link and state that limitation. Distinguish a saved draft from an executed agreement.

## Match the transaction, not a fixed form list

- Listing/representation: scope, represented parties, capacity, dates, price where applicable, total brokerage remuneration versus cooperating amount, fixed versus percentage, taxes as directed, holdover, exclusions and approved schedules.
- Purchase/lease: price/rent, deposit holder and timing, closing/possession or term, irrevocability and timezone, conditions/deadlines, inclusions/exclusions, rental items, representation and relevant disclosures.
- Cancellation/re-list: identify what ends, effective date/time, continuing obligations or release choices, and the separate new agreement's terms. Cancelling an agreement, cancelling an MLS listing and releasing liability are distinct actions. “Same commission” requires the actual agreement, not just the MLS co-op figure.
- Amendment, signback, notice, waiver or release: preserve the original and subsequent amendments; identify the exact change, chosen instrument, deadlines, affected parties and necessary consents. Use the platform's amendment/revision workflow. Existing signatures do not approve changed terms. Never choose a waiver or release for the user.
- Commercial, business, disclosures, compliance and other paperwork: derive questions from the actual form, authorized records and professional direction. Do not force residential assumptions or substitute one jurisdiction's forms for another's.

Resolve relative dates to explicit dates in the transaction timezone; do not roll expired deadlines forward. Do not turn an effective date, acceptance-event time or receipt acknowledgement into the date of signing. If an instruction has no matching field, keep it in the review notes and ask how it should be documented; a note is not an operative term.

## Prepare, approve, send, then verify

Drafting does not require signer emails if the platform permits an unsigned draft. When signing is requested, prepare the native envelope using the final saved documents and the user's existing signing provider. Apply the compatible saved signing template and inspect every tag. Read the fields-and-signing guide for recipients, execution stages and the final package review.

Show the exact document versions, recipients/capacities/emails, signing order, applicable fields, subject/message and any expiry/reminders. Obtain approval of this concrete package and authorization to send; retain any approval already given for the unchanged package instead of repeatedly asking. Changes to documents, recipients, material fields or delivery invalidate that approval. Click the actual final send control only within that authorization. Do not sign or initial for recipients, accept their consent, waive identity checks, or treat inviting as completion.

After send, verify the native envelope ID/link and displayed recipient/delivery state. If the result is uncertain, inspect the existing envelope/activity before retrying; do not create another or send twice. Follow up through native status. After all required parties complete, verify the provider's completed state and signed document, retain the completion certificate/audit record when available, and file them in the original transaction. Sending a notice or delivering an offer to the other side, filing with a regulator, changing MLS status, voiding an envelope, sending reminders and sharing externally are separate actions requiring the user's corresponding instruction.

Finish each stage with private links, the actual saved/sent/completed status and the remaining decisions. A browser blocker should name the failed step and preserve progress. Never claim platform access, installation, a saved file, delivery, signature, filing or legal completion without the corresponding evidence.