Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Pilot Real Estate Analyzer Setup

v1.0.0

Deploy a real estate analysis system with 4 agents for property scraping, market valuation, comparable analysis, and deal alerting. Use this skill when: 1. U...

0· 54·0 current·0 all-time
byCalin Teodor@teoslayer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for teoslayer/pilot-real-estate-analyzer-setup.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Real Estate Analyzer Setup" (teoslayer/pilot-real-estate-analyzer-setup) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-real-estate-analyzer-setup
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: pilotctl, clawhub
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install pilot-real-estate-analyzer-setup

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-real-estate-analyzer-setup
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description match the runtime instructions: it configures four roles (scraper, analyzer, comparator, notifier) and requires pilotctl and clawhub to manage agents and install related pilot-* skills. Requested binaries (pilotctl, clawhub) are appropriate for this orchestrator-style skill.
Instruction Scope
SKILL.md is an instruction-only installer that tells the agent to run shell commands (clawhub install, pilotctl set-hostname, handshake, publish/subscribe) and to write a manifest under ~/.pilot/setups. Commands and file writes are aligned with setup goals, but the instructions will cause network installs (clawhub) and automated trust handshakes; these behaviors expand runtime scope and deserve explicit user confirmation.
Install Mechanism
There is no install spec in the skill bundle itself (instruction-only). The setup relies on clawhub to fetch and install many pilot-* packages; the provenance and contents of those packages are not visible here. That is expected for an orchestrator, but it means you cannot statically verify what will be downloaded or executed when following these steps.
!
Credentials
The skill configures a notifier role that references Slack/webhook/email bridges, which typically require credentials (API tokens, webhook URLs, SMTP credentials). The skill declares no required environment variables or credential inputs, so credentials will need to be supplied later by other components or interactively — this omission is an incoherence that can lead to implicit credential requests later or misconfiguration.
Persistence & Privilege
always is false and the skill is user-invocable (normal). The only persistent write instructed is a manifest under the user's ~/.pilot directory; it does not attempt to modify other skills' configurations or system-wide settings. The handshake automation (auto-approve when both sides send handshakes) increases trust surface but is a platform behavior rather than a hidden privilege of this skill.
What to consider before installing
This skill is an orchestrator (not a payload) and largely does what it says, but review these before installing: 1) Verify the source and integrity of the pilotctl and clawhub binaries and confirm where clawhub will download pilot-* packages (registry/URLs). 2) Prepare credentials (Slack webhook/API tokens, email/SMTP, any other service keys) and ensure they will be supplied securely to the installed bridge skills — the setup does not declare them. 3) Be aware that handshakes auto-approve trust when both agents send them; only run these steps between hosts you control or in an isolated test network first. 4) Because this skill is instruction-only, you cannot statically inspect the code of the pilot-* skills it installs; consider installing and auditing those dependencies in a sandbox before deploying to production. 5) If you need higher assurance, ask the skill author for a list of exact package sources and the environment variables those downstream skills require.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspilotctl, clawhub
latestvk97dfz2c76vzkqtqbj6da9crgx85dkd5
54downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Real Estate Analyzer Setup

Deploy 4 agents that scrape listings, calculate valuations, generate CMA reports, and alert investors to deals.

Roles

RoleHostnameSkillsPurpose
scraper<prefix>-scraperpilot-stream-data, pilot-cron, pilot-archiveMonitors MLS, Zillow, Redfin for new listings
analyzer<prefix>-analyzerpilot-metrics, pilot-dataset, pilot-task-routerCalculates valuations, cap rates, rental yields
comparator<prefix>-comparatorpilot-event-filter, pilot-share, pilot-reviewPulls comps, adjusts for features, generates CMA reports
notifier<prefix>-notifierpilot-alert, pilot-slack-bridge, pilot-webhook-bridgeScores deals by ROI, alerts investors via Slack/email

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# scraper:
clawhub install pilot-stream-data pilot-cron pilot-archive
# analyzer:
clawhub install pilot-metrics pilot-dataset pilot-task-router
# comparator:
clawhub install pilot-event-filter pilot-share pilot-review
# notifier:
clawhub install pilot-alert pilot-slack-bridge pilot-webhook-bridge

Step 3: Set the hostname:

pilotctl --json set-hostname <prefix>-<role>

Step 4: Write the setup manifest:

mkdir -p ~/.pilot/setups
cat > ~/.pilot/setups/real-estate-analyzer.json << 'MANIFEST'
{
  "setup": "real-estate-analyzer",
  "setup_name": "Real Estate Analyzer",
  "role": "<ROLE_ID>",
  "role_name": "<ROLE_NAME>",
  "hostname": "<prefix>-<role>",
  "description": "<ROLE_DESCRIPTION>",
  "skills": { "<skill>": "<contextual description>" },
  "peers": [ { "role": "...", "hostname": "...", "description": "..." } ],
  "data_flows": [ { "direction": "send|receive", "peer": "...", "port": 1002, "topic": "...", "description": "..." } ],
  "handshakes_needed": [ "<peer-hostname>" ]
}
MANIFEST

Step 5: Tell the user to initiate handshakes with direct communication peers.

Manifest Templates Per Role

scraper

{"setup":"real-estate-analyzer","setup_name":"Real Estate Analyzer","role":"scraper","role_name":"Property Scraper","hostname":"<prefix>-scraper","description":"Monitors MLS listings, Zillow, Redfin feeds for new properties matching criteria.","skills":{"pilot-stream-data":"Stream normalized listing data to market analyzer as properties are found.","pilot-cron":"Schedule periodic scraping runs against MLS and listing feeds.","pilot-archive":"Archive raw listing snapshots for historical trend analysis."},"peers":[{"role":"analyzer","hostname":"<prefix>-analyzer","description":"Receives new listings for market analysis"}],"data_flows":[{"direction":"send","peer":"<prefix>-analyzer","port":1002,"topic":"new-listing","description":"New property listings with normalized data"}],"handshakes_needed":["<prefix>-analyzer"]}

analyzer

{"setup":"real-estate-analyzer","setup_name":"Real Estate Analyzer","role":"analyzer","role_name":"Market Analyzer","hostname":"<prefix>-analyzer","description":"Calculates property valuations, cap rates, rental yields, and appreciation trends.","skills":{"pilot-metrics":"Compute cap rates, rental yields, price-per-sqft, appreciation trends.","pilot-dataset":"Store and query historical market data for valuation models.","pilot-task-router":"Route properties to appropriate valuation models by property type."},"peers":[{"role":"scraper","hostname":"<prefix>-scraper","description":"Sends new property listings"},{"role":"comparator","hostname":"<prefix>-comparator","description":"Receives valuation requests for comparable analysis"}],"data_flows":[{"direction":"receive","peer":"<prefix>-scraper","port":1002,"topic":"new-listing","description":"New property listings with normalized data"},{"direction":"send","peer":"<prefix>-comparator","port":1002,"topic":"valuation-request","description":"Valuation requests with market metrics"}],"handshakes_needed":["<prefix>-scraper","<prefix>-comparator"]}

comparator

{"setup":"real-estate-analyzer","setup_name":"Real Estate Analyzer","role":"comparator","role_name":"Comp Analyzer","hostname":"<prefix>-comparator","description":"Pulls comparable sales, adjusts for features, generates CMA reports.","skills":{"pilot-event-filter":"Filter comps by proximity, recency, and property similarity.","pilot-share":"Share generated CMA reports with deal notifier and external consumers.","pilot-review":"Review and validate comp adjustments for accuracy."},"peers":[{"role":"analyzer","hostname":"<prefix>-analyzer","description":"Sends valuation requests with market metrics"},{"role":"notifier","hostname":"<prefix>-notifier","description":"Receives deal scores for investor alerting"}],"data_flows":[{"direction":"receive","peer":"<prefix>-analyzer","port":1002,"topic":"valuation-request","description":"Valuation requests with market metrics"},{"direction":"send","peer":"<prefix>-notifier","port":1002,"topic":"deal-score","description":"Deal scores with CMA reports"}],"handshakes_needed":["<prefix>-analyzer","<prefix>-notifier"]}

notifier

{"setup":"real-estate-analyzer","setup_name":"Real Estate Analyzer","role":"notifier","role_name":"Deal Notifier","hostname":"<prefix>-notifier","description":"Scores deals by ROI potential, alerts investors via Slack/email for hot opportunities.","skills":{"pilot-alert":"Generate deal alerts when ROI exceeds investor thresholds.","pilot-slack-bridge":"Post formatted deal summaries to investor Slack channels.","pilot-webhook-bridge":"Send deal alerts to email services and CRM webhooks."},"peers":[{"role":"comparator","hostname":"<prefix>-comparator","description":"Sends deal scores with CMA reports"}],"data_flows":[{"direction":"receive","peer":"<prefix>-comparator","port":1002,"topic":"deal-score","description":"Deal scores with CMA reports"},{"direction":"send","peer":"external","port":443,"topic":"deal-alert","description":"Deal alerts to Slack and email"}],"handshakes_needed":["<prefix>-comparator"]}

Data Flows

  • scraper -> analyzer : new-listing events (port 1002)
  • analyzer -> comparator : valuation-request events (port 1002)
  • comparator -> notifier : deal-score events (port 1002)
  • notifier -> external : deal-alert notifications (port 443)

Handshakes

# scraper <-> analyzer:
pilotctl --json handshake <prefix>-analyzer "setup: real-estate-analyzer"
pilotctl --json handshake <prefix>-scraper "setup: real-estate-analyzer"

# analyzer <-> comparator:
pilotctl --json handshake <prefix>-comparator "setup: real-estate-analyzer"
pilotctl --json handshake <prefix>-analyzer "setup: real-estate-analyzer"

# comparator <-> notifier:
pilotctl --json handshake <prefix>-notifier "setup: real-estate-analyzer"
pilotctl --json handshake <prefix>-comparator "setup: real-estate-analyzer"

Workflow Example

# On analyzer — subscribe to new listings:
pilotctl --json subscribe <prefix>-scraper new-listing

# On scraper — publish a new listing:
pilotctl --json publish <prefix>-analyzer new-listing '{"mls_id":"MLS-78432","address":"1425 Oak Valley Dr","price":485000,"sqft":2200,"beds":4}'

# On comparator — subscribe to valuation requests:
pilotctl --json subscribe <prefix>-analyzer valuation-request

# On notifier — subscribe to deal scores:
pilotctl --json subscribe <prefix>-comparator deal-score

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.

Comments

Loading comments...