DriveMind
v0.3.0Apply DriveMind, the calm reliability layer for AI agents. Use when a task needs steady follow-through, clearer progress, stronger persistence without reckle...
⭐ 0· 221·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
The name/description (a steadiness/safety layer for agents) aligns with the SKILL.md: all files are prose, templates, and guidelines. No unrelated binaries, env vars, or install steps are requested.
Instruction Scope
All runtime instructions are policy and templates for agent output, referencing only included reference docs and templates. One minor ambiguity: the SKILL.md says 'Persist stable lessons' but does not specify how or where to persist (agent memory, external store, user files). That is an operational detail the integrator must control; the skill itself does not include code that performs persistence or external I/O.
Install Mechanism
No install spec and no code files beyond documentation/templates — lowest-risk form (instruction-only). Nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The instructions do not ask for secrets or other unrelated credentials.
Persistence & Privilege
always:false and normal autonomous invocation are used (expected). The only potential concern is the skill's suggestion to 'persist stable lessons' — since the skill provides no mechanism, check the host agent's memory/persistence settings to confirm where these lessons would be stored and who can read them.
Assessment
DriveMind is an instruction-only policy/template pack — it does not install code or request secrets, so it's internally coherent. Before enabling it broadly, confirm the host agent's memory or persistence mechanism: the skill recommends persisting 'stable lessons' but doesn't specify where. If you care about privacy or separation of duties, verify (1) where lessons get stored (local ephemeral memory vs persistent user memory vs external service), (2) who/what can read that storage, and (3) whether you want DriveMind active for agents that can act with high privileges (deployments, external messaging). If you want tighter control, allow DriveMind only in contexts where its persistence target and autonomy are acceptable.Like a lobster shell, security has layers — review code before you run it.
latestvk97ags15kehdfchzdj33arkyqx82rr3p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.