ClawHub
Back to skill

Security audit

HTML CSS Style Color Guide

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only color guidance skill with some broad and rigid styling advice but no evidence of unsafe behavior.

Installers should treat this as a style preference guide, not a security-sensitive integration. Users should override its color bans when explicit user requirements, brand guidelines, or accessibility-tested designs call for different colors.

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
87% confidence
Finding
The manifest description says to use the skill when 'creating or updating HTML/CSS styles' and 'choosing colors for web pages,' which are very broad activities common to many frontend tasks. It does not provide narrower trigger phrases, scope constraints, or negative examples to distinguish when this skill should activate versus more general styling guidance.

Natural-Language Policy Violations

Medium
Confidence
76% confidence
Finding
The instructions state 'Never Use' for several colors, including broad categories like purple, magenta, and any hot color, regardless of user preference or project requirements. This reads as a hard organizational style mandate rather than optional guidance, and the file does not offer user choice or clarify that exceptions depend on user or brand requirements.

Static analysis

No suspicious patterns detected.