ClawHub
Back to skill

Security audit

Systematic Debugging

Security checks across malware telemetry and agentic risk

Overview

This debugging skill is mostly coherent, but it includes broad activation rules and credential-related diagnostic examples that could expose sensitive signing or environment details.

Review this before installing if you work with production systems, code signing, secrets, or CI credentials. Use the debugging process only with redaction-safe diagnostics, avoid dumping environment or keychain state into agent-visible logs, and treat the helper script as arbitrary command execution controlled by the command you pass.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (9)

Intent-Code Divergence

Medium
Confidence
95% confidence
Finding
The docstring claims the tool is 'Safe' because it runs only the command passed, but it still executes arbitrary user-supplied programs and can therefore perform destructive actions if invoked with a harmful command. This misleading safety framing can cause operators or downstream agents to trust and invoke it in contexts where arbitrary execution should be treated as dangerous.

Intent-Code Divergence

Low
Confidence
92% confidence
Finding
The file explicitly uses authority pressure, time pressure, and social conformity cues to push the reader toward bypassing the stated systematic debugging process. In an agent skill context, this is dangerous because it trains or prompts the agent to privilege interpersonal pressure over required verification steps, increasing the chance of unsafe or incorrect actions.

Vague Triggers

High
Confidence
95% confidence
Finding
The frontmatter description says to use the skill for virtually any technical issue, including broad prompts like 'debug this' or 'why error'. Overly broad activation criteria can cause the agent to invoke this skill in situations outside its intended scope, increasing the chance of inappropriate tool use or conflicting behavior.

Vague Triggers

Medium
Confidence
88% confidence
Finding
The secondary trigger guidance activates on any request that roughly matches the broad description, without precise boundaries. This can lead to accidental invocation and unsafe over-application of the debugging workflow in unrelated contexts.

Vague Triggers

High
Confidence
97% confidence
Finding
The 'When to Use' section explicitly says to use the skill for 'ANY technical issue' and emphasizes especially broad conditions like time pressure. In an agentic system, this creates an unsafe catch-all behavior that may override more specialized or safer skills.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The diagnostic example instructs printing secret availability and environment propagation details, which can expose sensitive operational state in logs. Even showing whether a secret is set, along with related environment and signing context, can aid attackers or leak internal configuration.

Ssd 3

Medium
Confidence
96% confidence
Finding
The multi-component debugging guidance encourages logging data at each boundary and includes examples that inspect environment state and signing identity context. In practice, this pattern can lead to secrets, tokens, credential metadata, or other sensitive state being exposed across logs and tool output during incident triage.

Credential Access

High
Category
Privilege Escalation
Content
env | grep IDENTITY || echo "IDENTITY not in environment"

   # Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v
Confidence
91% confidence
Finding
Keychain

Credential Access

High
Category
Privilege Escalation
Content
# Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v

   # Layer 4: Actual signing
Confidence
94% confidence
Finding
keychain

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Static analysis

No suspicious patterns detected.