T05 · Unauthorized Access and Privilege Escalation
- Location
distribution-manifest.json:2- Finding
Skill Operations Exceed the Capabilities Declared in the Distribution Manifest
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill's main workflow is understandable, but its package metadata understates the network/script and memory-write actions it tells an agent to perform.
Install only in a host that enforces per-operation permissions. Allow the named connectors and memory paths only if you expect this skill to perform resonance monitoring, and require confirmation before report saves, event proposals, open-loop updates, or cache changes.
distribution-manifest.json:2Skill Operations Exceed the Capabilities Declared in the Distribution Manifest
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 report, ask: "Save these results for future sessions?" On confirmation, write `memory/narrative/narrative-resonance-monitor/YYYY-MM-DD-<topic>.md` per the [skill-contract.md](../../../references/skill-contract.md) §Save Results Template. Unbacked resonance/effectiveness statements go only to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`. This skill writes no canonical `memory/narrative-registry/` files — only [narrative-registry](../../../protocol/narrative-registry/SKILL.md) does; if a resonance read surfaces a canon-grade lexicon or naming fact, submit it to `memory/events/narrative.ndjson` via an authorized `operation: propose` request to `registry-events.py` only. Do not write memory without asking.
## Reference Materials
No suspicious patterns detected.