role-configurator
v1.0.0OpenClaw Role Configurator - Help you easily configure your OpenClaw AI assistant role, the first skill every new user needs. Trigger scenarios: - Just insta...
⭐ 0· 43·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (role configurator, templates, recommendations, auto-write config) match the included files: template data, recommendation rules, a template manager, recommender, and a config writer. No unrelated capabilities (cloud, network, or secret‑store access) are present.
Instruction Scope
SKILL.md describes conversation-driven configuration and auto-writing a config file. The scripts implement this: reading local JSON templates, formatting recommendations, and writing SOUL.md. The instructions and code read from the packaged data/ files and write a config file to a workspace — this is within scope, but the skill does perform filesystem writes (backs up an existing SOUL.md then overwrites it). Users should be aware it will modify files in the workspace path.
Install Mechanism
No install spec and no external downloads; the skill is instruction-only with small local Python scripts. No high-risk install behavior detected.
Credentials
Registry metadata lists no required env vars, but scripts use OPENCLAW_WORKSPACE (defaulting to /root/.openclaw/workspace). This is a minor inconsistency: the env var is optional, but the skill will write to a default filesystem location if not set. No secrets or unrelated credentials are requested.
Persistence & Privilege
Skill is not always-enabled and does not modify other skills or global agent settings. Its only persistent effect is writing/overwriting the SOUL.md file in the workspace (with a .backup for existing file).
Assessment
This skill appears to do what it claims: load templates, recommend skills, and write a role config file. Before installing, consider: 1) it will write to a workspace path (OPENCLAW_WORKSPACE or default /root/.openclaw/workspace) and will rename any existing SOUL.md to SOUL.md.backup — set OPENCLAW_WORKSPACE to a location you control if you don't want writes under /root; 2) there are no network calls or secret requests, but you should still review the packaged templates (data/role_templates.json) if you want to ensure their contents are acceptable; 3) the registry metadata doesn't list OPENCLAW_WORKSPACE as a required env var even though the scripts read it — that's benign but worth noting. If you need stronger guarantees, run the skill in a sandbox or inspect/execute the scripts in a controlled environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97c3x9kdb1839nxan5pbasn25844tdg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.