Persona Forge
Analysis
Persona Forge appears to be a local logging/export tool for persona notes, with no evidence of network access, credential use, or destructive behavior, though it stores entries persistently and its setup/description are somewhat under-declared.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
No install spec — this is an instruction-only skill. ... Code file presence: scripts/script.sh
The registry framing says there is no install mechanism, while the artifact set includes a shell script and the documentation expects a `persona-forge` command. This is an incomplete/under-declared setup contract, but the provided script content aligns with local logging behavior.
Character creator with profiles, backstories, personality traits, relationships, character arcs. ... When called with input, it records a new timestamped entry.
The headline description suggests character creation, while the operational description says commands primarily record and display log entries. This looks like a capability/expectation mismatch rather than harmful deception.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
All data is stored locally in `~/.local/share/persona-forge/` ... `history.log` records all write operations ... `search <term>`| Search across all log entries
The skill explicitly stores user-provided persona entries in persistent local logs and later retrieves or exports them. This is expected for the stated local logging workflow, but persistent user text can contain private character notes or prompts.
