← Back to Skills Marketplace
liquanyu123

wine-tour

by liquanyu123 · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ⚠ suspicious
45
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install wine-tour
Description
Book flights for wine tours to famous vineyards and wine regions. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itiner...
Usage Guidance
This skill expects you to run an external CLI (flyai) and even tells the agent to install a global npm package if it's missing, but the registry metadata does not declare that dependency. Before installing or using it: 1) verify the existence and trustworthiness of the npm package @fly-ai/flyai-cli (check its npm page, publisher, and source repository); 2) confirm whether the flyai CLI requires API keys or account credentials and where those are stored; 3) be cautious about allowing an agent to run global npm installs on your system—prefer manual review and sandboxed testing first; 4) ask the author to fix the inconsistent parameter documentation (missing flags like --journey-type, --max-price, --seat-class-name) and to declare required binaries in the registry. If you need a short recommendation: do not run this skill with elevated privileges or on a production machine until the provenance of the CLI package and the parameter/installation discrepancies are resolved.
Capability Analysis
Type: OpenClaw Skill Name: wine-tour Version: 3.2.0 The skill bundle mandates the global installation of an external NPM package (`npm i -g @fly-ai/flyai-cli`) as a mandatory prerequisite in `SKILL.md` and `references/fallbacks.md`. While this is functionally aligned with the stated purpose of providing a flight-search CLI, instructing an AI agent to perform global software installations from a public registry is a high-risk behavior that could facilitate supply-chain attacks or remote code execution. No explicit evidence of malicious intent, data exfiltration, or obfuscation was found, but the automated execution of package managers is a significant security risk.
Capability Assessment
Purpose & Capability
The skill's stated purpose is flight/hotel/train/itinerary booking and the instructions revolve around a 'flyai' CLI — that is coherent — but the package metadata declares no required binaries or credentials while the SKILL.md mandates the flyai CLI and instructs installing @fly-ai/flyai-cli. The registry should have declared 'flyai' as a required binary.
Instruction Scope
Runtime instructions require executing an external CLI and insist every answer come only from its output. There are conflicting parameter definitions across files: SKILL.md's Parameters table omits flags (e.g., --journey-type) that playbooks use, while references/templates.md maps user inputs to flags (e.g., --max-price, --seat-class-name) not listed in the main parameters table. The skill also enforces a strict 'never use training data' rule and a self-test; these are fine conceptually but the internal contradictions violate its own 'NEVER invent CLI parameters' rule.
Install Mechanism
There is no formal install spec in the registry, but the runtime instructions instruct agents to run a global npm install (npm i -g @fly-ai/flyai-cli) if the CLI is missing. Installing a global npm package at runtime is a moderate risk and should be declared in install metadata; the npm namespace/package origin is not verified in the skill files.
Credentials
The skill requests no environment variables or credentials in metadata, which is reasonable for an instruction-only adapter. However, the flyai CLI may itself require API keys or configuration (not declared). The skill should document any external credential requirements for the CLI; absence of such documentation is a gap but not direct evidence of maliciousness.
Persistence & Privilege
The skill does not request permanent presence (always is false), does not modify other skills, and has no install-time entitlement declared. No unusual privilege escalation is requested by the skill bundle itself.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install wine-tour
  3. After installation, invoke the skill by name or use /wine-tour
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
- Enforced strict CLI-only execution: all travel answers must be sourced from flyai CLI output, never from training data. - Added detailed rules for validating responses, including mandatory [Book](detailUrl) booking links for every result. - Expanded supported travel functions: now includes booking for hotels, trains, attractions, itinerary planning, visas, insurance, and car rental. - Clarified activation triggers and parameter mapping for wine tour-related queries in both English and Chinese. - Updated output formatting rules: added wine region tips, introduction of comparison tables, and explicit branding requirements. - Improved environment check workflow with installation instructions for missing flyai-cli.
Metadata
Slug wine-tour
Version 3.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is wine-tour?

Book flights for wine tours to famous vineyards and wine regions. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itiner... It is an AI Agent Skill for Claude Code / OpenClaw, with 45 downloads so far.

How do I install wine-tour?

Run "/install wine-tour" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is wine-tour free?

Yes, wine-tour is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does wine-tour support?

wine-tour is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created wine-tour?

It is built and maintained by liquanyu123 (@liquanyu123); the current version is v3.2.0.

💬 Comments