Skillv3.2.1

ClawScan security

Aerobase Travel Wallet · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousMar 31, 2026, 12:35 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's declared API-based functionality and single API key requirement are coherent, but an internal contradiction (claims 'API-only' while advertising browser automation and Gmail import for Pro) raises concerns you should verify before enabling or upgrading.
Guidance: This skill appears to be what it says: an Aerobase API client that uses a single API key. Before installing or upgrading to Pro, verify the following: 1) Confirm you obtain AEROBASE_API_KEY only from the official site (https://aerobase.app/openclaw-travel-agent). 2) Ask the vendor to clarify the apparent contradiction between 'API-only' and the Pro features that mention browser automation and Gmail imports — specifically what additional permissions, OAuth flows, or tokens are required and how those are handled (scopes, vendor access, data retention). 3) Never paste passwords, OTPs, cookies, or mailbox credentials into chat; prefer OAuth flows that you inspect in-browser. 4) If you enable Pro features that access Gmail or perform browser automation, verify the exact scopes and consider using a mailbox/account with limited data or recovery options. If the vendor cannot clearly explain the Pro privacy/auth flow, treat the Pro features as a potential privacy risk and avoid enabling them.
Findings: [no_regex_findings] expected: The package is instruction-only and contains only SKILL.md and a license, so the regex scanner had no code to analyze. This absence of findings is expected but not evidence of safety.

Review Dimensions

Purpose & Capability: okName/description (travel wallet, CPP calculation, transfer partners) align with the declared primary credential (AEROBASE_API_KEY) and the API endpoints listed. Requiring an Aerobase API key is proportional and expected for this purpose.
Instruction Scope: concernSKILL.md limits runtime behavior to calls to Aerobase endpoints, parameter validation, and error handling, and explicitly forbids collecting passwords/OTPs. However, the 'Pro Superpowers' section advertises browser-powered automation and Gmail loyalty statement import (which would require access to third‑party accounts/data). That conflicts with the earlier 'API-only: no scraping, no browser automation' statement and is a scope inconsistency that should be clarified.
Install Mechanism: okInstruction-only skill with no install spec and no code files — minimal install risk because nothing will be written to disk by the skill package itself.
Credentials: noteOnly one credential is declared (AEROBASE_API_KEY), which matches the stated API integration. The SKILL.md also promises Pro features (Gmail import, browser automation) that would require additional credentials/permissions (OAuth tokens, mailbox access) but these are not declared; verify what extra permissions or tokens are required if you enable/upgrade.
Persistence & Privilege: okSkill is not always-on and is user-invocable; it does not request elevated platform privileges or modifications to other skills. Autonomous invocation is permitted (platform default) but not combined with other red flags here.