Northbase
v1.0.3Access and manage your persistent notes and workspace files via the Northbase CLI when you explicitly request reading, writing, listing, or syncing them.
⭐ 0· 185·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 SKILL.md clearly limits the skill to reading, writing, listing, and syncing files via the northbase CLI, which matches the name/description. However, the registry metadata claims no required binaries while the runtime instructions explicitly require the `northbase` CLI to be installed — this metadata mismatch should be corrected.
Instruction Scope
Instructions are narrowly scoped: they direct the agent to use specific northbase commands (pull, list, get, put, login) and explicitly forbid reading local file paths or bypassing the CLI. The skill also instructs not to auto-run and to require explicit user intent for file operations.
Install Mechanism
No install spec or code is included (instruction-only), so nothing new will be written to disk or downloaded by the skill itself. This is a low-risk install footprint.
Credentials
The skill declares no environment variables or credentials. Authentication is delegated to the northbase CLI (it may prompt the user to login), which is proportionate for a file-accessing CLI.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system modifications or access to other skills' configs. Note: model invocation is allowed (normal platform default), but the SKILL.md explicitly instructs to only use the CLI on explicit user requests.
Assessment
This skill appears to do what it says: use the northbase CLI to list, read, write, and sync your notes when you explicitly ask. Before enabling: (1) confirm the northbase CLI is installed and working on the agent host (the registry metadata should be updated to list it as a required binary); (2) verify how `northbase login` stores credentials on the host (tokens or files) and that you’re comfortable with the agent invoking the CLI under your explicit request; (3) test with a non-sensitive file to confirm behavior; and (4) if you want stronger guarantees that the agent won't access files without explicit permission, consider disabling autonomous invocation or restricting the agent's permissions in your environment. If the metadata is not updated to document the CLI dependency, treat that as a minor red flag and ask the publisher for clarification.Like a lobster shell, security has layers — review code before you run it.
latestvk973r6df96yn92ezt0yf882kcx82r17jnotes files memory cli storagevk97cdza02n091sk0xe0pxb6gfd82rrwy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.