ClawHub

Pilot Status Page Setup

Security checks across malware telemetry and agentic risk

Overview

This is a coherent status-page setup skill that clearly describes installing role-specific Pilot skills, configuring agents, and sending status notifications, with some operational privacy and overwrite cautions to review.

Before installing, confirm you trust pilotctl, clawhub, and the referenced pilot-* skills. Back up or inspect ~/.pilot/setups/status-page.json before running the manifest write step, and review incident payloads so public status pages, subscriber emails, and Slack channels do not receive internal hostnames, private endpoints, secrets, or unnecessary outage details.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill explicitly describes sending incident notifications to subscribers via email and Slack, but provides no warning that operational data will be disclosed to third parties or guidance on limiting message contents. In a status-page workflow, incident messages can easily expose internal service names, outage details, URLs, or timing information, creating unnecessary privacy and information-disclosure risk if operators follow the example as written.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill instructs the agent to write `~/.pilot/setups/status-page.json` using shell redirection, which will overwrite any existing manifest at that path without checking or warning the user. Because this is a setup skill that persists configuration, silent replacement can destroy prior local setup state or reconfigure an existing deployment unintentionally.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The publisher manifest and workflow clearly describe sending status and incident data to external systems, including a public status page API, subscriber notifications, and Slack channels, but the skill does not prominently warn the user before enabling those outbound flows. In an incident-management context, this can lead to unintended disclosure of outage details, internal service names, and incident metadata to public or third-party destinations.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal