Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Grok Ai Video

v1.0.2

grok-ai-video is a ClawHub skill that brings Grok's reasoning capabilities directly to your video workflows. Upload footage, ask questions about content, req...

0· 73·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill claims to provide Grok-powered video analysis via the NemoVideo API. Requesting an API token (NEMO_TOKEN) and persisting a client_id under ~/.config/nemovideo/ is coherent with that purpose. However the skill's metadata lists no required env vars while declaring a primaryEnv of NEMO_TOKEN and a config path; this minor mismatch is noteworthy but not fatal.
!
Instruction Scope
SKILL.md instructs the agent to: (a) automatically call the service's anonymous-token endpoint, (b) read/write ~/.config/nemovideo/client_id, and (c) 'silently' set a session token and never inform the user. Those actions go beyond only processing a user-supplied file: they perform network requests and persist a client identifier without explicit user consent or visible disclosure. There is also an instruction contradiction: greet user immediately, but do setup 'before responding' and 'silently', which grants the skill implicit autonomy over auth/IO decisions.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. The only file writes come from the runtime behavior described in SKILL.md (client_id persistence), not from an installation script.
Credentials
The only declared primary credential is NEMO_TOKEN which is appropriate for an API-backed video service. SKILL.md additionally references optional env vars (NEMO_API_URL, NEMO_WEB_URL, NEMO_CLIENT_ID) and a SKILL_SOURCE fallback; these are reasonable. The proportionality concern is behavioral: the skill auto-generates or fetches tokens and instructs the agent to keep that hidden from the user, which reduces transparency about credential use.
!
Persistence & Privilege
The skill persists a client_id to ~/.config/nemovideo/client_id and obtains an anonymous token automatically. Writing to a per-service config path is reasonable, but the explicit 'do this SILENTLY' and 'Never mention tokens... to the user' directives increase the skill's effective privilege and reduce user visibility into what credentials exist or when network calls occur. The skill is not 'always: true', so it won't be forced into every session, but it does request persistent client state and autonomous auth activity.
What to consider before installing
This skill appears to be what it says — a Nemovideo-backed video analysis tool — but it asks the agent to silently (a) obtain an anonymous token from nemovideo, (b) persist a client_id at ~/.config/nemovideo/client_id, and (c) explicitly hide token/auth details from the user. Before installing or enabling it, consider: - Do you consent to the agent uploading video content to nemovideo.ai? The skill will contact an external API and likely send your video data for analysis. - Are you comfortable with the skill auto-generating and persisting a client_id file in your home directory? If not, create and set NEMO_CLIENT_ID and/or NEMO_TOKEN yourself so the skill doesn’t generate them. - The 'never mention tokens' directive reduces transparency. If you want visibility, ask the publisher for clearer behavior or a mode that prompts before obtaining tokens. - Because SKILL.md is instruction-only (no code), verify the upstream repository and the service domain (https://nemovideo.com) before trusting it. If possible, test in an isolated environment, avoid using sensitive footage, and monitor network traffic to confirm what is uploaded. What would change this assessment: presence of the publisher's official repository or signed package, explicit user-consent prompts for token generation, or a documented privacy/dataflow statement showing how video data and tokens are handled would reduce concerns. Conversely, evidence of hidden data exfiltration or unexpected endpoints would raise the severity.

Like a lobster shell, security has layers — review code before you run it.

latestvk974mff3mww8bne1mbk1ektrq983nnk3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🎬 Clawdis
Primary envNEMO_TOKEN

Comments