Weather Query

Use when users ask about weather conditions, forecasts, or climate information for locations in China.

Security Scan

The skill is internally consistent for fetching weather data: its scripts perform simple GET requests to a single third‑party weather API and no credentials or installs are required, but the external API host is not a well-known provider so you should consider privacy/trust before using it.

Purpose & Capability

The name/description match the included scripts: realtime.sh and forecast.sh query a weather API and return current conditions and forecasts for Chinese locations. Required resources (no env, no binaries) are proportional to the stated purpose.

Instruction Scope

SKILL.md instructs the agent to run the provided shell scripts and to format responses by encoding. The scripts make outbound HTTPS GET requests and will transmit user-provided location queries to https://60s.viki.moe. The SKILL.md does not disclose that hostname explicitly; this is not malicious but is a privacy/trust consideration. The scripts do not read local files or environment variables beyond parameters, and they do not attempt extra data collection.

Install Mechanism

No install spec; the skill is instruction+script only. The scripts are plain shell and do not download or install additional code. This is low-risk from an install/execution perspective.

Credentials

The skill requests no environment variables or credentials. There are no config paths required. This is proportionate to a simple weather lookup skill.

Persistence & Privilege

The skill does not request persistent/system privileges and is not marked always:true. It does not modify other skills or system configuration.

Assessment

This skill appears to do what it says: run two shell scripts that call a third‑party weather API and return results. Before installing, consider that: (1) location queries (user input) are sent to https://60s.viki.moe — verify you trust that provider and its privacy policy if you will send sensitive or private location data; (2) SKILL.md does not list the remote hostname, so inspect the scripts (already included) to confirm behavior; (3) no credentials are requested, so there is no obvious credential exfiltration risk, but if you prefer trusted sources swap the API endpoint to a known provider; (4) run the skill in a controlled environment if you need to audit traffic (e.g., via a network proxy) before deploying broadly.

Weather Query Skill

This skill enables AI agents to fetch real-time weather information and forecasts for locations in China using the provided shell scripts.

When to Use This Skill

Use this skill when users:

• Ask about current weather conditions
• Want weather forecasts
• Need temperature, humidity, wind information
• Request air quality data
• Plan outdoor activities and need weather info

How to Use

Get Real-time Weather

Use the realtime.sh script to get current conditions, air quality, daily life indices, and weather alerts.

./scripts/realtime.sh <query> [--encoding <text|json|markdown>]

Get Weather Forecast

Use the forecast.sh script to get hourly and daily forecast data, along with sunrise/sunset times.

./scripts/forecast.sh <query> [--encoding <text|json|markdown>] [--days <0-8>]

• query (Required): The name of the city, district, or area in Chinese (e.g., 雨花台, 北京). Can be provided as a positional argument or with --query.
• encoding (Optional): Used to specify the returned data format. Can be text, json, or markdown.
• days (Optional, forecast only): Used to specify the weather forecast date range. An integer between 0 and 8.

Response Format

To balance information depth with token consumption, you MUST use the following rules for the encoding parameter:

1. Default Strategy (--encoding markdown)

   • When to use: By default for standard weather inquiries.
   • Why: Provides well-structured, easy-to-read information with moderate token usage.

2. Brief Information (--encoding text)

   • When to use: When the user explicitly requests brief or summarized weather information.
   • Why: Returns only essential details in plain text, saving maximum tokens.

3. Complete Information (--encoding json)

   • When to use: Only when the user explicitly asks for raw data, detailed fields, or comprehensive data (all indices, timestamps).
   • Why: Returns the complete API payload, which is highly token-heavy.

Best Practices

1. Location Names: Always use Chinese characters for location names

2. Error Handling: Check if the location is valid before displaying results

3. Context: Provide relevant context based on weather conditions

   • Rain: Suggest bringing umbrella
   • Hot: Recommend staying hydrated
   • Cold: Advise wearing warm clothes
   • Poor AQI: Suggest wearing mask

4. Fallbacks: If a specific district doesn't work, try the city name

Troubleshooting

Issue: Location not found

• Solution: Try using the main city name instead of district
• Example: Use "北京" instead of "朝阳区"

Issue: No forecast data

• Solution: Verify the location name is correct
• Try standard city names: 北京, 上海, 广州, 深圳, etc.

Issue: Data seems outdated

• Solution: The API updates regularly, but weather can change quickly
• Check the updated timestamp in the response

Supported Locations

The weather API supports most cities and districts in China, including:

• Provincial capitals: 北京, 上海, 广州, 深圳, 成都, 杭州, 南京, 武汉, etc.
• Major cities: 苏州, 青岛, 大连, 厦门, etc.
• Districts: 海淀区, 朝阳区, 浦东新区, etc.