Skill flagged — suspicious patterns detected

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

explore-cambodia

v3.2.0

Book flights to Cambodia including Phnom Penh and Siem Reap. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itinerary p...

0· 60·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-cambodia.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install explore-cambodia
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's stated purpose (flight/hotel/itinerary booking for Cambodia) matches the runtime instructions which rely on a dedicated CLI (flyai). However the registry metadata did not declare any required binaries even though SKILL.md mandates flyai CLI — this is an inconsistency (missing declared requirement) rather than an obvious malicious mismatch.
Instruction Scope
The SKILL.md stays focused on flight search/booking and confines actions to the flyai CLI and formatting the CLI output. It does not instruct reading unrelated files or environment variables. It does, however, require the agent to install/run an external npm package if the CLI is absent and enforces strict rules (never answer from training data), which could cause the agent to repeatedly attempt network installs if not present.
!
Install Mechanism
There is no install spec in the registry, but SKILL.md instructs installing '@fly-ai/flyai-cli' via `npm i -g`. That implies downloading and executing third-party code from the npm registry at runtime. Because the package and its provenance are not declared or vetted here, this is a supply-chain / install risk (global npm installs may require elevated permissions and pull arbitrary code).
Credentials
The skill requests no environment variables, credentials, or config paths. Its runtime needs (a CLI and Node.js) are consistent with the task and do not request unrelated secrets.
Persistence & Privilege
The skill is not forced always-on and uses normal autonomous invocation settings. It does not request to modify other skills or system-wide settings in the instructions. No persistence or cross-skill privilege escalation is requested by SKILL.md.
What to consider before installing
This skill appears to be a focused travel/booking wrapper around a third-party CLI, but it instructs the agent to install the '@fly-ai/flyai-cli' npm package at runtime even though the registry metadata doesn't list any required binaries. Before installing or using the skill: (1) verify the npm package (@fly-ai/flyai-cli) on the npm registry — check the publisher, source repo, and recent activity; (2) be aware that `npm i -g` will download and install code from the network (may require sudo on some systems); (3) consider running the skill in a sandboxed environment or verifying the CLI's behavior manually first; (4) if you don't trust the package owner or cannot verify the CLI's source, avoid installing it — ask the skill author to add a proper install spec and required-binaries declaration so the provenance is clear.

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

latestvk97ckx1yaxt36qkf2b6pt0f7kh85e986
60downloads
0stars
1versions
Updated 3d 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-cambodia

Overview

Explore Cambodia.

When to Activate

User query contains:

  • English: "cambodia flight", "phnom penh flight", "siem reap flight", "angkor wat flight", "discover"
  • Chinese: "柬埔寨航班", "金边机票", "暹粒机票", "吴哥窟机票", "去柬埔寨"

Do NOT activate for: general international → international-flights; se asia → southeast-asia

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: "cambodia 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. Cambodia tip — visa on arrival; Siem Reap for Angkor Wat
  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
"cambodia" / "柬埔寨"--sort-type 2
"cheap siem reap" / "便宜暹粒机票"--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...