Skillv1.0.0

ClawScan security

Trio Stream Vision · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 10, 2026, 6:07 PM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requirements and runtime instructions match its stated purpose (sending live-stream frames to Trio's Vision API using a TRIO_API_KEY); nothing requested is disproportionate or unrelated.
Guidance: This skill is coherent with its description: it sends stream URLs/frames to Trio's cloud API and requires a TRIO_API_KEY. Before installing, consider: 1) privacy — frames/clips from your cameras will be uploaded to a third party (machinefi/trio); do not point it at cameras you don't own or at people without consent; 2) webhook recipients — if you configure a webhook, that endpoint will receive event data (and optionally frames); ensure you control/trust it; 3) key handling — store TRIO_API_KEY securely (not in shared scripts or public repos), rotate it if exposed, and prefer a key with limited scope if the provider supports it; 4) cost/control — continuous monitoring incurs per-minute charges, so limit durations/intervals and warn users before starting long monitors; 5) vet the provider — confirm you trust machinefi/trio for handling sensitive visual data. If you want stronger guarantees, ask the publisher for an on-prem or self-hosted option or more explicit documentation about data retention and access controls from Trio.

Review Dimensions

Purpose & Capability: okThe skill is an instruction-only wrapper around Trio's Vision-as-an-API. Requiring a TRIO_API_KEY and a CLI (curl or python3 for JSON formatting) is directly aligned with the described capability of analyzing livestreams via Trio's API. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope: noteSKILL.md instructs the agent to POST stream URLs and natural-language conditions to Trio endpoints (check-once, live-monitor, live-digest), and optionally to request frames/clips (base64) or deliver events to a webhook. The instructions remain within the described scope, but they explicitly send visual data to an external cloud service (trio.machinefi.com) and allow delivery to arbitrary user-supplied webhooks — both of which have privacy implications and deserve user attention before enabling the skill.
Install Mechanism: okNo install spec or binary downloads are present; this is SKILL.md-only and uses existing system tools (curl/python3). That is the lowest-risk install model and consistent with the stated approach.
Credentials: okOnly one environment variable (TRIO_API_KEY) is required and it's the primary credential needed to call Trio's API. There are no unrelated secrets or excessive env requirements.
Persistence & Privilege: okThe skill does not request always:true, has no special persistence or privileged system access, and does not attempt to modify other skills or system-wide configs. Autonomous invocation is possible (platform default) but is not combined with other concerning privileges.