ClawHub
Back to skill

Security audit

Bug Report Formatter Skill

Security checks for vulnerabilities and agentic risk

Overview

This is a simple bug-report templating skill with no executable code, persistence, credential handling, or hidden high-impact behavior.

Installers should understand this skill may be invoked a bit broadly for software-quality planning, but its instructions are transparent and limited to reusable bug-report-oriented templates. Avoid pasting secrets or unnecessary personal data into bug reports, consistent with the skill's own safety rules.

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 (2)

Vague Triggers

Medium
Confidence
91% confidence
Finding
The 'When to use' section is broad enough to match many ordinary software-help requests, such as wanting structured guidance or reusable prompts, without strongly tying invocation to bug report formatting specifically. This can cause the skill to activate outside its intended scope, leading to inappropriate prompt injection of its instructions into unrelated tasks and reducing routing precision.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The example prompt 'Help me outline a concise plan using the Bug Report Formatter approach' uses everyday language that is generic enough to overlap with many harmless planning requests. If the platform uses example phrases as invocation cues, this increases the chance of accidental triggering in unrelated contexts, which can misroute user intent and inject irrelevant skill behavior.

Static analysis

No suspicious patterns detected.