2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill propai-live- _meta.json279 B
- SKILL.md2.9 KB
Overview
This skill bundles a complete AI-powered realtor automation suite that unifies lead management, social posting, and assistant workflows into a single CLI and UI. It integrates core services like PropAI Sync, Social Flow, and OpenClaw, and provides built-in license and risk controls to keep live operations safe. The suite is designed for daily realtor workflows: from lead follow-ups to social scheduling with logging and retry handling.
How this skill works
The skill validates environment and license status, parses incoming intent into domains (lead, social, or general), proposes a minimal command plan, and executes approved actions while logging outcomes and retrying safe steps on failure. Typical commands include propai-live doctor, node scripts/license-status.mjs --mode read, and domain-specific subcommands: propai-live lead ..., propai-live social ..., propai-live ask .... Before any write, a license-guard check is required to enforce entitlements and risk gates.
When to use it
- Automating day-to-day lead follow-ups and triage from WhatsApp or other messaging sources.
- Scheduling and managing Meta social posts and campaigns through Social Flow.
- Running quick environment and license checks before onboarding or moving devices.
- Drafting outreach messages or social content where review-before-send is required.
- Archiving and auditing past skill runs or when migrating setups across machines.
Best practices
- Always run propai-live doctor on new machines or after network changes.
- Check license status with node scripts/license-status.mjs --mode read before inspecting or exporting data.
- Require explicit confirmation for high-risk actions (live spends, real-user messages).
- Keep commands profile-aware (include agency and city) to avoid cross-account mistakes.
- Treat unknown-impact actions as high-risk and gate them behind license entitlements.
Example use cases
- Validate setup, parse a new WhatsApp lead, generate a follow-up draft, and queue it for review with propai-live lead ...
- Run a social posting dry-run to preview captions and tags, then request approval before publishing with propai-live social ...
- Check license entitlement for lead-storage before exporting a contact batch using node scripts/license-guard.mjs --mode write --require-entitlement lead-storage.
- Diagnose a failed API connection using propai-live doctor, then run the setup wizard to reconfigure credentials.
- Use propai-live ask ... to run OpenClaw queries for market summaries and action suggestions for listings.
FAQ
Run propai-live --version then propai-live doctor to validate the bundle and connections, and check license with node scripts/license-status.mjs --mode read.
How are risky actions controlled?
Writes and high-impact operations require explicit license-guard checks and user confirmation; unknown-impact actions are treated as high-risk by default.