T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:41- Finding
Persistent State Writes Exceed the Manifest's Declared Capability Boundary
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned for building pitch narratives, but it asks for persistent memory writes that are not declared in its manifest capabilities.
Review this before installing if your host relies on the manifest for permissions. The narrative workflow itself is reasonable, but the package should either declare narrowly scoped write capabilities or return proposed records inline unless you explicitly approve each destination and payload.
SKILL.md:41Persistent State Writes Exceed the Manifest's Declared Capability Boundary
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.
## Save Results
After delivering the pitch narrative, ask: "Save these results for future sessions?" On confirmation, write `memory/narrative/pitch-narrative-builder/YYYY-MM-DD-<topic>.md` per the [Skill Contract](../../../references/skill-contract.md) §Save Results Template. Every `[needs source]` proof goes only to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`; any canon-grade wording surfaced while drafting goes only to `memory/events/narrative.ndjson` via an authorized `operation: propose` request to `registry-events.py` — [narrative-registry](../../../protocol/narrative-registry/SKILL.md) is the sole writer of `memory/narrative-registry/` canonical files. Do not write memory without asking.
## Reference Materials
No suspicious patterns detected.