Back to skill
Skillv1.3.2
ClawScan security
Crypto Traveler - Book Hotels and Flights with Bitcoin · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 10, 2026, 4:14 PM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's requests and runtime instructions are consistent with a travel booking integration that uses API credentials; it is an instruction-only skill and does not ask for unrelated access or installs.
- Guidance
- This skill appears coherent for a crypto-capable travel booking API. Before installing: (1) Confirm how and where you'll provide CLIENT_ID / CLIENT_SECRET / USER_ACCESS (use the platform's secure secret storage rather than pasting tokens into chat). (2) Only provide USER_ACCESS when a real user explicitly grants it, and prefer scope-limited tokens. (3) Verify that the agent will only send credentials to https://agents.cryptotraveler.com as the SKILL.md requires. (4) Be aware the SKILL.md asks agents to re-fetch itself for updates — if your agent follows that automatically, remote changes could alter behavior, so consider a review/check step before accepting updates.
Review Dimensions
- Purpose & Capability
- okName and description (booking flights, hotels, eSIMs with crypto) match the SKILL.md content: API base, endpoints, and credential model (CLIENT_ID, CLIENT_SECRET, optional USER_ACCESS) are appropriate for a web API integration.
- Instruction Scope
- noteThe SKILL.md specifies registration, header/signing rules, and careful handling of CLIENT_SECRET/USER_ACCESS. It also asks agents to 're-fetch this file regularly' to detect changes — reasonable for keeping an integration up-to-date, but be aware remote SKILL.md updates can change agent behavior if the agent automatically follows that guidance.
- Install Mechanism
- okNo install spec and no code files are included (instruction-only). This minimizes risk from arbitrary downloads or on-disk installs.
- Credentials
- noteThe skill expects API credentials (CLIENT_ID, CLIENT_SECRET, optional USER_ACCESS) which are proportionate to its purpose. However, the registry metadata does not declare required environment variables or a primaryEnv; the SKILL.md describes tokens and signing rules but the registry does not list where/how those credentials will be provided—this is an operational gap to verify before use.
- Persistence & Privilege
- okalways:false and no install mean the skill does not request elevated or permanent presence. Autonomous invocation is allowed (default) but not combined with other red flags.