ClawHub
Back to skill

Security audit

SRE & Incident Management Platform

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only SRE skill with production-impacting guidance that is expected for its stated purpose, but users should authorize any real operational changes.

Installers should treat this as an SRE playbook. Before applying its incident, chaos, or self-healing recommendations to live systems, require an authorized operator, confirm blast radius, validate rollback plans, and avoid letting an agent execute production changes automatically.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

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

Vague Triggers

Medium
Confidence
88% confidence
Finding
The quick-start examples are highly generic trigger phrases that could cause the skill to activate in a wide range of contexts without clear scope limits, preconditions, or exclusions. Because this is an SRE and incident-management skill, over-broad activation could lead the agent to provide incident-response or operational guidance when the user did not explicitly intend to invoke this skill, increasing the chance of inappropriate or unsafe actions during production-related workflows.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The incident response workflow instructs operators to use rollback, feature disabling, traffic shifts, scaling changes, and manual data fixes as mitigation options. In a markdown skill description, these behaviors should be accompanied by clear warnings about possible impact to production systems and data integrity, but none are provided.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
This markdown file specifies automated remediation actions such as deleting pods, running cleanup scripts, archiving data, killing connections, and triggering renewals. The surrounding skill description does not include a user-facing warning that these actions may affect system availability or data, which matches the markdown-specific missing-warning criterion.

Static analysis

No suspicious patterns detected.