ClawHub
Back to skill

Security audit

Api Changelog Drafter

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation helper that drafts API changelog material and does not request system access, persistence, credentials, or automatic publishing authority.

Before using the output in a real release, have engineering verify breaking-change classifications, semantic-version recommendations, and any removal or sunset dates. The skill should be treated as a drafting aid, not an authority to publish release policy.

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

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 216)May include surrounding context.

md
- This skill does not have access to your codebase or version control. All change data must be provided by the user.
- Incorrect version bump recommendations or incomplete breaking-change flags could cause downstream integration failures. Engineering must verify all classifications before release.
- Do not publish deprecation or removal timelines without confirmation from the product or engineering team that the timeline is final.

## Feedback

Static analysis

No suspicious patterns detected.