ClawHub
Back to skill

Security audit

Story Bank Builder

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed marketing workflow that builds reusable story-bank documents and only saves project memory after user confirmation.

Before installing, be comfortable with the skill reading your project memory and user-provided customer/interview materials, and only confirm saving when you want story-bank outputs and pending proof proposals written to project memory.

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 68)May include surrounding context.

md
## Save Results

After delivering the story bank, ask: "Save these results for future sessions?" On confirmation, save to `memory/narrative/story-bank-builder/YYYY-MM-DD-<topic>.md` — see [skill-contract.md](../../../references/skill-contract.md) §Save Results Template. Every unbacked proof goes only to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`; any canon-grade story element (e.g. the flagship origin story destined for boilerplate) goes only to `memory/events/narrative.ndjson` via an authorized `operation: propose` request to `registry-events.py` — [narrative-registry](../../../protocol/narrative-registry/SKILL.md) owns the canonical `memory/narrative-registry/` files. Do not write memory without asking.

## Reference Materials

Static analysis

No suspicious patterns detected.