Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Lynkr AI Routing Proxy
v0.6.0Intelligent LLM routing proxy with complexity-based tier routing, agentic workflow detection, and multi-provider failover. Drop-in replacement for direct pro...
⭐ 0· 55·0 current·0 all-time
byVishal Veera Reddy@vishalveerareddy123
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name and description (an LLM routing proxy) match the SKILL.md content (tier routing, complexity scoring, multi-provider). However the registry metadata at the top of the evaluation says 'Required binaries: none' while the SKILL.md itself declares node >=18 and an npm package (lynkr) — an inconsistency between manifest metadata and the runtime instructions.
Instruction Scope
SKILL.md instructs installing a global npm package (npm install -g lynkr) and running a local proxy, plus enabling features like server-side tool execution and OPENCLAW_MODE which rewrites model names in responses. Those instructions imply executing third-party code and possibly server-side tool invocation (command execution), but the skill does not declare how or where provider credentials are configured. The doc also suggests adding an 'api_key' value of 'any-value' for openclaw.json, which is ambiguous and could enable an unauthenticated or misconfigured proxy if followed literally.
Install Mechanism
There is no formal install spec in the registry entry (instruction-only), but SKILL.md tells operators to use npm to install a published 'lynkr' package. Installing a public npm package is a standard workflow but carries inherent risk (you are executing third-party code); the instruction does not point to a verified release URL or checksum. This is moderate risk but expected for an npm-distributed tool.
Credentials
The skill declares no required environment variables in the metadata, yet the SKILL.md shows multiple env vars (MODEL_PROVIDER, TIER_* entries, OPENCLAW_MODE) and implies the proxy will use provider-specific credentials to call many cloud providers. The manifest omits any requirement for provider API keys or guidance on securely supplying them; the provided openclaw.json snippet uses 'api_key':'any-value', which is ambiguous and could encourage insecure deployment. Requesting no secrets in metadata while supporting many providers is inconsistent and should be clarified.
Persistence & Privilege
The skill is not marked always:true and does not request special persistent privileges in the registry metadata. It is user-invocable and can be invoked autonomously by the agent (default), which is expected for skills.
What to consider before installing
This skill appears to be a legitimate LLM routing proxy, but several things don't add up. Before installing or running it: 1) Inspect the actual npm package and GitHub repository (verify maintainer, recent commits, and code) rather than relying only on SKILL.md. 2) Confirm how provider API keys are configured and stored — do not run an unauthenticated public proxy. 3) Be cautious about installing a global npm package and running it as a service — review the package contents and any startup scripts. 4) If you enable OPENCLAW_MODE, understand it will expose the actual provider/model names in responses (possible metadata leakage). 5) Because the SKILL.md mentions server-side tool execution, limit network exposure and run it in an isolated environment until you’ve audited its behavior. Providing the repository URL, package tarball, or the lynkr source code would materially increase confidence and allow a more precise assessment.Like a lobster shell, security has layers — review code before you run it.
latestvk973vxr5c5agpat4xcr7s84xvh83d1wk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.