← Back to Skills Marketplace
roojenkins

Uplo Consulting

by RooJenkins · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
234
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install uplo-consulting
Description
AI-powered consulting knowledge management. Search engagement records, methodology frameworks, deliverable templates, and best practices with structured extr...
Usage Guidance
This skill appears to be a legitimate connector to an UPLO consulting knowledge service, but there are packaging inconsistencies and a moderate installation risk to consider. Before installing: 1) Verify the publisher and contents of the npm package @agentdocs1/mcp-server (review its code or use a vetted internal mirror). 2) Confirm the correct UPLO instance URL and create an API key scoped to the minimum required permissions (read-only search, and separate keys for logging/writes if needed). 3) Treat the API key as a secret and do not reuse highly privileged cloud/service keys. 4) Because the registry listing omitted the required credentials while skill.json requires them, expect the agent to request or need an API key — do not supply credentials until you confirm the endpoint and package. 5) If possible, run the MCP server in an isolated environment or behind network controls and monitor traffic to ensure data remains within your org. If you cannot verify the npm package or do not want to provide an external API key, do not install.
Capability Analysis
Type: OpenClaw Skill Name: uplo-consulting Version: 1.0.0 The skill bundle provides a legitimate interface for a consulting knowledge management platform (UPLO). The instructions in SKILL.md and identity-patch.md are well-aligned with the stated purpose of retrieving engagement records and methodology frameworks, and the MCP configuration in skill.json uses standard patterns for connecting to an external API via the @agentdocs1/mcp-server package.
Capability Assessment
Purpose & Capability
The skill's name/description and SKILL.md consistently describe a consulting knowledge retrieval tool (search_knowledge, search_with_context, get_directives, export_org_context, etc.) and the declared capabilities align with that purpose. However, the registry metadata provided earlier lists no required credentials while the included skill.json clearly requires an UPLO instance URL and an API key — a packaging/manifest inconsistency that could cause the agent to request secrets unexpectedly.
Instruction Scope
SKILL.md instructs only on querying the UPLO knowledge service and logging conversation metadata (e.g., get_identity_context, get_directives, search_knowledge, log_conversation). It does not ask the agent to read unrelated local files, environment variables, or exfiltrate data to unexpected endpoints. The identity-patch biases the agent to consult UPLO first, which is functionally expected for this skill but should be noted as behavioral biasing.
Install Mechanism
There is no explicit 'install spec' in the registry, but skill.json and README show an MCP runtime that runs via 'npx @agentdocs1/mcp-server --http' (i.e., fetching and executing an npm package at runtime). Using npx to fetch/execute a remote npm package is a moderate risk (remote code execution at install/run time). The package origin (@agentdocs1) is not a widely known system package in this metadata — verify the npm package, its publisher, and contents before running.
Credentials
The skill requires an external service URL and an API key (agentdocs_url / api_key) to function. Those are reasonable for a knowledge-base integration, but the earlier registry summary claiming 'no required env vars / primary credential: none' contradicts the included skill.json and README. That mismatch is concerning because it means the skill may prompt for or expect sensitive credentials even though the registry listing did not declare them. Ensure the API key is least-privilege and that you understand what scopes the UPLO MCP token grants (search, read/export, write/logging).
Persistence & Privilege
The skill is not set to always:true and does not request elevated platform privileges or modify other skills. Autonomous invocation is allowed (default) but not by itself a red flag here. The skill does include an identity patch that biases use toward UPLO data, which is expected for a knowledge connector.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install uplo-consulting
  3. After installation, invoke the skill by name or use /uplo-consulting
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of uplo-consulting. - Enables AI-powered consulting knowledge management with structured retrieval. - Search and extract engagement records, frameworks, templates, and best practices. - Provides tooling for proposal development, staffing, onboarding, and lessons learned. - Includes directives and reporting functions to support firm operations and compliance.
Metadata
Slug uplo-consulting
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Uplo Consulting?

AI-powered consulting knowledge management. Search engagement records, methodology frameworks, deliverable templates, and best practices with structured extr... It is an AI Agent Skill for Claude Code / OpenClaw, with 234 downloads so far.

How do I install Uplo Consulting?

Run "/install uplo-consulting" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Uplo Consulting free?

Yes, Uplo Consulting is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Uplo Consulting support?

Uplo Consulting is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Uplo Consulting?

It is built and maintained by RooJenkins (@roojenkins); the current version is v1.0.0.

💬 Comments