ClawHub
Back to skill

Security audit

Error Decoder

Security checks for vulnerabilities and agentic risk

Overview

This is a simple error-explanation skill with no executable code, persistence, credential access, or hidden data movement.

Installing this skill should be reasonable if you want structured explanations of errors, but treat diagnoses based on partial traces as hypotheses and verify fixes before applying them to important code.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Anti-Refusal Statement

High
Category
Anti-Refusal
Content
## Working from a brief

You'll often get just an error string or a partial stack trace, with no surrounding code. **Always deliver a complete diagnosis anyway** — infer the language/framework and the likely context from the error itself, and mark inferences as *(assumed — confirm)*. Never refuse for missing context and never leave bracketed placeholders.

## Input
Confidence
95% confidence
Finding
The instruction to 'Never refuse for missing context' pressures the agent to provide a complete diagnosis from incomplete evidence, encouraging hallucinated root causes and unsafe, overconfident fixes. In a debugging skill, this is especially risky because stack traces and error strings often lack the surrounding code, environment, secrets handling, or production constraints needed for a trustworthy remediation.

Vague Triggers

Medium
Confidence
94% confidence
Finding
The skill description is broadly scoped to common debugging and error-explanation requests, which creates ambiguous trigger boundaries and increases the chance of over-invocation. In an agent setting, that can cause the skill to activate on general coding conversations and steer responses toward speculative debugging guidance even when the user did not explicitly request this specialized behavior.

Static analysis

No suspicious patterns detected.