SKILLEMALL.ai
GitHub ↗ RU Sign in

AB propai-live

PropAI Live is the complete AI-powered realtor automation suite, bundling OpenClaw core, PropAI Sync for WhatsApp lead management, Social Flow for Meta operations, and essential realtor skills for lead processing and AI assistance. It provides a unified CLI and UI for daily workflows, from lead follow-ups to social posting, with built-in risk management and approvals.

ClawHub Agent Skills author: Vishal v1.0.1 14 files body ≈ 630 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions

IntegrationWhatsAppInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 41 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 630 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 370: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 41 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: suspicious
This skill is not clearly harmful, but it needs review because it directs agents toward real WhatsApp, Meta, lead-storage, and spending workflows through dependencies and a CLI that are not included or scoped in the submitted artifact.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026