ClawHub
Back to skill

Security audit

Knowledge to ClawHub Skill Publisher

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward documentation and ClawHub publishing workflow with no hidden execution, credential use, or deceptive behavior found.

Before installing, confirm you want a workflow that can help prepare and publish skills to ClawHub. Review generated packages for secrets, machine-specific tokens, and raw transcripts before publishing, as the skill itself also instructs.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Natural-Language Policy Violations

Low
Confidence
86% confidence
Finding
The document includes mandatory bilingual content, including Chinese text, but does not state that language presentation is optional or selected based on user preference. Under the stated policy, fixed language or locale behavior without opt-in can be a natural-language policy concern.

Natural-Language Policy Violations

Low
Confidence
89% confidence
Finding
The file presents the skill description in both English and Chinese and later instructs authors to 'prefer bilingual docs' for mixed audiences. This can be read as imposing a language/locale presentation choice by default rather than explicitly offering user choice or opt-in.

Natural-Language Policy Violations

Low
Confidence
93% confidence
Finding
The heuristic 'if the audience is mixed, prefer bilingual docs' establishes a default language policy. Because the rule does not mention asking the user or maintainer for language preference, it may conflict with policies requiring language/locale choice or opt-in.

Static analysis

No suspicious patterns detected.