ClawHub

UAPI 查询天气 接口

Security checks across malware telemetry and agentic risk

Overview

This is a narrow weather-lookup skill, with the main caution that generic weather requests may call an external API and may use IP-based location if no city is provided.

Install this if you want an agent to use UAPI for weather lookups. Prefer giving a city or adcode so the skill does not rely on IP-based location, and provide a UAPI Key only if you trust the service and need authenticated or higher-quota access.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
91% confidence
Finding
The skill description includes very broad English trigger terms such as "weather" and "weather api," which can match ordinary user conversation rather than an explicit request to use this specific endpoint. This can cause unintended skill activation and route requests to an external API when the user only wanted general weather discussion or planning help.

Vague Triggers

Medium
Confidence
93% confidence
Finding
The common keyword list contains ambiguous phrases including "weather," "city weather," and "weather forecast," which are generic enough to overlap with many normal conversations. In an agent-routing context, this increases the chance of false activation, unnecessary external calls, and potential leakage of user-provided location data to the API without sufficiently explicit intent.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The documentation states that when neither `city` nor `adcode` is provided, the service will fall back to IP-based automatic location lookup, but it does not warn that this uses the user's network-derived location data. This can lead an agent to trigger geolocation without explicit user consent or awareness, creating a privacy issue and potentially disclosing approximate location unexpectedly.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal