← Back to Skills Marketplace
Uplo Clinical
by
RooJenkins
· GitHub ↗
· v1.0.0
· MIT-0
247
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install uplo-clinical
Description
AI-powered clinical operations intelligence spanning pharmaceutical development and healthcare delivery. Unified search across clinical trials, protocols, an...
Usage Guidance
Before installing: (1) Note the inconsistency — the registry lists no required credentials but skill.json/README require a UPLO URL and an API key; confirm this is intentional and request updated metadata. (2) Treat the API key as sensitive: provision a scoped, least-privilege token (preferably for a non-production/sandbox instance) and confirm logging/audit locations and retention policies. (3) Verify the npm package '@agentdocs1/mcp-server' publisher and integrity before running npx (npm packages execute code during install/run). (4) Confirm organizational compliance (HIPAA/GxP) for sending identity context and clinical data to the configured UPLO instance and ensure classification tiers are enforced by the instance. (5) If you lack confidence in the publisher or need tighter control, run the MCP server in a sandbox environment and inspect network traffic and logs first. If the author cannot reconcile the metadata mismatch or provide provenance for the npx package, treat the skill as risky.
Capability Analysis
Type: OpenClaw Skill
Name: uplo-clinical
Version: 1.0.0
The uplo-clinical skill is a specialized integration for the UPLO clinical intelligence platform, designed to facilitate search and management of pharmaceutical and healthcare data. It utilizes an MCP server (@agentdocs1/mcp-server) to provide tools for clinical trial analysis, regulatory compliance, and organizational context retrieval. While the skill handles sensitive information and includes high-privilege tools like 'export_org_context' and 'get_identity_context', its instructions in SKILL.md and identity-patch.md are strictly aligned with its stated purpose of clinical operations and pharmacovigilance, with no evidence of malicious intent or unauthorized data exfiltration.
Capability Assessment
Purpose & Capability
The skill's functions (search_with_context, search_knowledge, get_directives, export_org_context, logging) align with a clinical knowledge-management product. The declared config in skill.json (agentdocs_url + api_key) is appropriate for connecting to a UPLO/MCP server. However, the registry metadata above lists 'required env vars: none' and 'primary credential: none', which contradicts skill.json and README that require an API key and URL.
Instruction Scope
SKILL.md instructs the agent to immediately pull identity context, check directives, run searches, and log pharmacovigilance sessions. Those actions are within the stated clinical operations scope. The instructions do require access to identity/clearance context and to log audit trails, which is expected for pharmacovigilance workflows, but also means the agent will handle sensitive identity and patient-related metadata — SKILL.md does state to respect classification tiers.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but README and skill.json indicate running an MCP server via 'npx @agentdocs1/mcp-server --http' and setting AGENTDOCS_URL/API_KEY. Using npx/npm to pull and run an MCP server is a moderate-risk install path because it will execute code from the npm package at runtime. The package name @agentdocs1/mcp-server should be verified (publisher, integrity, and intended behavior) before installation.
Credentials
The skill.json requires agentdocs_url and api_key (an MCP token) which are proportionate to the service, but the publicly visible registry metadata lists no required env vars/credentials — this mismatch is a red flag. The skill will have access to organization identity context and potentially sensitive clinical data when given the API key; ensure the API key has least privilege and is scoped to an appropriate environment (test/sandbox) before granting access.
Persistence & Privilege
always is false and the skill does not request system-wide persistent privileges. The skill's behavior is limited to interacting with the remote MCP/UPLO instance and logging to the knowledge base; it does not claim to modify other skills or global agent configs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install uplo-clinical - After installation, invoke the skill by name or use
/uplo-clinical - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
uplo-clinical 1.0.0 — Initial Release
- Launches unified AI-powered clinical operations intelligence for pharmaceutical and healthcare workflows
- Enables role-based access, session context, and up-to-date directive retrieval for clinical users
- Provides comprehensive search across trial protocols, patient care documentation, and operational SOPs
- Supports use cases in pharmacovigilance signal detection, formulary review, quality metrics, and regulatory preparation
- Introduces tools for knowledge gap reporting, organizational context export, and structured logging of audit activities
Metadata
Frequently Asked Questions
What is Uplo Clinical?
AI-powered clinical operations intelligence spanning pharmaceutical development and healthcare delivery. Unified search across clinical trials, protocols, an... It is an AI Agent Skill for Claude Code / OpenClaw, with 247 downloads so far.
How do I install Uplo Clinical?
Run "/install uplo-clinical" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Uplo Clinical free?
Yes, Uplo Clinical is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Uplo Clinical support?
Uplo Clinical is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Uplo Clinical?
It is built and maintained by RooJenkins (@roojenkins); the current version is v1.0.0.
More Skills