Skill flagged — suspicious patterns detected

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

explore-canada

v3.2.0

Book flights to Canada including Vancouver, Toronto, and Montreal. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itine...

0· 62·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 dingtom336-gif/explore-canada.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "explore-canada" (dingtom336-gif/explore-canada) from ClawHub.
Skill page: https://clawhub.ai/dingtom336-gif/explore-canada
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 explore-canada

ClawHub CLI

Package manager switcher

npx clawhub@latest install explore-canada
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill claims to be “powered by Fliggy (Alibaba Group)” in the description but the runtime strictly requires a third‑party CLI named @fly-ai/flyai-cli. That branding mismatch is unexplained and suspicious, though the required operations (running a flight-search CLI) are consistent with a travel-booking skill.
!
Instruction Scope
The SKILL.md forces all answers to come only from the flyai CLI and instructs the agent to install that CLI if missing. It mandates re-execution until every result contains a [Book](...) link. It does not instruct any validation of the CLI binary/package (no checksum, no vendor homepage) and instructs global npm installation at runtime — expanding the agent's scope to download and run third‑party code on the host.
!
Install Mechanism
There is no formal install spec in the registry; instead the instructions tell the agent to run `npm i -g @fly-ai/flyai-cli` if the CLI isn't present. Installing an npm package at runtime pulls arbitrary code from the public registry and writes to disk/globally alters the environment without provenance or verification — a non-trivial install risk.
Credentials
The skill requests no environment variables, credentials, or config paths. For a flight-search/bookings skill this is proportionate; nothing here attempts to access unrelated secrets or system configs.
Persistence & Privilege
always:false and no install spec in the registry. The skill does instruct installing a global npm package at runtime, but it does not request permanent platform privileges or set always:true. Autonomous invocation is allowed (default) but that is normal for skills and not sufficient alone to be flagged.
What to consider before installing
This skill appears to be a travel-booking wrapper that depends on a third-party CLI but has a few red flags: the description credits 'Fliggy' while the runtime requires an @fly‑ai CLI (branding mismatch), and the skill tells the agent to run a global `npm i -g` at runtime with no provenance checks. Before installing or enabling this skill: 1) ask the publisher for the CLI's official homepage, source repo, and package owner on npm (verify that @fly-ai is a legitimate, trusted publisher); 2) prefer skills that include an explicit, reviewed install spec or a verified binary/sha256; 3) avoid allowing autonomous execution until you confirm the package is safe; and 4) if you must use it, run the npm install in an isolated environment (container or VM) and inspect the installed package and its network behavior. If you cannot verify the CLI vendor or source repo, treat this skill as high-risk and do not install it on production or personal systems.

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

latestvk973edbk3nk0y79vdpevmbv6ch85e5d7
62downloads
0stars
1versions
Updated 4d 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: explore-canada

Overview

Explore Canada.

When to Activate

User query contains:

  • English: "canada flight", "vancouver flight", "toronto flight", "montreal flight", "discover"
  • Chinese: "加拿大航班", "温哥华机票", "多伦多机票", "蒙特利尔机票", "去加拿大"

Do NOT activate for: general international → international-flights

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: "canada flight", "加拿大航班"

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. Canada tip — visa required; best time Jun-Sep
  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
"canada" / "加拿大"--sort-type 2
"cheap vancouver" / "便宜温哥华机票"--sort-type 3

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...