🧪 Skills

AgentZero

Interact with the AgentZero real estate listing tracker (local Rust/Axum backend at http://localhost:8000). Use when asked to add a property listing by URL,...

v1.1.0
❤️ 0
⬇️ 67
👁 2
Share

Description


name: agent-zero description: Interact with the AgentZero real estate listing tracker (local Rust/Axum backend at http://localhost:8000). Use when asked to add a property listing by URL, refresh an existing listing, or list search profiles/scenarios. AgentZero parses Redfin and REW.ca URLs; Zillow and Realtor.ca are blocked (saves stub only). The Daily Email Scan workflow reads Redfin alert emails via himalaya (IMAP) and opens Gmail in the openclaw browser to extract listing URLs — explicit user consent and himalaya configuration are required before use. After any action, log a summary to agent_zero_logs/YYYY-MM-DD.md in the workspace. metadata: openclaw: requires: bins: - himalaya - openclaw localServices: - name: AgentZero backend url: "http://localhost:8000" note: "Rust/Axum server — must be running before invoking any listing API workflows" - name: AgentZero frontend (optional) url: "http://localhost:5173" note: "Vite/TypeScript UI — optional, used for reviewing listings" credentials: - name: himalaya Gmail config description: > himalaya must be configured with an IMAP/SMTP account pointing to the user's Gmail inbox. The app password or OAuth token must be stored in the system keychain or himalaya config file. Without this, the Daily Email Scan workflow will fail. configPath: "/.config/himalaya/config.toml" keychain: true privacy: emailAccess: true browserAutomation: true note: > The Daily Email Scan workflow reads Redfin alert emails from the user's Gmail inbox via himalaya, opens Gmail in the openclaw browser, clicks listing links, and records email IDs and thread URLs to /.openclaw/workspace/agent_zero_logs/. This is intentional — the workflow is explicitly user-triggered (cron or manual) and scoped to Redfin sender emails only (from:redfin.com). No email body text is stored; only listing URLs and envelope metadata (ID, subject) are logged. writes: - "/.openclaw/workspace/agent_zero_logs/YYYY-MM-DD.md" - "/.openclaw/workspace/agent_zero_logs/processed_emails.json"

AgentZero Skill

AgentZero is a personal real estate listing tracker. Backend at http://localhost:8000.

Prerequisites

Before using this skill, ensure the following are in place:

Requirement Details
AgentZero backend Must be running at http://localhost:8000 (Rust/Axum). Start with ./scripts/run_backend.sh in the project directory.
himalaya CLI email client — must be installed (brew install himalaya or similar) and configured with your Gmail account via IMAP. Config at ~/.config/himalaya/config.toml.
himalaya credentials Gmail app password or OAuth token stored in keychain. Required for the Daily Email Scan workflow.
openclaw browser Used by the Daily Email Scan to open Gmail and click listing links. Start with openclaw browser --browser-profile openclaw start.
AgentZero frontend (optional) Vite UI at http://localhost:5173 for reviewing listings. Start with ./scripts/run_frontend.sh.

Privacy & Email Access

The Daily Email Scan workflow accesses your Gmail inbox. Specifically it:

  • Reads envelope metadata (subject, sender, ID) of Redfin alert emails via himalaya envelope list
  • Opens Gmail in the openclaw browser to click through listing links (no email body text is read or stored)
  • Records processed email IDs and listing URLs in ~/.openclaw/workspace/agent_zero_logs/

This is opt-in: the scan only runs when explicitly triggered (cron or manual) and is scoped to from:redfin.com emails only. If you do not want email or browser access, use only the Add Listing by URL and Refresh workflows, which require no email access.


Key APIs

Action Method Endpoint Body / Params
List search profiles GET /api/search-profiles
Add listing (AI) POST /api/listings/suggest {"url": "...", "search_profile_id": N}
Refresh listing PUT /api/listings/:id/refresh
List all listings GET /api/listings ?status=...&search_profile_id=N
Get single listing GET /api/listings/:id

Responses are JSON Property objects (see field list below).

Workflow: Add a Listing by URL

  1. GET /api/search-profiles to fetch all profiles.
  2. Read each profile's title + description. Pick the best fit based on property type, location, price, and size from the URL or page context.
  3. If no profile fits, log a skip message in the daily notes file and tell the user why. Do NOT add the listing.
  4. POST /api/listings/suggest with {"url": "<url>", "search_profile_id": <id>}.
  5. On 409 CONFLICT response: the listing already exists. Parse the JSON body for existing_id and existing_title and report to user.
  6. On success: log a summary to the daily notes file (see Logging section).

Supported URL sources: redfin.ca, redfin.com, rew.ca (parses fully). zillow.com, realtor.ca (saves stub only — inform user).

Workflow: Refresh a Listing

  1. If given a listing ID directly, use it. Otherwise GET /api/listings and find the matching listing by title or address.
  2. PUT /api/listings/:id/refresh (no body).
  3. Log the result to daily notes.

Workflow: List Search Profiles

  1. GET /api/search-profiles
  2. Present each profile with id, title, description, and listing_count.

Logging — agent_zero_logs/

After every action (add, refresh, skip), append a summary to:

~/.openclaw/workspace/agent_zero_logs/YYYY-MM-DD.md

Create the folder and file if they don't exist.

Format:

## HH:MM — Added listing #38
- **Email:** https://mail.google.com/mail/u/0/#inbox/<thread_id>
- **Title:** 7778 Nanaimo St, Vancouver - 6 beds/3.5 baths
- **URL:** https://www.redfin.ca/...
- **Profile:** East Van House (id=1)
- **Price:** $2,198,000
- **Status:** Pending

## HH:MM — Skipped listing
- **Email:** https://mail.google.com/mail/u/0/#inbox/<thread_id>
- **URL:** https://...
- **Reason:** No search profile matches — listing is in Burnaby, all profiles target Vancouver.

The thread_id is the hex ID visible in the Gmail URL after opening the email in the browser.

Key Property Fields

id, title, price, street_address, city, bedrooms, bathrooms, sqft, land_sqft, property_tax, mortgage_monthly, monthly_total, status, redfin_url, rew_url, mls_number, search_profile_id

Workflow: Daily Email Scan (Cron)

This is the workflow for the scheduled daily cron task.

Requires: himalaya configured with Gmail + openclaw browser running. See Prerequisites above.

Step-by-step

  1. Notify your user (via whatever messaging channel is configured): "🏠 AgentZero daily scan starting — checking Redfin emails..."

  2. Write scan-start entry to ~/.openclaw/workspace/agent_zero_logs/YYYY-MM-DD.md immediately (create file/folder if needed):

    ## HH:MM — Scan started
    - Checking Redfin emails...
    
  3. Load state file ~/.openclaw/workspace/agent_zero_logs/processed_emails.json

    • If missing, treat as {"processed_ids": [], "date_counts": {}}
    • Format: {"processed_ids": ["57471", ...], "date_counts": {"2026-03-09": 2}}
    • processed_ids are himalaya envelope IDs (sequential integers) — used to avoid re-processing emails already handled in previous scans
    • Append to log:
      ## HH:MM — Loaded state
      - Already processed IDs: 57471, 57457
      - Processed today: 1
      
  4. Check daily limit: count how many emails were processed today (from date_counts[today]). If ≥ 3, append to log and notify your user:

    ## HH:MM — Skipped scan
    - Reason: Daily limit (3) already reached.
    
  5. List Redfin emails via himalaya:

    himalaya envelope list --output json 2>/dev/null
    

    Filter to emails where from.addr contains redfin.com and ID is NOT in processed_ids. Take up to 3 - already_processed_today.

    Append to log immediately:

    ## HH:MM — Found N new Redfin email(s)
    - Email IDs: 57493, 57490
    - Already processed today: 1 (limit: 3)
    
  6. For each email:

    a. Append to log before opening:

    ## HH:MM — Processing email <id>: "<subject>"
    - Opening in Gmail...
    

    b. Open the email in Gmail via browser (run openclaw browser --browser-profile openclaw start if not already running):

    • Navigate to Gmail and search using the subject and sender from the himalaya envelope (e.g. from:listings@redfin.com subject:"<subject from step 5>")
    • Click the matching email to open it

    c. For each listing link visible in the email body:

    • Skip "Go tour it", "Tour home", "Schedule a Tour", and "View all saved open houses" links — these go to booking pages, not listings
    • Skip full address links (e.g. "930 Cambie St, Vancouver, BC, V6B 5X6") — these go to Google Maps
    • Click the short property name links (e.g. "7778 Nanaimo St" or "2094 E 7th Ave") — these are the actual Redfin listing links
    • Read the final URL from the new tab (e.g. https://www.redfin.ca/bc/vancouver/.../home/200788210)
    • Close the tab
    • ⚠️ Never construct or guess URLs. Only use URLs extracted directly by clicking through the email. Do not derive URLs from propertyId params or address strings.
    • Append to log before submitting:
      - Found listing URL: https://www.redfin.ca/...
      - Submitting to AgentZero...
      
    • Submit via Add Listing workflow above (auto-select search profile)
    • Append result to log immediately after each listing (success, skip, or 409)

    d. Mark email as processed:

    • Update processed_ids in state file with this email ID
    • Increment date_counts[today]
    • Add agent_zero label in Gmail via himalaya:
      himalaya message copy <email_id> "agent_zero"
      
    • Append to log:
      - Email <id> marked as processed.
      
  7. Append final summary to log:

    ## HH:MM — Scan complete
    - Processed N emails, added M listings (K skipped).
    
  8. Notify your user with summary and a prompt to review new listings in the frontend:

    ✅ AgentZero scan complete — processed 2 emails, added 3 listings (1 skipped: no matching profile).
    
    🏡 New listings are ready to review: http://localhost:5173/inbox
    

State file location

~/.openclaw/workspace/agent_zero_logs/processed_emails.json

Reviews (0)

Sign in to write a review.

No reviews yet. Be the first to review!

Comments (0)

Sign in to join the discussion.

No comments yet. Be the first to share your thoughts!

Compatible Platforms

Pricing

Free

Related Configs