Qunar

Help users make better Qunar travel-booking decisions from public platform trade-offs. Use when the user wants to think through flight, hotel, or travel book...

Security Scan

Instruction-only travel-decision support that asks for no credentials, makes no installs, and stays within its stated public, non-account scope.

Purpose & Capability

The name and description (Qunar/travel booking decision help) match the SKILL.md: the skill gives public decision guidance for flights, hotels, and bookings. It does not request unrelated capabilities (no cloud creds, no system binaries).

Instruction Scope

The runtime instructions explicitly limit actions to public decision support and explicitly forbid account access, login, cookie handling, checkout-state actions, persistence, or browser automation. The references are small, local docs and all runtime guidance stays within the stated purpose.

Install Mechanism

There is no install spec and no code files to write to disk. Being instruction-only, it performs no downloads or installs.

Credentials

The skill declares no required environment variables, no primary credential, and no config paths. This is proportional to a read-only decision-support skill.

Persistence & Privilege

always is false and the skill does not request persistent presence or modify other skills or system settings. Autonomous invocation is allowed (platform default) but the skill's scope is limited and benign.

Assessment

This is an instruction-only, read-only decision-support skill: it does not access accounts, install software, or request secrets. It appears internally consistent and low-risk. Keep in mind: (1) provenance is limited (no homepage/source URL provided), so if you need supply-chain assurance prefer skills with known authors or public repos; (2) the skill does not fetch live prices or perform bookings — verify prices, availability, and account-specific details on the booking site before paying; and (3) do not paste sensitive credentials or private account screenshots into the conversation because the skill explicitly does not handle account data.

Help users think through Qunar booking decisions from public travel trade-offs.

This is a low-sensitivity public skill. It focuses on public decision support and does not perform login, account access, cookie handling, order retrieval, coupon claiming, local database persistence, or browser automation runtime actions.

Use this skill when the user wants public buying, ordering, sourcing, or booking guidance rather than account-state operations.

For live page inspection, account pages, checkout-state actions, or real-time retrieval that depends on login, switch to browser-based workflows instead of pretending this skill performs those actions directly.

Read these references as needed:

• references/booking-guide.md for supporting guidance
• references/output-patterns.md for supporting guidance

Workflow

1. Identify the user's shopping, ordering, or booking need.

   • Accept a product, merchant, ride, store, or booking scenario.
   • If the request is too broad, ask one short clarifying question.

2. Focus on public decision-relevant factors.

   • Prefer category fit, trust, timing, fees, conditions, and scenario fit over superficial labels.

3. Explain trade-offs.

   • Say why the strongest option fits.
   • Mention meaningful risks or caveats.

4. Give practical next-step advice.

   • Tell the user what to verify before paying or placing an order.

Output

Use this structure unless the user asks for something shorter:

Best Option

State the strongest current choice.

Why

List the main reasons.

Caveats

List meaningful concerns or trade-offs.

Final Advice

Give a direct practical suggestion.

Quality bar

Do:

• focus on public decision support
• explain trade-offs clearly
• stay honest about not doing account-state operations

Do not:

• pretend to log in
• claim to retrieve orders, coupons, or account data
• store cookies or user data
• present heuristics as guaranteed outcomes