Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Robot Resources
v1.0.0Reduce LLM API costs by 60-90% with intelligent local routing + compress web content by 70-80% with token-optimized scraping. Free, runs locally, no markup....
⭐ 0· 80·0 current·0 all-time
byManuel Sobrino@manuelsobrino
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The stated purpose (route LLM calls to cheaper providers and compress web content) matches the actions described (local proxy on localhost:3838, routing to OpenAI/Anthropic/Google, scraper API). However the SKILL.md also instructs contacting api.robotresources.ai for an API key and describes a GitHub OAuth browser step; these items are plausible but not strictly required by a purely local router and are not declared in the registry metadata, creating a discrepancy between claim and requirements.
Instruction Scope
The instructions tell the agent/installer to run an npx package that will install a local proxy, possibly register a system service, modify agent model defaults to route all LLM calls, and may contact robotresources' remote API (signup path). The doc also gives a non-interactive API signup flow that produces an rr_live_... key and claim URL. The skill claims 'no Robot Resources servers in between' yet documents an API path and remote signup — a direct contradiction. The instructions do not ask to read arbitrary host files, but they do grant the installed software broad control over how all LLM calls are routed on the host.
Install Mechanism
There is no registry install spec, but SKILL.md directs use of 'npx robot-resources', which will fetch and execute code from the npm registry (or an npm-like registry). npx installs/executes remote code with full local privileges; the installer also may register a system service and auto-configure agent settings. This is a moderate-to-high risk install pattern unless the package and its source are audited.
Credentials
Registry metadata declares no required env vars or credentials, but the SKILL.md explicitly asks the user to export provider API keys (ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY) and may store/accept an RR_API_KEY from robotresources.ai. The mismatch between declared requirements and runtime instructions is concerning because the skill will rely on provider keys and an rr key but the registry did not surface these requirements.
Persistence & Privilege
The installer intends to run a background service (localhost:3838) and to modify agent configuration so that the agent's primary model routes through the local proxy. While the skill is not force-enabled (always:false), the described changes give the installed component broad ongoing control over all LLM traffic on the host, which is a significant persistent privilege and should be approved by the human operator.
What to consider before installing
Things to consider before installing:
- Do not run npx robot-resources without a human operator reviewing the package and code. npx executes remote code on your machine.
- The SKILL.md claims "your API keys never leave your infrastructure" but also documents contacting api.robotresources.ai and obtaining an rr_live_... key — ask for clarification and source code proving the local-only behavior.
- The installer may register a system service and set your agent to route all LLM calls through localhost:3838. That gives the installed software persistent control over LLM traffic; only proceed if you trust and have audited the package.
- The registry metadata did not declare required env vars, yet the runtime doc asks for OPENAI/ANTHROPIC/GOOGLE keys and possibly an RR_API_KEY. Confirm what credentials will be stored and where.
- If you consider installing: inspect the npm package and GitHub repo (verify authenticity, recent commits, maintainers), review the installer code and service registration scripts, run in an isolated or disposable environment first, and prefer a manual, audited install over blindly running npx.
If you cannot audit the package or verify the open-source repository and release provenance, treat this skill as high-risk and avoid installing it on production or privileged machines.Like a lobster shell, security has layers — review code before you run it.
latestvk974w483vz1wbk02tnsgtjzzbn839zvw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.