Nix Mode

Handle Clawdbot operations in Nix mode (configuration management, environment detection).

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 1.6k · 0 current installs · 1 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name and description match the requested binaries (nix, bash) and the described behavior (detect Nix mode, handle Nix store paths, avoid auto-installs). That's appropriate for a Nix-mode helper. However, SKILL.md metadata declares it requires CLAWDBOT_NIX_MODE, while the registry metadata listed no required envs. The skill also documents handling CLAWDBOT_CONFIG_PATH and CLAWDBOT_STATE_DIR even though those config paths were not declared in the registry — a mismatch between what the skill claims to need and what the registry advertises.
Instruction Scope
The instructions stay within the Nix-mode domain: detect CLAWDBOT_NIX_MODE, identify Nix-managed config paths, explain behavior and guide users. They do not explicitly instruct broad data collection or exfiltration. That said, phrases like "identify Nix-managed configuration paths" and "recognize Nix-specific error messages" imply the agent may inspect environment variables and filesystem paths; the skill does not explicitly limit which paths or files to read, so there's some scope ambiguity.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk install surface. It does not fetch or extract remote code.
!
Credentials
The SKILL.md metadata explicitly lists CLAWDBOT_NIX_MODE as a required env var, but the registry shows no required envs. The document also references CLAWDBOT_CONFIG_PATH and CLAWDBOT_STATE_DIR without those being declared. While these are Clawdbot-specific (not broad secrets like cloud keys), the mismatch means the agent might attempt to read environment variables or config paths that the registry didn't advertise — an inconsistency worth attention.
Persistence & Privilege
always is false, the skill is user-invocable and can be invoked autonomously (normal). It does not request persistent presence or claim to modify other skills or system-wide agent settings.
What to consider before installing
This appears to be a simple Nix-mode helper, but note the metadata mismatch: SKILL.md expects CLAWDBOT_NIX_MODE and mentions CLAWDBOT_CONFIG_PATH / CLAWDBOT_STATE_DIR while the registry didn’t list those. Before installing, confirm whether the agent will read those environment variables or filesystem paths and whether that's acceptable in your environment. If you have sensitive environment variables or configs, run the skill in a sandbox first or restrict the agent’s autonomy. Ask the skill author (or maintainer) to update the registry metadata so required env vars and any config-path access are declared explicitly.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
latestvk974gwkr95pd6fvvthh4ad8sg5801xpv

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

❄️ Clawdis
Binsnix, bash

SKILL.md

Clawdbot Nix Mode Skill

This skill handles Clawdbot operations specifically when running in Nix mode.

Nix Mode Specific Features

Environment Detection

  • Detect when CLAWDBOT_NIX_MODE=1 is set
  • Identify Nix-managed configuration paths
  • Recognize Nix-specific error messages and behaviors

Configuration Management

  • Understand that auto-install flows are disabled in Nix mode
  • Guide users to proper Nix package management
  • Explain why certain self-modification features are unavailable

Path Handling

  • Recognize Nix store paths
  • Understand the difference between config and state directories
  • Handle CLAWDBOT_CONFIG_PATH and CLAWDBOT_STATE_DIR appropriately

Troubleshooting

  • Identify Nix-specific remediation messages
  • Guide users to proper dependency management via Nix
  • Explain the read-only Nix mode banner behavior

Usage Guidelines

When operating in Nix mode:

  1. Do not attempt to auto-install dependencies
  2. Direct users to Nix package management instead
  3. Respect the immutable nature of Nix installations
  4. Advise on proper configuration practices for Nix environments

Files

1 total
Select a file
Select a file to preview.

Comments

Loading comments…