regenerative_intelligence
v1.0.0Implements energy-efficient, harm-reducing memory and pattern governance that preserves ecological variance and excludes identity tracking or profiling.
⭐ 1· 1.9k·3 current·3 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 files and SKILL.md describe a non-extractive memory/recall architecture; the skill requests no binaries, env vars, or installs — exactly what you'd expect for a design/instruction-only skill. Nothing in the bundle asks for unrelated system access.
Instruction Scope
SKILL.md and companion docs are high-level design and operational constraints (e.g., Trust Vault, stasis gate, ghosting). They do not instruct the agent to read files, environment variables, or external endpoints. However, the guidance is conceptual rather than actionable code: an actual implementation could deviate from these invariants, so verify runtime code before trusting enforcement of the described protections.
Install Mechanism
There is no install spec and no code files to execute. This minimizes installation risk — nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The described Trust Vault concept references execution-only identity handling but does not request credentials in this bundle; that is appropriate for a specification-only package.
Persistence & Privilege
always is false and the skill is user-invocable (normal defaults). The docs describe long-term memory and a 'Trust Vault' concept; because this package contains only spec documents, there is no actual persistent agent-side behavior here. If a later implementation grants persistent access or autonomy, confirm it adheres to the invariants described.
Assessment
This package is a specification and design document set (no code, no installs, no secrets) and appears coherent and non-extractive. It poses low immediate technical risk as-is. Before you install or enable any implementation derived from these docs, verify the actual runtime code: ensure there are no hidden downloads, that the Trust Vault is truly ephemeral and execution-only, and that embedding/storage code enforces non-identifiability and decay rules described here. If you plan to let an agent invoke this skill autonomously, confirm how the platform enforces the invariants and that implementations cannot write shadow logs, exfiltrate data, or access unrelated credentials. If you need higher assurance, ask the provider for the implementation code or for a security review demonstrating the invariants are enforced in practice.Like a lobster shell, security has layers — review code before you run it.
co-intelligencevk97945j0f1gsm7868kc61fe83h80bp4renergy-awarevk97945j0f1gsm7868kc61fe83h80bp4rharm-reductionvk97945j0f1gsm7868kc61fe83h80bp4rlatestvk97945j0f1gsm7868kc61fe83h80bp4rnon-extractive resonancevk97945j0f1gsm7868kc61fe83h80bp4rregenerative gentle-memoryvk97945j0f1gsm7868kc61fe83h80bp4rtrust-by-designvk97945j0f1gsm7868kc61fe83h80bp4r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.