Skill flagged — suspicious patterns detected

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

Uplo Consulting

v1.0.0

AI-powered consulting knowledge management. Search engagement records, methodology frameworks, deliverable templates, and best practices with structured extr...

0· 207·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for roojenkins/uplo-consulting.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Uplo Consulting" (roojenkins/uplo-consulting) from ClawHub.
Skill page: https://clawhub.ai/roojenkins/uplo-consulting
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install uplo-consulting

ClawHub CLI

Package manager switcher

npx clawhub@latest install uplo-consulting
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
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.
What to consider before installing
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.

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

latestvk97d00mf3059g0vc3565yz2n258356qf
207downloads
0stars
1versions
Updated 23h ago
v1.0.0
MIT-0

UPLO Consulting — Firm Knowledge at Your Fingertips

Consulting firms are knowledge businesses that routinely forget what they know. The partner who led the airline digital transformation last year is on a different engagement; the associate who built the market sizing model left six months ago; the methodology deck from the supply chain practice sits in someone's OneDrive. UPLO Consulting captures engagement artifacts, methodology IP, proposal content, and lessons learned so the firm's collective intelligence is accessible to every team, on every engagement, without playing "who do I ask?"

Session Start

Fetch your identity to establish your practice area, seniority level, and current engagement assignments:

get_identity_context

Review firm-wide directives — these typically include utilization targets, proposal approval thresholds, and client confidentiality mandates:

get_directives

When to Use

  • Staffing a new engagement and need to find consultants who have delivered similar work (industry, capability, geography)
  • Building a proposal and looking for relevant case studies, win rates for similar pursuits, and reusable methodology sections
  • Starting a workstream and want to see how a previous team structured a similar analysis (e.g., total cost of ownership model for a manufacturing client)
  • Preparing a client steering committee deck and need the firm's standard framework for presenting transformation roadmaps
  • Conducting a lessons-learned review and want to surface patterns across multiple completed engagements
  • Looking for the firm's published point of view on a topic (e.g., AI in financial services) to reference in a client workshop
  • Checking what deliverables were produced on a past engagement before scoping a follow-on

Example Workflows

Proposal Development

A principal is pursuing a healthcare payer operational improvement engagement and needs to build the proposal over a weekend.

search_with_context query="healthcare payer operations improvement engagement case studies outcomes"

Find reusable methodology content from the operations practice:

search_knowledge query="operational excellence methodology framework Lean Six Sigma consulting deliverables"

Pull the firm's current strategic priorities to align the proposal narrative:

get_directives

Identify consultants with relevant experience for the proposed team:

search_knowledge query="healthcare payer experience consultants managed care claims processing"

Engagement Kickoff Knowledge Transfer

A manager is starting on a new engagement and the previous phase was led by a different team. They need to get up to speed.

export_org_context
search_with_context query="client ABC Phase 1 findings current state assessment key recommendations"
search_knowledge query="client ABC stakeholder map decision makers change readiness assessment"
log_conversation summary="Onboarded to client ABC Phase 2; reviewed Phase 1 findings, stakeholder map, and org context" topics='["engagement-onboarding","client-ABC","knowledge-transfer"]' tools_used='["export_org_context","search_with_context","search_knowledge"]'

Key Tools for Consulting

search_with_context — Consulting questions are inherently cross-cutting. "What did we learn from similar engagements?" requires connecting engagement records with client industries, methodologies used, and outcomes achieved. The graph traversal assembles this narrative. Example: search_with_context query="retail supply chain transformation engagements outcomes cost savings"

search_knowledge — When you need a specific artifact: a deliverable template, a framework diagram source, a pricing model, or a named methodology. Example: search_knowledge query="zero-based budgeting methodology template"

export_org_context — Produces the firm's practice structure, leadership, key systems (CRM, time tracking, knowledge management), and strategic priorities. Indispensable for new hire orientation and cross-practice collaboration.

get_directives — Firm directives govern proposal approval thresholds, travel policies, rate cards, and client confidentiality walls. Check before making commitments to clients.

report_knowledge_gap — If a pursuit team cannot find case studies for a new capability area, that is a strategic signal. Flagging the gap helps the practice development team prioritize IP creation.

Tips

  • Client names may be anonymized in the knowledge base due to confidentiality agreements. Search by industry, engagement type, and capability rather than relying solely on client names.
  • Methodology frameworks are often versioned. Include "latest" or "v3" qualifiers if the firm maintains multiple generations of a methodology to avoid pulling deprecated content.
  • When building proposals, combine search_with_context (for case studies and outcomes) with search_knowledge (for specific deliverable examples) — they serve complementary retrieval patterns.
  • Always log proposal development sessions. Win/loss analysis relies on understanding what knowledge was available to the pursuit team at the time of proposal submission.

Comments

Loading comments...