Skill flagged — suspicious patterns detected

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

explore-australia

v3.2.0

Book flights to Australia including Sydney, Melbourne, and Brisbane. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, iti...

0· 66·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 xiejinsong/explore-australia.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install explore-australia
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (book flights, hotels, tickets) align with the behaviour in SKILL.md: all runtime actions are calls to a 'flyai' CLI (search-flight, keyword-search) and formatting of results. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are narrowly scoped to collecting flight parameters, invoking the flyai CLI, formatting results, and enforcing output rules. The skill does not instruct the agent to read system files, environment secrets, or to transmit data to arbitrary endpoints beyond what the CLI would do. It does mandate always using CLI data (never using training data) and that outputs include booking links from CLI JSON.
Install Mechanism
There is no declared install spec in the registry, but SKILL.md instructs the agent to run 'npm i -g @fly-ai/flyai-cli' if flyai isn't installed. Installing a global npm package is a legitimate way to obtain a CLI but carries moderate risk: npm packages run code from a remote registry and the skill provides no homepage/repository or vetting information for @fly-ai/flyai-cli.
Credentials
The skill requests no environment variables, no credentials, and no config paths. All required inputs are user-supplied query parameters (origin, destination, dates). This is proportional to a flight-search integration.
Persistence & Privilege
always is false and the skill has no install-time persistence spec. It does not request elevated system privileges or attempt to modify other skills' configs. Autonomous invocation is allowed but is the platform default.
Assessment
This skill appears coherent for a flight-booking integration that relies on an external CLI. Before installing or enabling it: 1) Verify the npm package '@fly-ai/flyai-cli' (check its npmjs.org page, repository, publisher, recent versions, and reviews) because 'npm i -g' runs third-party code on your machine. 2) Prefer installing the CLI in a sandbox/container or evaluating it in a throwaway environment first. 3) Ask the publisher for a homepage/repo or an official vendor statement (the skill metadata lists no homepage). 4) Confirm the CLI's behaviour: whether it asks for or stores credentials, writes files, or posts data to third-party endpoints. 5) If you are uncomfortable with global installs, decline or restrict the skill; you can also require manual verification of the CLI before allowing the agent to run it. If you want higher assurance, request a versioned install spec or a signed release URL from the skill author.

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

latestvk97cgz0k48hxsqgcravs8hcxkd85eyyr
66downloads
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-australia

Overview

Explore Australia.

When to Activate

User query contains:

  • English: "australia flight", "sydney flight", "melbourne flight", "brisbane 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: "australia 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. Australia tip — visa required; peak season Dec-Feb
  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
"australia" / "澳大利亚"--sort-type 2
"cheap sydney" / "便宜悉尼机票"--sort-type 3
"australia direct" / "澳洲直飞"--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...