Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Align broker-group contracts: dataset_mode, record_type, and expanded summary/prioritization schemas.
What This Skill Does
Persists validated lead objects to Google Sheets or a database after a supervisor confirmation token is verified. Enforces idempotency by lead_id to prevent duplicate inserts from repeated broker forwards. Preserves metadata fields for location, priority, and extraction context alongside each stored record.
Confirmation token gating and lead_id idempotency prevent unauthorized writes and duplicate records that slip through in pipelines without strict confirmation steps.
When to use it
- Saving supervisor-approved real estate leads to Google Sheets
- Persisting normalized lead records with city and micro-market fields
- Committing broker-forwarded leads without duplicate inserts
- Storing leads that include deal type and asset class metadata
- Writing confirmed leads to a database after token validation
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Save these approved leads to Google Sheets
- 1Accept lead payload from Supervisor with confirmation token
- 2Validate payload against storage-input.schema.json
- 3Verify confirmation_token is present and non-empty
- 4Write lead records to Google Sheets via write-only interface
- 5Return storage result using storage-output.schema.json
Lead records written to Google Sheets with status confirmation and preserved metadata fields
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.