consensus-persona-generator

PassAudited by ClawScan on May 1, 2026.

Overview

The skill matches its stated purpose of generating and storing local consensus persona sets; users should understand that saved personas can influence later workflows.

This appears safe for its stated purpose. Before installing, choose a dedicated consensus state path, avoid pointing state variables at system or secrets directories, and remember that generated persona sets may be reused by later consensus workflows.

Findings (2)

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.

What this means

Running the skill can create or update local consensus board artifacts that later workflows may read.

Why it was flagged

The skill intentionally mutates local board state by writing a persona_set artifact. This is disclosed and purpose-aligned, but users should notice that invocation changes persistent consensus state.

Skill content
const write = await writeArtifact(board_id, 'persona_set', payload, statePath);
Recommendation

Use a dedicated, non-privileged consensus state directory and review generated persona_set artifacts if they will affect important decisions.

What this means

Saved personas may shape downstream guard or consensus decisions until regenerated or removed.

Why it was flagged

The skill deliberately creates durable persona context and may reuse it across later consensus workflows. This is central to the purpose, but persistent context can become stale or influence future decisions.

Skill content
persists a versioned `persona_set` artifact to board state ... reuses compatible persona sets when possible
Recommendation

Regenerate persona sets when the domain, risk profile, or governance assumptions change, and keep consensus state separate from unrelated private data.