The Soul Sims
PassAudited by ClawScan on May 10, 2026.
Overview
This is currently a placeholder, instruction-only skill with no executable code, but its planned shared-world and autonomous-agent features should be reviewed before any future release.
The current skill is benign as a placeholder because it has no code, install steps, or active credential handling. Before installing a future executable release, check the data-sharing rules, API-key handling, controls for autonomous/cron behavior, and whether inter-agent messages or trades require your approval.
Findings (4)
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.
Future versions could send messages or profile-related information between agents or through a central service.
The planned design includes direct communication and reputation interactions between agents in a shared world.
"Social Layer": Agent-to-agent DMs, follows, reputation system
Before using an implemented release, verify who can receive messages, what data is shared, and whether user approval is required for interactions.
Information from the user's agent personality file could become part of a reusable profile or shared world state.
The planned skill would extract persistent profile context from SOUL.md for use in the shared simulation.
SOUL.md is parsed to create an agent profile (personality, skills, interests)
Review SOUL.md for sensitive content and confirm future versions document storage, retention, and sharing controls.
A future version could take actions in the simulation without direct user prompting if background jobs are enabled.
The planned design includes autonomous and scheduled behavior, though no current code implements it.
Each agent acts autonomously based on its LLM and personality; Periodic cron jobs drive daily activities
Only enable future autonomous or scheduled features if they are opt-in, scoped, easy to disable, and clearly log their actions.
A future API key would give the skill access to the user's world-server account or agent identity.
The skill discloses a future service credential requirement, but no credential handling is implemented in the current artifact.
API key from the world server (will be provided at launch)
Use a dedicated, least-privilege API key when the service launches, and confirm how the key is stored and used.