From re-assistant
This skill should be used when a user asks to "analyze disclosure documents", "summarize the disclosure package", "review the disclosures", "create a disclosure summary", "analyze the inspection reports", "run a disclosure review", or when the user uploads disclosure PDFs for a property. Produces a structured, client-ready Disclosure Package Summary covering title, inspections, permits, seller disclosures, and a repair cost summary. Designed for San Francisco residential real estate transactions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/re-assistant:disclosure-package-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a structured, bullet-only Disclosure Package Summary from uploaded disclosure PDFs. Output is ready to paste into Google Docs and follows the 13-section format defined in `references/output-template.md`.
Produce a structured, bullet-only Disclosure Package Summary from uploaded disclosure PDFs. Output is ready to paste into Google Docs and follows the 13-section format defined in references/output-template.md.
Before doing anything else, read ~/.claude/re-assistant.local.md using the Read tool.
If the file does not exist or agent_name is not set in the YAML frontmatter, stop and tell the user:
"This plugin requires setup before use. Please run
/re-assistant:setupto save your agent profile, then try again."
If the file exists and agent_name is set, extract these values from the YAML frontmatter and keep them available for use in output headers or agent attribution:
agent_nameteam_name (may be empty)brokerage_nameagent_emailAsk the user for the following. Accept whatever is available; infer the rest where possible:
Assume San Francisco, CA unless the user states otherwise.
Ask the user to attach or upload all disclosure package PDFs. Accept whatever is provided. Common documents include:
If only non-inspection documents are provided (e.g., title report only), proceed with the available sections and note which inspection sections could not be completed.
Calculate the following before writing:
Repeat all numbers exactly as written in source documents, with units (sf, $, %, amps, etc.).
Search Realtor.com, Zillow, or Redfin for the property address to find confirmed bedroom, bathroom, and price data for the executive summary. If web search is unavailable, skip this step and rely on MLS data provided by the user in Step 1.
Process uploaded documents in this order. Skip any type not present — do not note its absence:
When a report uses strong or precise language, include short exact quotes (3–20 words) in quotation marks — prioritize high-signal language, do not overquote. Write "Not found in uploaded docs" when information is missing. Do not guess.
Write the output using the 13-section structure defined in references/output-template.md. Verify all calculations before output.
Output rules:
npx claudepluginhub betoiii/betos-plugin-marketplace --plugin re-assistantCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.