Solid Agent Storage
v0.3.9Give your AI agent persistent identity (WebID) and personal data storage (Pod) using the Solid Protocol
⭐ 2· 710·1 current·1 all-time
byPaul Worrall@masterworrall
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, required binaries (node, curl, jq), env vars (INTERITION_PASSPHRASE, SOLID_SERVER_URL), and provided CLI scripts all match a Solid Pod provisioning and token workflow. The code implements account/pod/client-credential management, token fetch, and local encrypted credential storage — all expected for this functionality.
Instruction Scope
Runtime instructions stay within the stated scope (provision, get-token, read/write via Bearer tokens). Two operational notes: (1) The Skill defaults to a third-party server (https://crawlout.io) if SOLID_SERVER_URL is unset — this means provisioning will create accounts and send credentials to that external host unless you explicitly point to your own server. (2) Provisioning generates and stores an email/password alongside client credentials in an encrypted local store; deprovision will attempt to remove the account but may be partial if credentials are missing. These behaviors are coherent but have privacy/trust implications the user should consider.
Install Mechanism
Install spec only asks to install jq via Homebrew (low risk). The rest of the skill is shipped as JS scripts intended to run under the user's node runtime; no remote, opaque downloads or archive extraction are performed by the install spec.
Credentials
Only two env vars are required and both are justified: INTERITION_PASSPHRASE to encrypt local credentials and SOLID_SERVER_URL to target a Solid server. INTERITION_PASSPHRASE is appropriately declared as primaryEnv. No unrelated secrets or broad credential access are requested.
Persistence & Privilege
The skill does write to a local directory (~/.interition/agents/) to store encrypted credentials, which is appropriate for persistent agent identity. always:false (not force-included) and it does not modify other skills or system-wide agent configuration. Autonomous invocation is allowed (platform default) but not combined with other privilege escalation indicators.
Assessment
This skill appears to do exactly what it says: create and manage Solid WebIDs/Pods and store the resulting credentials encrypted on disk. Before installing, decide whether you trust the default server (https://crawlout.io) — if not, run your own Community Solid Server and set SOLID_SERVER_URL. Use a strong, unique INTERITION_PASSPHRASE and keep it secret: it decrypts your stored client id/secret and any saved agent password. Provisioning will create accounts and store generated passwords locally (encrypted) and deprovision will attempt to remove the server-side account but may not fully remove it in all cases; plan accordingly. If you need maximal control/privacy, self-host the Solid server and review the provided scripts (dist/ and scripts/) yourself before use.Like a lobster shell, security has layers — review code before you run it.
latestvk9768tpne94h4qxq1vqjks9n2x81yd3z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnode, curl, jq
EnvINTERITION_PASSPHRASE, SOLID_SERVER_URL
Primary envINTERITION_PASSPHRASE
Install
Homebrew
Bins: jq
brew install jq