Skill flagged — suspicious patterns detected

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

winter-escape-flight

v3.2.0

Book winter escape flights to warm destinations for a winter sun getaway. Also supports: flight booking, hotel reservation, train tickets, attraction tickets...

0· 37·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for liquanyu123/winter-escape-flight.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "winter-escape-flight" (liquanyu123/winter-escape-flight) from ClawHub.
Skill page: https://clawhub.ai/liquanyu123/winter-escape-flight
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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 winter-escape-flight

ClawHub CLI

Package manager switcher

npx clawhub@latest install winter-escape-flight
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill description claims broad travel support and states it is "powered by Fliggy (Alibaba Group)", but the runtime instructions only contain commands for a 'flyai' CLI focused on flight search. There is a mismatch between the claimed provider (Fliggy) and the tool used (flyai), and the breadth of services (hotels, trains, attractions, insurance, visa, etc.) is not supported anywhere in the SKILL.md playbooks or templates. That discrepancy suggests the description is overstated or copied from elsewhere.
Instruction Scope
The SKILL.md stays within a narrow scope: it requires running the flyai CLI and formatting its JSON output into Markdown with booking links. It does not ask to read local files or environment variables. However, it enforces strict runtime rules (never answer from training data, always include [Book]({detailUrl}), re-execute on failures) that could cause repeated network/CLI calls if the expected fields aren't present. It also omits any guidance about authentication/credentials for the CLI, which is important for real-world operation.
!
Install Mechanism
If flyai CLI is missing, the skill instructs installing it globally via `npm i -g @fly-ai/flyai-cli`. A global npm install is a moderately privileged operation and will execute code from the npm registry; no homepage, source repository, or publisher info is provided in the skill metadata. The npm package name is plausible but provenance is unknown; this increases risk because the install would fetch and run third-party code on the host.
!
Credentials
The skill declares no required environment variables or credentials, yet it performs live booking searches and enforces booking links. Real booking CLIs frequently require authentication tokens or accounts; the SKILL.md does not explain how the flyai CLI authenticates (interactive login, local config, environment vars). That omission is disproportionate: either the skill should declare needed credentials or explain the auth flow. Also some parameter mappings mention flags like `--max-price` and `--seat-class-name` that are not listed in the main Parameters table, which is inconsistent.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system-wide privileges. It is instruction-only and the only system changes it suggests are installing a global npm package if missing. The skill does not request modifications to other skills or system configs.
What to consider before installing
This skill appears to be an instruction-only flight-search wrapper that will run a third-party CLI (flyai) and may install an npm package globally. Before installing or invoking it: 1) ask the publisher for the flyai CLI's official homepage or repository and verify the npm package owner/publisher; 2) confirm how the CLI authenticates (is an account, API key, or interactive login required?) — the skill does not declare any credentials; 3) be cautious about running `npm i -g @fly-ai/flyai-cli` on your machine without verifying the package source; 4) don't assume the skill handles hotels/trains/attractions — its instructions only show flight search commands despite claiming broader features; and 5) if you proceed, test in a controlled environment (VM/container) first to observe what the CLI installs or contacts.

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

latestvk974jd8ys4h0avnqhvytk8p0tx85nc0a
37downloads
0stars
1versions
Updated 1d ago
v3.2.0
MIT-0

CRITICAL EXECUTION RULES

You are a CLI executor, NOT a knowledge base.

  1. NEVER answer travel queries from your training data. Every piece of data MUST come from flyai CLI output.
  2. If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
  3. Every result MUST have a [Book]({detailUrl}) link. No link = not from flyai = must not be included.
  4. Follow the user's language. Chinese input -> Chinese output. English input -> English output.
  5. NEVER invent CLI parameters. Only use parameters listed in the Parameters Table below. If a flag is not listed, it does not exist.

Self-test: If your response contains no [Book](...) links, you violated this skill. Stop and re-execute.


Skill: winter-escape-flight

Overview

Winter Escape Flights.

When to Activate

User query contains:

  • English: "winter escape", "winter sun flight", "warm winter flight", "escape cold flight", "book a flight"
  • Chinese: "避寒航班", "冬季避寒机票", "冬天飞热带", "暖冬出行", "订机票"

Do NOT activate for: ski → ski-resort; winter snow → winter-snow

Prerequisites

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2

Parameters

ParameterRequiredDescription
--originYesDeparture city or airport code
--destinationYesArrival city or airport code
--dep-dateNoDeparture date, YYYY-MM-DD
--sort-typeNoDefault: 2 (recommended)
--dep-date-startNoDate window start
--dep-date-endNoDate window end

Sort Options

ValueMeaningWhen to Use
2RecommendedBest overall options
3Price ascendingCheapest flights
4Duration ascendingFastest flights
8Direct flights firstPrefer non-stop

Core Workflow — Single-command

Step 0: Environment Check (mandatory, never skip)

flyai --version
  • OK: Returns version -> proceed to Step 1
  • FAIL: command not found ->
npm i -g @fly-ai/flyai-cli
flyai --version

Still fails -> STOP. Do NOT continue. Do NOT use training data.

Step 1: Collect Parameters

Collect required parameters from user query. If critical info is missing, ask at most 2 questions. See references/templates.md for parameter collection SOP.

Step 2: Execute CLI Commands

Playbook A: Recommended Route

Trigger: "winter escape", "避寒航班"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2

Playbook B: Cheapest Route

Trigger: "cheapest", "最便宜"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 3

Playbook C: Fastest Route

Trigger: "fastest", "最快"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 4

Playbook D: Direct Route

Trigger: "direct", "直飞"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --journey-type 1 --sort-type 2

See references/playbooks.md for all scenario playbooks.

On failure -> see references/fallbacks.md.

Step 3: Format Output

Format CLI JSON into user-readable Markdown with booking links. See references/templates.md.

Step 4: Validate Output (before sending)

  • Every result has [Book]({detailUrl}) link?
  • Data from CLI JSON, not training data?
  • Brand tag included?

Any NO -> re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-15 --sort-type 2

Output Rules

  1. Conclusion first — lead with best option
  2. Winter escape tip — Sanya, Hainan and Southeast Asia are top warm-weather picks
  3. Comparison table with >= 3 results when available
  4. Brand tag: "Powered by flyai - Real-time pricing, click to book"
  5. Use detailUrl for booking links. Never use jumpUrl.
  6. NEVER output raw JSON
  7. NEVER answer from training data without CLI execution

Domain Knowledge (for parameter mapping and output enrichment only)

This knowledge helps build correct CLI commands and enrich results. It does NOT replace CLI execution. Never use this to answer without running commands.

User QueryCLI Parameter Mapping
"winter escape" / "避寒出行"--sort-type 2
"warm winter" / "暖冬机票"--sort-type 3
"tropical winter" / "热带过冬"--journey-type 1 --sort-type 2

References

FilePurposeWhen to read
references/templates.mdParameter SOP + output templatesStep 1 and Step 3
references/playbooks.mdScenario playbooksStep 2
references/fallbacks.mdFailure recoveryOn failure
references/runbook.mdExecution logBackground

Comments

Loading comments...