Auto Rename Session Label

• Outcome: Review
• Latest audit: Jun 21, 2026 at 4:02 PM UTC
• Version:
  1.0.0

Overview

This skill does what it claims, but its install trigger is too broad for a persistent hook that changes OpenClaw behavior automatically.

Install only if you intentionally want a persistent OpenClaw hook that auto-labels new sessions. Before running the workflow, confirm the install request is explicit, review the hook code, and remember it will send the first user message to the same model/provider used by that session to generate a title.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The instruction to run the install workflow whenever the listed triggers are 'seen/heard' is overly broad and can cause the agent to perform filesystem writes and enable a persistent hook without confirming user intent or execution context. Because the workflow installs and activates code, ambiguous activation materially increases the risk of unintended persistence or social-engineering-triggered execution.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: At least one trigger phrase is broad enough to overlap with ordinary conversation about chat naming or session titles, making accidental activation plausible. In this skill, accidental activation is more dangerous because the action is not read-only: it copies files, enables a hook, and creates persistent behavior in the user's OpenClaw environment.

VirusTotal

64/64 vendors flagged this skill as clean.