Coding

Sentiment Priority Scorer RE-India

Score normalized real-estate leads using sentiment, urgency, intent, recency, and record type to produce deterministic priority rankings and P1-P3 buckets. U...

What it does

Score normalized real-estate leads using sentiment, urgency, intent, recency, and record type to produce deterministic priority rankings and P1-P3 buckets. U...

The skill document

Sentiment Priority Scorer

Produce deterministic priority scores for leads without mutating any state.

Quick Triggers

  • Rank leads by urgency and tone for callback priority.
  • Classify leads into P1/P2/P3 queue.
  • Score follow-up priority from normalized lead records.

india-location-normalizer -> sentiment-priority-scorer -> summary-generator

Execute Workflow

  1. Accept input from Supervisor containing normalized leads.
  2. Validate input with references/sentiment-priority-input.schema.json.
  3. Score each lead with:
    • sentiment_score in range [-1, 1]
    • intent_score in range [0, 1]
    • recency_score in range [0, 1]
    • mapped urgency_score from lead urgency (high=1.0, medium=0.6, low=0.3)
  4. Use record_type to avoid over-prioritizing generic bulk inventory:
    • buyer_requirement: apply +0.10 intent lift (hard demand signal)
    • inventory_listing: no lift unless high-action cues are present
  5. Boost intent_score when high-action cues exist in listing text:
    • immediately, keys at office, one day notice, possession, inspection any time
  6. Compute priority_score on a 0-100 scale:
    • priority_score = 100 * (0.40*urgency_score + 0.30*intent_score + 0.20*recency_score + 0.10*sentiment_risk)
    • sentiment_risk = max(0, -sentiment_score)
  7. Assign buckets:
    • P1 for priority_score >= 75
    • P2 for priority_score >= 50 and < 75
    • P3 for < 50
  8. Produce plain-language evidence tokens that explain the score, including record-type evidence.
  9. Validate output with references/sentiment-priority-output.schema.json.

Enforce Boundaries

  • Never write to Google Sheets, databases, or files.
  • Never send messages or trigger outbound channels.
  • Never create reminders or execute actions.
  • Never bypass Supervisor routing or approvals.
  • Never replace upstream urgency; only derive scoring fields.

Handle Errors

  1. Reject schema-invalid inputs.
  2. Return field-level reasons when scoring cannot be computed.
  3. Fail closed if required scoring features are missing.

Related skills

Normalize Indian real-estate location text into canonical city and locality fields (Mumbai and Pune v1) with confidence and unresolved flags. Use when leads...

35 installs

Generate daily or range-based lead summaries from read-only lead data. Use when users ask for todays lead summary, broker inventory counts, locality trends,...

41 installs

Generate non-binding follow-up action suggestions from lead summaries or lead lists. Use when users ask for next best actions, call list for hot leads, or fo...

45 installs

Extract structured real-estate lead records from parsed message objects. Use when users ask to find leads in WhatsApp exports, extract name-phone-budget, or...

49 installs

PRD review stress-test simulator: 5 cross-functional roles challenge your requirements and outputs a scored HTML or Markdown survival report with radar chart...

32 installs1 stars

Generate comparative market analysis (CMA) and home valuation reports from IDX listing data and selected comparable properties. Use when a user wants to pick...

47 installs