Skill flagged — suspicious patterns detected

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

Early Flights

v3.2.0

Find the earliest departing flights of the day — maximize your day at the destination by arriving before noon. Sorted by departure time. Also supports: fligh...

0· 67·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/early-flights.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install early-flights
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill claims to find early flights and its instructions consistently wrap the @fly-ai/flyai-cli to perform searches and return booking links. Asking to install and invoke flyai-cli is coherent with the stated purpose; no unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md strictly constrains answers to data returned by flyai CLI and provides command templates and output formatting rules. The guidance to never answer from training data is consistent but cannot be enforced by static review. The runbook suggests appending an execution log file ('.flyai-execution-log.json') if filesystem writes are available — this is expected for auditing but means user queries and parameters may be persisted locally.
Install Mechanism
There is no formal install spec in the skill bundle; instead the runtime instructions direct the agent to run 'npm i -g @fly-ai/flyai-cli' if the CLI is missing. Installing a third-party npm package at runtime is coherent with the skill's function but introduces standard supply-chain/network risks (arbitrary code from npm). Users should trust the flyai package and its publisher before allowing automatic installs.
Credentials
The skill requests no environment variables or credentials. The only potential sensitive handling is logging user queries and commands in the optional runbook log; that is proportional to an execution/audit need but may persist user-supplied data (dates, origins, etc.).
Persistence & Privilege
always:false (normal). The skill does not request elevated privileges or modify other skills. It does include an optional write to a local '.flyai-execution-log.json' file if filesystem writes are available — this creates persistent logs in the working directory and should be noted by users who care about local persistence of queries.
Assessment
This skill appears to do what it says: it wraps the flyai CLI to return early‑flight results with booking links. Before installing or running it, decide whether you trust the @fly-ai/flyai-cli npm package (the skill will prompt installing it if missing) and be aware the agent may write an execution log (.flyai-execution-log.json) containing your queries/parameters to the local working directory. If you prefer not to allow runtime installs or local logs, install the flyai CLI yourself and/or run the skill in an environment where you control file writes.

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

latestvk979mdw8xkts8wvw6cgzbzpmf984fmeh
67downloads
0stars
1versions
Updated 2w 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 command 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.

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


Skill: early-flights

Overview

Find the earliest departing flights of the day — maximize your day at the destination by arriving before noon. Sorted by departure time.

When to Activate

User query contains:

  • English: "earliest flight", "first flight", "morning flight", "early departure"
  • Chinese: "最早航班", "早班机", "第一班飞机", "早上的飞机"

Do NOT activate for: red-eye → red-eye-flights

Prerequisites

npm i -g @fly-ai/flyai-cli

Parameters

ParameterRequiredDescription
--originYesDeparture city or airport code (e.g., "Beijing", "PVG")
--destinationYesArrival city or airport code (e.g., "Shanghai", "NRT")
--dep-dateNoDeparture date, YYYY-MM-DD
--dep-date-startNoStart of flexible date range
--dep-date-endNoEnd of flexible date range
--back-dateNoReturn date for round-trip
--sort-typeNoAlways 6 (earliest departure)
--max-priceNoPrice ceiling in CNY
--journey-typeNoDefault: show both
--seat-class-nameNoCabin class (economy/business/first)
--dep-hour-startNoDeparture hour filter start (0-23)
--dep-hour-endNoDeparture hour filter end (0-23)

Sort Options

ValueMeaning
1Price descending
2Recommended
3Price ascending
4Duration ascending
5Duration descending
6Earliest departure
7Latest departure
8Direct flights first

Core Workflow — Single-command

Step 0: Environment Check (mandatory, never skip)

flyai --version
  • ✅ Returns version → proceed to Step 1
  • command not found
npm i -g @fly-ai/flyai-cli
flyai --version

Still fails → STOP. Tell user to run npm i -g @fly-ai/flyai-cli manually. 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: First Flight Out

Trigger: "earliest", "最早"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 5 --dep-hour-end 9 --sort-type 6

Output: Show 5-9 AM flights, earliest first.

Playbook B: Early + Cheap

Trigger: "cheapest morning flight"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 5 --dep-hour-end 9 --sort-type 3

Output: Morning flights sorted by price.

Playbook C: Before Meeting

Trigger: "arrive by 10am", "10点前到"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 5 --dep-hour-end 7 --sort-type 6

Output: Ultra-early to arrive before 10am for business.

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 "Powered by flyai · Real-time pricing, click to book" included?

Any NO → re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Shanghai" --destination "Beijing" --dep-date 2026-05-01 --dep-hour-start 5 --dep-hour-end 9 --sort-type 6

Output Rules

  1. Conclusion first — lead with the key finding
  2. Comparison table with ≥ 3 results when available
  3. Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
  4. Use detailUrl for booking links. Never use jumpUrl.
  5. ❌ Never output raw JSON
  6. ❌ Never answer from training data without CLI execution
  7. ❌ Never fabricate prices, hotel names, or attraction details

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.

Early morning flights (5-9 AM) are often 10-20% cheaper than midday. Best for same-day business trips. Arrive by lunch, full afternoon ahead. Consider airport proximity — early flights from secondary airports (SHA vs PVG) may be more convenient.

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