Back to skill
Skillv1.0.2
ClawScan security
WhenToMeet · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousMar 13, 2026, 1:51 PM
- Verdict
- suspicious
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's documentation and examples clearly require a WhenToMeet API key, but the registry metadata does not declare any required credential — this mismatch is incoherent and should be clarified before installing.
- Guidance
- Before installing, confirm how and where the skill expects the WhenToMeet API key to be provided (the skill examples use Authorization: Bearer sk_... but the registry shows no required env var). Only provide a dedicated, limited-scope API key (not a shared or high-privilege secret). Verify the domain (whentomeet.io) is the official service you trust, and review the OpenAPI / docs links listed in the skill to ensure endpoints and scopes match your expectations. Because this is instruction-only, it won't install code locally, but it will make network calls to the listed API—consider the privacy of any event data you allow the skill to send. If anything is unclear, ask the skill author to (1) declare the exact env var/credential name the agent will use, (2) confirm required scopes, and (3) explain how the agent stores/uses the key.
Review Dimensions
- Purpose & Capability
- concernThe skill claims to provide group scheduling via the WhenToMeet public REST API, which legitimately requires a service API key for authenticated endpoints (examples show Authorization: Bearer sk_YOUR_API_KEY_HERE). However, the registry metadata lists no required env vars or primary credential while the SKILL.md header metadata includes requires:["api-key"]. This inconsistency between declared requirements and the runtime instructions is a coherence problem.
- Instruction Scope
- okSKILL.md and the reference file only describe calling whentomeet.io endpoints (cURL examples, endpoint list, OpenAPI link). The instructions do not ask the agent to read local files, shell history, or unrelated environment variables, nor do they instruct exfiltration to unknown endpoints. Scope stays within the scheduling API.
- Install Mechanism
- okThis is instruction-only (no install spec, no code files). Nothing is written to disk by an installer step, which reduces the surface area.
- Credentials
- concernThe API requires a bearer API key for authenticated endpoints, but the skill does not declare the required env var name or a primaryEnv in the registry metadata. That omission makes it unclear what credential the agent will ask for or where you should store it. Ensure any provided key is limited-scope and not a high-privilege secret used elsewhere.
- Persistence & Privilege
- okThe skill does not request always:true and has normal invocation settings. There are no instructions that modify other skills or system-wide settings.