← Back to Skills Marketplace
danielfoch

GHL CRM for Realtors

by danielfoch · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
795
Downloads
2
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install ghl-crm-for-realtors
Description
Manage realtor tasks in GoHighLevel CRM including contact search and updates, pipeline tracking, messaging, calendar slots, and workflow enrollment via API v2.
README (SKILL.md)

GHL CRM for Realtors

Use this skill when a user wants realtor CRM actions in GoHighLevel (GHL), including lead follow-up, pipeline movement, appointment booking context, and messaging workflows.

Required Environment

Set these variables before running the scripts:

  • HIGHLEVEL_TOKEN (Private Integration token)
  • HIGHLEVEL_LOCATION_ID (sub-account location ID)

Optional runtime variables:

  • PYTHONUNBUFFERED=1

Setup

If the user asks to connect or set up GHL, run:

python3 scripts/setup-wizard.py

The wizard validates credentials and tests API connectivity.

Primary Script

Use the helper script for direct actions:

python3 scripts/ghl-api.py \x3Ccommand> [args...]

Common commands for realtor workflows:

  • test_connection
  • search_contacts [query]
  • get_contact [contact_id]
  • create_contact [json]
  • update_contact [contact_id] [json]
  • list_opportunities
  • list_pipelines
  • list_conversations
  • send_message [contact_id] [message]
  • list_calendars
  • get_free_slots [calendar_id] [start_date] [end_date]
  • list_workflows
  • add_to_workflow [contact_id] [workflow_id]

Realtor-Focused Playbooks

New Lead Intake

  1. search_contacts to prevent duplicates.
  2. If not found, create_contact with source tags (for example: buyer, zillow, open-house).
  3. Add next-step task/note using supported contact endpoints.

Pipeline Progress

  1. list_opportunities to inspect active deals.
  2. Move stage using the opportunity update command path in ghl-api.py.
  3. Confirm stage and status in response payload.

Follow-Up Messaging

  1. Resolve contact first (search_contacts or get_contact).
  2. Send message with send_message.
  3. Re-check conversation history with list_conversations.

Appointment Assist

  1. list_calendars
  2. get_free_slots for date range.
  3. Use the calendar endpoints in script for appointment creation if requested.

Safety Rules

  • Never print or echo raw tokens in chat output.
  • Prefer dry informational reads before write actions when intent is ambiguous.
  • Validate contact/opportunity IDs from GHL responses instead of guessing.
  • If an API error returns 401/403, stop and ask for corrected scopes or token.

References

Load these only as needed:

  • references/contacts.md
  • references/opportunities.md
  • references/conversations.md
  • references/calendars.md
  • references/troubleshooting.md
Usage Guidance
This skill looks like a plausible GHL integration, but take these precautions before installing: - Verify provenance: the source/homepage is unknown; confirm you trust the owner before supplying credentials. - Provide a dedicated Private Integration token with the minimum scopes needed (contacts.readonly, conversations.readonly/write, calendars, etc.) rather than a high-privilege account token. Rotate or revoke the token after testing. - Do not paste your token into chat or public logs. Although the setup script masks the token display, the troubleshooting docs include examples that echo $HIGHLEVEL_TOKEN — avoid running those echo commands publicly. - Because the registry metadata omits required env vars, ask the publisher to correct the manifest to declare HIGHLEVEL_TOKEN and HIGHLEVEL_LOCATION_ID so you can review permissions up front. - Test in a safe environment (a throwaway sub-account or token with limited scopes) before using this against production data. If you cannot verify the publisher or are uncomfortable supplying a token, do not install or run the scripts.
Capability Analysis
Type: OpenClaw Skill Name: ghl-crm-for-realtors Version: 1.0.0 The skill is classified as suspicious due to a vulnerability in `scripts/ghl-api.py` where JSON input for API calls (e.g., `create_contact`, `update_contact`) is directly parsed from command-line arguments (`sys.argv`) using `json.loads()` without further content validation. While path segments are sanitized with `_validate_id`, this lack of sanitization for the JSON request body creates a prompt injection risk against the AI agent. An attacker could craft malicious JSON via prompt injection, leading the agent to execute harmful or unintended API actions on the GoHighLevel platform, such as data corruption or unauthorized modifications, even though the script's core intent is to provide legitimate API access.
Capability Assessment
ℹ Purpose & Capability
The code and SKILL.md are coherent with the stated purpose: both scripts interact only with GoHighLevel (services.leadconnectorhq.com) and implement contact, conversation, calendar, and opportunity endpoints. However, the registry metadata lists no required environment variables while the SKILL.md and both scripts clearly require HIGHLEVEL_TOKEN and HIGHLEVEL_LOCATION_ID. That metadata omission is an inconsistency that should be corrected.
ℹ Instruction Scope
Runtime instructions and scripts are narrowly scoped to the GHL API and related references; they do not attempt to read unrelated filesystem paths or contact unknown endpoints. Minor scope issues: references/troubleshooting.md shows example commands that echo $HIGHLEVEL_TOKEN (which would print the raw token), while SKILL.md's Safety Rules say 'Never print or echo raw tokens' — this contradiction could lead to accidental token exposure during debugging or by less-knowledgeable users.
✓ Install Mechanism
No install spec; this is an instruction-only skill with included Python scripts using only standard library modules (urllib, json, re, etc.). There are no external downloads, package installers, or executable creation steps — low installation risk.
⚠ Credentials
The skill legitimately needs a Private Integration token (HIGHLEVEL_TOKEN) and a location ID (HIGHLEVEL_LOCATION_ID) to operate. These are sensitive credentials and are appropriately the only secrets required. However, the registry metadata failing to declare these env vars is a red flag for transparency. Also, the troubleshooting docs include examples that would print the token, increasing accidental exposure risk if users follow them without caution.
✓ Persistence & Privilege
The skill does not request always:true or any elevated persistent platform privileges. It does not modify other skills or system-wide agent settings. It is user-invocable and allows autonomous invocation (platform default), which is expected for this kind of skill.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install ghl-crm-for-realtors
  3. After installation, invoke the skill by name or use /ghl-crm-for-realtors
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of GHL CRM for Realtors skill. - Provides GoHighLevel CRM integration for realtor workflows: contact management, pipeline actions, messaging, calendar, and workflow enrollment. - Includes setup wizard and command-line helpers for common realtor tasks. - Enforces safety rules for credentials and API responses. - Supplies playbooks for lead intake, pipeline progress, follow-up messaging, and appointment scheduling.
Metadata
Slug ghl-crm-for-realtors
Version 1.0.0
License —
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is GHL CRM for Realtors?

Manage realtor tasks in GoHighLevel CRM including contact search and updates, pipeline tracking, messaging, calendar slots, and workflow enrollment via API v2. It is an AI Agent Skill for Claude Code / OpenClaw, with 795 downloads so far.

How do I install GHL CRM for Realtors?

Run "/install ghl-crm-for-realtors" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GHL CRM for Realtors free?

Yes, GHL CRM for Realtors is completely free (open-source). You can download, install and use it at no cost.

Which platforms does GHL CRM for Realtors support?

GHL CRM for Realtors is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GHL CRM for Realtors?

It is built and maintained by danielfoch (@danielfoch); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463942 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259883 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200739 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191401 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190375 · by oswalpalash

💬 Comments