ClawHub
Back to skill

Security audit

任务编排与调度 (Agentic AI 科研平台)

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent demo clinical-research workflow skill that reads mock files and reports progress locally, with no hidden installer, credential use, or destructive behavior found.

Install this only if you want a local demo workflow for clinical research orchestration and have the referenced mock_data files and localhost monitoring service. Before using it with real institutional or patient-related data, confirm authorization and ensure the local reporting endpoint will not store sensitive task details.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
89% confidence
Finding
The trigger conditions are broad enough to match ordinary user requests for analysis, which can cause the orchestrator to activate unexpectedly. In this skill, accidental activation is more dangerous because it initiates multi-step workflow behavior, including progress reporting and access to mock clinical-research-related data files, without an explicit confirmation gate.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill states it will report progress to a local monitoring backend but does not clearly warn users that task metadata will be transmitted externally to the conversation flow. Even though the endpoint is localhost, this still sends data to another service/process, creating a transparency and privacy risk, especially in a clinical research context.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The workflow involves reading internal data dictionary information and export-governance details tied to patient-level risk, but the document does not warn about the sensitivity of this access. In a healthcare setting, omission of this warning increases the chance that users trigger handling of sensitive institutional or patient-related metadata without informed approval.

Static analysis

No suspicious patterns detected.