Skill flagged — suspicious patterns detected

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

last-minute

v3.2.0

Book last minute flights, same-day tickets and urgent departures with emergency travel options. Also supports: flight booking, hotel reservation, train ticke...

0· 36·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 palexu/last-minute.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install last-minute
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill claims to be a last-minute flight booking helper but the metadata lists no required binaries or install steps while the SKILL.md mandates using the third-party 'flyai' CLI (@fly-ai/flyai-cli). That is an incoherence: either the skill should declare the CLI as a required binary/install, or it shouldn't require it at runtime. The skill also references 'Powered by Fliggy (Alibaba Group)' but provides no homepage, source, or explanation of authentication/payment flows.
!
Instruction Scope
The instructions force the agent to (a) only use flyai CLI output and never fall back to training data, (b) install the CLI via npm if missing, (c) run keyword-search and multiple retries, and (d) persist an execution log to .flyai-execution-log.json if writable. The SKILL.md also suggests using 'sudo npm i -g' as a fallback — an instruction that could attempt privilege escalation. Writing local logs that include raw user queries may capture sensitive PII. These runtime actions go beyond simple read-only lookups and are not reflected in the declared metadata.
!
Install Mechanism
There is no install spec in the registry entry, but the SKILL.md instructs installing a global npm package (@fly-ai/flyai-cli) from the npm ecosystem, and even suggests sudo if initial installs fail. Installing a global npm package can execute arbitrary code on the host; the skill provides no trusted release URL, no source repo, and no signature. That gap materially increases risk.
!
Credentials
The skill declares no required environment variables, yet it will invoke a networked CLI that likely transmits user queries (origins/destinations/dates) to a remote service. There is no mention of authentication tokens, payment handling, or where sensitive data is sent. The lack of declared credentials or privacy guidance is disproportionate to a booking workflow that normally involves external accounts and payment redirects.
!
Persistence & Privilege
The skill does not request permanent 'always' privilege, which is good, but it directs runtime installation of a global package (and suggests sudo) and encourages appending execution logs to a local file. Global installs and sudo commands are system-level actions; the skill also requests writing logs that may contain sensitive user input. These are non-trivial privileges not reflected in the registry metadata.
What to consider before installing
This skill is suspicious because its instructions require installing and running an external CLI (@fly-ai/flyai-cli) yet the skill metadata doesn't declare that dependency or provide a source/homepage. Before installing or using it: 1) Ask the publisher for the package source and a homepage/repo; verify the npm package '@fly-ai/flyai-cli' (owner, repository, versions, README, and security advisories). 2) Do not run global npm installs or sudo on a production machine — prefer a sandbox/container or inspect the package contents first. 3) Confirm where booking links lead and whether payments or authentication are required; avoid giving credentials unless you trust the upstream service. 4) Be wary that the skill writes a local .flyai-execution-log.json containing raw queries (PII risk); ensure logs are stored securely or disable logging. 5) If you need this capability, request the publisher add explicit install metadata, a verified homepage/repo, and declare required credentials and privacy behavior. If you cannot validate the CLI package and its publisher, avoid installing or running this skill.

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

latestvk97dztqrt71e10efs88jqncg8n85nhps
36downloads
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: last-minute

Overview

Book last minute flights — same-day tickets, urgent departures, and emergency travel. For travelers who need to fly NOW, not tomorrow.

When to Activate

User query contains:

  • English: "last minute flight", "same-day flight", "urgent flight", "emergency flight", "fly today", "last minute ticket"
  • Chinese: "临期航班", "当天机票", "紧急机票", "说走就走", "今晚机票", "马上飞"

Do NOT activate for: cheap/budget flights without urgency → economy-flights; red eye specifically → red-flights

Prerequisites

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

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. Default: today
--dep-hour-startNoDeparture hour filter start (0-23). Default: current hour
--dep-hour-endNoDeparture hour filter end (0-23). Default: 23
--sort-typeNoDefault: 6 (earliest departure — fly ASAP)
--journey-typeNo1=direct, 2=connecting
--seat-class-nameNoeconomy / business / first. Default: economy
--max-priceNoPrice ceiling in CNY

Sort Options

ValueMeaningWhen to Use
6Earliest departureDefault — fly ASAP
7Latest releaseFreshly added last-minute inventory
3Price ascendingCheapest among last-minute
4Duration ascendingFastest route

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: Same-Day Urgent

Trigger: "fly today", "当天机票", "马上飞"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {today} --dep-hour-start {now+1} --sort-type 6

Output: Flights departing within hours, earliest first.

Playbook B: Tomorrow Morning

Trigger: "tomorrow morning flight", "明早航班"

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

Output: Morning flights for tomorrow, earliest departure first.

Playbook C: Within 3 Days Bargain

Trigger: "last minute deal this week", "这几天有便宜票吗"

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

Output: Cheapest flights within the next 3 days.

Playbook D: Broad Search (no last-minute found)

Trigger: fallback when 0 results

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {today} --sort-type 6
flyai keyword-search --query "{origin} to {destination} last minute flights today"

Output: Broader search without hour filter + keyword fallback.

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?
  • All results are for near-term dates (today/tomorrow)?

Any NO → re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-04-14 --dep-hour-start 14 --sort-type 6
flyai search-flight --origin "Guangzhou" --destination "Chengdu" --dep-date 2026-04-15 --dep-hour-start 6 --dep-hour-end 12 --sort-type 6

Output Rules

  1. Conclusion first — lead with earliest departing flight
  2. Urgency indicator — show "departs in X hours" for same-day flights
  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
  8. ❌ Never fabricate prices, flight numbers, or schedules

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
"last minute" / "临期航班"--dep-date {today} --sort-type 6
"fly today" / "当天机票"--dep-date {today} --dep-hour-start {now+1}
"tomorrow morning" / "明早航班"--dep-date {tomorrow} --dep-hour-start 6 --dep-hour-end 12
"within 3 days" / "这几天"--dep-date-start {today} --dep-date-end {today+3}
"cheapest last minute" / "最便宜临期票"add --sort-type 3 instead of 6
"direct only" / "只看直飞"add --journey-type 1
"under budget" / "预算内"add --max-price {budget}

Last-minute inventory changes rapidly. If 0 results for tonight, try expanding to tomorrow or removing hour filters. Same-day flights after 21:00 may overlap with red-eye category.

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