Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Uplo Knowledge Management
v1.0.0AI-powered knowledge management intelligence. Search taxonomies, content curation records, expertise directories, and communities of practice with structured...
⭐ 0· 88·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is described as an UPLO knowledge-management connector and the declared capabilities (search_knowledge, search_with_context, export_org_context, etc.) align with that purpose. The skill.json requires an agentdocs_url and api_key to reach an UPLO/MCP server — these credentials are appropriate for a connector of this type. (Note: the registry summary above listed no required env/config, but the included skill.json does declare two required config entries; this appears to be a metadata mismatch rather than malicious behavior.)
Instruction Scope
SKILL.md instructs the agent to call well-scoped MCP tools (get_identity_context, search_with_context, search_knowledge, export_org_context, report_knowledge_gap, etc.). These actions stay within knowledge-management activities (searching, exporting org context, flagging gaps). The instructions do not tell the agent to read unrelated system files, environment variables, or to send data to unknown external endpoints beyond the configured UPLO/MCP server.
Install Mechanism
There is no platform-level install spec in the registry listing, but the README and skill.json indicate the MCP server is run via npx @agentdocs1/mcp-server (npm). Fetching an npm package at runtime is a typical pattern for MCP adapters but carries the usual moderate risk of executing code fetched from the npm registry. No direct downloads from untrusted URLs or archive extracts are present.
Credentials
The only required configuration in skill.json is agentdocs_url and api_key (the UPLO/MCP instance URL and token). Those are proportionate to a knowledge-management connector. The skill does not request unrelated credentials or broad system-level secrets.
Persistence & Privilege
The skill is not always-enabled, does not request system-wide configuration changes, and contains no instructions to modify other skills. It operates as a connector that may read/export organizational context via the configured MCP endpoint — appropriate for its stated purpose.
Assessment
This skill appears to be a legitimate connector to an UPLO/MCP instance. Before installing: (1) verify you trust the UPLO instance URL and owner of the npm package (@agentdocs1), (2) supply a least-privilege API key (read-only if possible) because the skill can export organizational context and expertise data, (3) be aware that the MCP server is launched via npx which will fetch code from the npm registry — review the package and its publisher if you can, and (4) test in a non-production environment first to confirm the data returned and any automated actions (e.g., report_knowledge_gap) behave as you expect. Also note the registry metadata omitted required config but skill.json includes it — ensure you provision the listed agentdocs_url and api_key only if this aligns with your security policies.Like a lobster shell, security has layers — review code before you run it.
latestvk970r8m04ht8s56nsjjkem35hs8394gw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
