Skill flagged — suspicious patterns detected

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

lessie

v1.0.0

Search, qualify, and enrich people and companies. Use this skill whenever the user wants to find professionals, candidates, or KOLs by title, company, locati...

1· 57·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
Benign
medium confidence
Purpose & Capability
Name/description (people search, enrichment, company research) match the instructions: CLI and MCP client workflows, web_search/web_fetch, enrich/find tools. No unrelated credentials or unrelated binaries are requested.
Instruction Scope
SKILL.md tells the agent to check for the lessie CLI, run `npm install -g @lessie/cli` if missing, call `lessie` subcommands, or fall back to an MCP server. It also instructs opening a browser for OAuth and caching a token at ~/.lessie/oauth.json. These are expected for a CLI-based enrichment tool but do cause local installs, disk writes, and a browser-based auth flow (user confirmation is mandated in the doc). The fallback generic `lessie tools` + `lessie call` workflow can relay arbitrary parameters to the remote service — expected for a tool client but worth noting because it lets the agent send arbitrary JSON payloads to Lessie's remote API.
Install Mechanism
No compiled code is shipped in the skill; the doc recommends installing the @lessie/cli and/or running npx @lessie/mcp-server. Installing from npm is a standard but nonzero risk (packages execute code during install and may be updated on the registry). This install mechanism is proportionate to a CLI client but you should confirm the npm package reputation before global installation or use a sandbox/container.
Credentials
The skill declares no required env vars or credentials. Examples include an optional LESSIE_REMOTE_MCP_URL for MCP configuration and note that OAuth tokens are cached at ~/.lessie/oauth.json. Those are reasonable for a remote enrichment service; no unrelated secrets (AWS, GitHub, etc.) are requested.
Persistence & Privilege
Skill does not request always:true and does not ask to modify other skills. It will create/modify its own config and token under ~/.lessie and may add an MCP entry if the user follows instructions — that is normal for a CLI/MCP integration and within expected scope.
Assessment
This skill appears to do what it says: act as a client for the Lessie people-search service. Before installing or allowing the agent to auto-install: (1) Verify the npm package @lessie/cli and the domain lessie.ai (check package page, maintainers, and recent versions); (2) Prefer running npm install inside a sandbox/container or use the MCP pattern (npx @lessie/mcp-server) if you want to avoid a global install; (3) Be aware the OAuth token will be stored at ~/.lessie/oauth.json — protect that file and revoke tokens if needed; (4) Understand that calling `lessie call` can send arbitrary JSON to Lessie's servers, so avoid sending sensitive secrets/content to the service; (5) Review Lessie's privacy and terms pages and ensure your use of enriched contact data complies with local laws (GDPR, CAN-SPAM). If you want a higher-assurance verdict, provide the actual npm package contents or the published package URL for a more thorough code-level review.

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

latestvk97dzve5m0trdce1t0vw10vf6n83zgzp

License

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

Comments