Skill flagged — suspicious patterns detected

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

pet-flights

v3.2.0

Fly with pets, find pet-friendly airlines and in-cabin pet tickets with animal cargo booking options. Also supports: flight booking, hotel reservation, train...

0· 39·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 bufferstreamer/pet-flights.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install pet-flights
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description match the instructions: the skill requires live data from a 'flyai' CLI to return pet‑friendly flight results. However the description also claims 'Powered by Fliggy (Alibaba Group)' while the implementation relies on a separate 'flyai' CLI — this inconsistency could be misleading about the data/source. No declared environment variables or config paths are required, which is consistent with an instruction-only CLI integration.
!
Instruction Scope
The SKILL.md mandates installing and using an external CLI (@fly-ai/flyai-cli) and forbids answering from training data; it also instructs detailed logging of executions and a file write (.flyai-execution-log.json) 'if file system writes are available'. These runtime actions include network installs, execution of external binaries, and persistent local logging of user queries/commands — all beyond mere read-only query behavior and potentially capturing sensitive input.
!
Install Mechanism
Although the registry lists no install spec, the skill's mandatory Step 0 instructs 'npm i -g @fly-ai/flyai-cli' (and even 'sudo npm i -g' as a fallback). Installing a global npm package from the public registry executes remote code with local privileges and can modify system state; there is no guidance to verify package provenance, pinned version, or checksum. This is a moderate-to-high risk action for an agent to perform automatically.
Credentials
The skill declares no required environment variables or credentials, which is proportionate on the face of it. However, the instructions assume the flyai CLI will provide booking/detailUrl data but do not explain authentication: if the CLI reads local credentials/config files or prompts for API keys, that access is not documented. Also the execution log schema stores raw 'user_query' and commands, which could capture sensitive user data; that persistence is not justified in the metadata.
!
Persistence & Privilege
The skill is not 'always' enabled, but its runtime rules ask to (a) install a global CLI (possibly with sudo), and (b) append execution logs to a local file if writable. Both create or modify system state and may persist user queries. The combination (global install + suggested sudo + local logging) increases the blast radius and should be reviewed before allowing the agent to act.
What to consider before installing
This skill mostly does what it says — it relies on a command‑line tool (flyai) to fetch live pet‑friendly flight data — but it instructs the agent to install a third‑party npm package globally (and suggests sudo) and to write execution logs locally. Before installing or allowing the agent to run this skill: 1) Verify the npm package (@fly-ai/flyai-cli) provenance and inspect its code or the publisher's reputation; 2) Do not allow automatic global installs with sudo — prefer that you or an administrator install the CLI manually in a controlled environment; 3) Ask the skill author to clarify authentication (how flyai obtains booking access) and to remove or limit persistent logging of full user queries; 4) Be skeptical of the 'Powered by Fliggy' claim vs. the 'flyai' CLI — request clarification of data sources. If you cannot verify the CLI package or do not want agents to modify system state or persist sensitive queries, do not enable this skill or only use it after manual, sandboxed installation of the CLI.

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

latestvk973p7z4azg2j45ergd0a60grd85nf2p
39downloads
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: pet-flights

Overview

Fly with pets — pet-friendly airlines, in-cabin pet tickets, and animal cargo booking. For travelers who need to bring their pets along.

When to Activate

User query contains:

  • English: "pet flight", "fly with pet", "pet-friendly airline", "animal cargo", "in-cabin pet", "dog flight"
  • Chinese: "宠物航班", "带宠物乘机", "宠物托运", "宠物机票", "小狗上飞机", "猫咪乘机"

Do NOT activate for: pet hotels → pet-hotel

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
--sort-typeNoDefault: 2 (recommended — pet-friendly routes prioritized)
--journey-typeNo1=direct (preferred with pets), 2=connecting
--seat-class-nameNoeconomy / business / first
--dep-hour-startNoDeparture hour filter start (0-23)
--dep-hour-endNoDeparture hour filter end (0-23)
--max-priceNoPrice ceiling in CNY

Sort Options

ValueMeaningWhen to Use
2RecommendedDefault — best pet-friendly options
4Duration ascendingShortest trip for pet comfort
8Direct flights firstMinimize stress — no transfers
3Price ascendingCheapest pet-friendly fares

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: Recommended Pet-Friendly Flight

Trigger: "pet flights", "宠物航班"

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

Output: Recommended flights (direct preferred for pet travel).

Playbook B: Shortest Pet Flight

Trigger: "shortest flight for pet", "宠物最短航班"

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

Output: Flights sorted by shortest duration — minimizes pet travel time.

Playbook C: Direct-Only Pet Flight

Trigger: "direct flight with pet", "带宠物直飞"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --journey-type 1 --sort-type 8

Output: Direct flights only — no transfers, less stress for pets.

Playbook D: Broad Search (no pet-friendly flights)

Trigger: fallback when 0 results

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --sort-type 2
flyai keyword-search --query "{origin} to {destination} pet friendly flights"

Output: Broader search + 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?
  • Direct flights prioritized for pet comfort?

Any NO → re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-01 --sort-type 2
flyai search-flight --origin "Shanghai" --destination "Guangzhou" --dep-date 2026-06-01 --journey-type 1 --sort-type 8

Output Rules

  1. Conclusion first — lead with best pet-friendly option (direct preferred)
  2. Pet travel tips — remind user about airline pet policies and carrier requirements
  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 pet policies, airline rules, or cargo fees

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
"pet flight" / "宠物航班"--sort-type 2 (recommended)
"shortest for pet" / "最短宠物航班"add --sort-type 4
"direct with pet" / "带宠物直飞"add --journey-type 1 --sort-type 8
"morning pet flight" / "早班宠物航班"add --dep-hour-start 6 --dep-hour-end 12

CLI does not have a pet-specific filter. Pet policy varies by airline — advise user to confirm pet cargo/cabin rules with the airline before booking. Direct flights are strongly preferred to minimize pet stress during transfers.

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