ClawHub
Back to skill

Security audit

Turkish

Security checks for vulnerabilities and agentic risk

Overview

This is a plain writing-style skill for casual Turkish with no code, tools, data access, or persistence.

Install this if you want Turkish output to sound casual and native-like. Avoid relying on it for formal, legal, academic, or professional Turkish unless you explicitly ask the assistant to use a formal register.

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
88% confidence
Finding
As a markdown skill file, this should clearly indicate when the skill should activate and what requests it is meant to handle. The name and description define a broad writing style goal ('Write Turkish that sounds human') but do not specify concrete trigger phrases, boundaries, or negative examples, which could lead to unintended invocation for general Turkish-writing tasks.

Natural-Language Policy Violations

Medium
Confidence
93% confidence
Finding
The file instructs the system to produce Turkish in a specific colloquial register by default, but it does not state that this behavior depends on the user's preference or explicit request. That can amount to forcing a language/locale style without opt-in, which is a natural-language policy issue.

Static analysis

No suspicious patterns detected.