Skip to content
TakoAPI
Back to skills

lead-storage

by vishalgojha

Coding Agents & IDEs
400Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Persist validated lead objects through write-only storage operations after Supervisor provides explicit confirmation.

Description

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

INPUT

User asks: Save these approved leads to Google Sheets

AGENT
  1. 1

    Accept lead payload from Supervisor with confirmation token

  2. 2

    Validate payload against storage-input.schema.json

  3. 3

    Verify confirmation_token is present and non-empty

  4. 4

    Write lead records to Google Sheets via write-only interface

  5. 5

    Return storage result using storage-output.schema.json

OUTPUT

Lead records written to Google Sheets with status confirmation and preserved metadata fields

Requirements

  • Google account with access to Google Sheets

Installation

clawhub install vishalgojha/lead-storage

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links