Back to skill

Security audit

simplified-technical-english

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign because the reported behavior appears purpose-aligned, with one low-severity note about requiring American spelling; confidence is medium.

The verdict is benign, but not a guarantee of safety. Consider whether the American spelling requirement suits your preferences. The scan is incomplete: one local path-like reference was missing, so the evidence does not cover everything that reference may point to.

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
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • 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 (3)

The skill mandates American spelling without offering a locale choice or explaining why US spelling is required.

Low
Category
Output Handling
Confidence
87% confidence
Finding

The adopted rules explicitly require American spelling. Although an English-language register is central to this skill, the file does not justify this specific regional constraint or let users retain their preferred English locale.

Content

No source excerpt is available for this finding.

The adopted rules mandate American spelling without user opt-in or a stated locale-specific justification.

Low
Category
Output Handling
Confidence
92% confidence
Finding

The American-spelling rule imposes a specific locale repository-wide without offering users a choice. The existing implementation is cited, but no justification is given for requiring this locale rather than respecting the user's preferred spelling convention.

Content

No source excerpt is available for this finding.

American spelling is required without user opt-in or a documented locale-specific justification.

Low
Category
Output Handling
Confidence
96% confidence
Finding

The conflict table marks American spelling as required under both the house rules and STE, imposing a specific locale on governed text. The file provides neither a user choice nor a locale-specific justification for this requirement.

Content

No source excerpt is available for this finding.