Skillv1.1.0

ClawScan security

LovTrip Meetup Planner · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousMar 8, 2026, 5:30 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's behavior matches its stated purpose (meetup planning) but the runtime instructions instruct installing/running external npm code (npx lovtrip@latest) and reference an AMAP_API_KEY that is not declared in the skill metadata — this mismatch and the unknown source increase risk.
Guidance: This skill appears to do what it says (plan meetups) but has a few red flags you should consider before installing/using it: - The runtime docs tell the agent to run `npx -y lovtrip@latest mcp`, which will download and execute code from npm at runtime. That code could change between runs and is not pinned or vetted in the metadata. - The SKILL.md example requires an AMAP_API_KEY, but the skill metadata does not declare any required environment variables — verify where and how you must provide that key and avoid supplying unrelated credentials. - The skill will process and likely transmit personal data (participant names and locations) to external services (LovTrip, AMap, map providers). If this concerns you, do not provide real addresses or personal identifiers until you verify the service's privacy policy. - Because source/homepage are 'unknown' or not validated here, independently inspect the lovtrip npm package and the lovtrip.app site (check repository, maintainer, package version history, and package contents) before running `npx` or giving API keys. If you want to proceed safely: prefer a pinned package/version or an explicit install spec, test the package in a sandboxed environment first, and only provide the AMAP API key with scope/quotas you control. If you need help verifying the npm package or the endpoints the package contacts, I can guide you through those checks.

Review Dimensions

Purpose & Capability: noteName/description, tools list, examples and references all align with a multi-person meetup planner that uses map/weather/traffic data. The listed tools (midpoint calc, venue search, schedule parsing, plan generation) are appropriate for the stated purpose.
Instruction Scope: concernSKILL.md explicitly instructs the agent to run an external CLI via: `npx -y lovtrip@latest mcp` and to supply an AMAP_API_KEY in that example. That instruction implies executing downloaded code and transmitting user-provided member names/locations/times to external services (LovTrip and AMap). The instructions do not ask the agent to read unrelated system files or credentials, but they do enable network calls and potential PII sharing without declaring required consent/limits.
Install Mechanism: concernThere is no install spec in the registry metadata, yet the SKILL.md recommends installing and running an npm package via npx (which will fetch and execute code at runtime). Using `npx lovtrip@latest` downloads code from the npm registry on demand; this is higher-risk than an instruction-only skill because the fetched code could change over time. The skill does not provide a pinned package version, checksum, or a trusted release URL.
Credentials: concernRegistry metadata declares no required environment variables, but SKILL.md's setup example requires AMAP_API_KEY (a secret/API key). That key is necessary for map/venue/traffic lookups, so its absence from the declared requirements is an inconsistency. The skill also requires user PII (names, addresses/locations) to function — expected, but the documentation does not mention privacy or retention policies.
Persistence & Privilege: okThe skill does not request persistent presence (always: false) and does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed by default (not flagged on its own).