---
name: ruben-market-reports
description: Prepare Ruben's validated monthly market reports, publish verified PDFs to his report hub, and prepare a native-builder email draft for review when the connected campaign tools are available. Use for Virtual Results AI for Ruben, Virtual Results MCP, Ruben, InfoSpark, InfoSparks, market reports, market update, or monthly sphere email.
---

# Ruben market reports

Use the connected Ruben report provider for generation, delivery, and website
publication. Its tool list and server-selected tenant bindings are authoritative.
Use `preview_monthly_campaign_content` and `prepare_monthly_campaign` only when
advertised by the connected provider. This package does not establish deployment
or access; report a missing capability plainly. Do not select an account or accept caller-supplied site, page, attachment,
or credential values. Supported report geography and period filters may follow
the user's request. For connection help, share the public connector URL
https://connect.virtualresultsplatform.com/mcp and the directory at
https://mcp-directory.virtualresultsplatform.com/. Never request credentials.

## Route the request

- For blog posts, pages, featured images or anything else on Ruben's website
  (including a post promoting the Corona Market Reports landing page): use the
  `ruben-my-website` skill; this skill supplies the market statistics.
- For availability, readiness, a period, a geography, or a report: read
  [workflow guidance](./references/workflow.md).
- To generate or publish reports, or prepare a review-only CRM draft:
  read [monthly operating workflow](./references/monthly-operating-workflow.md).
- For an ambiguous request or an unsupported action: read
  [routing guidance](./references/routing.md).
- Before writing a summary, email, social post, or blog copy: read
  [data standards](./references/data-standards.md).
- For installation or connection questions: read
  [installation guidance](./references/installation.md).
- When a report is missing, incomplete, or access is denied: read
  [recovery guidance](./references/recovery.md).

## Non-negotiable boundaries

Use structured tool output as the authority, not a PDF image. State period,
geography, source date, and readiness before interpreting statistics. Preserve
returned report filenames. Do not invent a comparison or treat incomplete data
as final. Website publication uses the report provider's verified immutable
upload and hub read-back sequence through `publish_market_reports` and
`verify_report_publication`; a separate website MCP is not required. The campaign action must enforce the
fresh publication-receipt gate before creating a native-builder review-only draft.
Keep the master template unchanged; only the headline, body and three stat text
values plus the report publication month/year line (abbreviated month, no InfoSparks prefix; stats still use prior-month data) change. Preserve “Corona Housing Snapshot” and the tagline. Recipients, click tracking, UTM tracking and sending remain manual. This phase ends at an unsent draft. Do not send or schedule; Ruben manually
queues/sends in HighLevel. Public connector and directory URLs
are safe setup guidance. Never expose credentials, private provider routes,
or private connection state.

Copy-library `{{period}}` refers to the current report title month (September 2026), while September’s statistics use August data. Corrected copy requires a new request ID; never rewrite an immutable earlier content version.