ClawHub
Back to skill

Security audit

Emergency After Action Report

Security checks for vulnerabilities and agentic risk

Overview

This skill is a structured drafting workflow for emergency after-action reports and includes clear safeguards for review, evidence, sensitivity handling, and non-distribution.

Before using it, confirm the report's sensitivity level and avoid pasting classified, PHI, or unnecessary personal details into the session. Treat all generated ratings and corrective actions as draft material requiring sponsor or incident-commander review before distribution.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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 (1)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 150)May include surrounding context.

Recommendation (preview): [one-sentence preview of corrective action]

text

Every Area for Improvement must reach root cause. Do not stop at "we did not have enough staff" without asking why. Capability-element tagging (POETE) is mandatory — corrective actions later flow from these tags.

### Step 10: Internal Consistency Check