Zillow Search

PassAudited by ClawScan on May 12, 2026.

Overview

This skill appears to do what it claims: search property listings through Zillapi using a user-provided API key, with disclosed credit usage.

This looks safe to install if you trust Zillapi with your property-search queries and are comfortable using API credits. Set ZILLAPI_KEY only for the intended account, keep broad searches capped with max_items, and monitor credit usage.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Broad searches may spend more Zillapi credits than intended if the user or agent asks for many results.

Why it was flagged

The skill can make API calls that consume the user's Zillapi credits, but this cost behavior is disclosed and directly related to listing search.

Skill content
Each result returned consumes one credit. For broad queries, narrow the filters or cap `max_items` before calling.
Recommendation

Use specific filters and set a small max_items value unless you intentionally want more results.

What this means

Anyone using the skill must provide a Zillapi API key, and searches will be associated with that key/account.

Why it was flagged

The handler sends the ZILLAPI_KEY environment variable as a Bearer token to the Zillapi API, which is expected for this integration.

Skill content
"Authorization": "Bearer " + _key(),
Recommendation

Use a dedicated Zillapi key if possible, monitor usage, and revoke or rotate the key if it is exposed.