Vinculum - Shared Consciousness

Key things to consider before installing: - Metadata mismatch: the registry lists no required binaries/install spec, but SKILL.md and package.json require Node.js (>=18) and npm and instruct you to run npm install. Ensure Node/npm are present and that you run installation in a controlled environment. - Network exposure: the skill launches a relay server (default port 8765) and will accept peer URLs you configure. If you add a remote peer that is reachable on the internet or an untrusted host, your shared-memory data (activity, learned knowledge, decisions) can be replicated to that host. Only join collectives and add peers you trust. - Pairing codes: invite/pairing codes grant read/write access to the collective. Treat them like secrets — anyone with a code can modify the shared state. - Data persistence: the skill stores data and logs under your home directory (~/.local/... and ~/.config/...). If you want to limit persistence, inspect the data_dir and storage locations in defaults.yaml and consider running the skill in a sandbox, container, or VM. - Review missing/truncated files: some implementation files were truncated in the provided package; if you plan to use this, review relay-simple.js and the gun-adapter implementation fully to confirm no unexpected network calls or remote endpoints are hardcoded. - Safe deployment recommendations: run initial testing on an isolated machine or inside a container, ensure your firewall blocks unwanted external access to the relay port, and only generate/share pairing codes with machines/users you control. If you want, I can: - Walk through the relay script and gun-adapter for code-level review of networking and persistence behavior (the repo listing included truncated files that I can inspect if you provide them), or - Produce a checklist to sandbox this skill safely before enabling it in a production agent.