ClawHub

Config

v2.0.1

Manage app configuration files with init, list, and add operations. Use when initializing configs, listing settings, switching environments.

⭐ 0· 393·3 current·3 all-time
by@bytesagain1

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bytesagain1/config.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Config" (bytesagain1/config) from ClawHub.
Skill page: https://clawhub.ai/bytesagain1/config
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install bytesagain1/config

ClawHub CLI

Package manager switcher

npx clawhub@latest install config
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
Overall the script implements a local config/log utility matching the name/description. However a couple of declared commands do not perform the action a user would reasonably expect: 'remove' only echoes a removal message and does not delete entries from data.log, and 'run' only prints its argument rather than executing anything. The SKILL.md and script otherwise align on storage location and basic operations.
ℹ
Instruction Scope
SKILL.md instructs the agent to run local commands (init, add, list, search, export). These are limited to local filesystem operations. Be aware the tool writes every executed command to history.log and appends user-provided text to data.log — so any sensitive text passed to 'config add' (or piped into the command examples like diff outputs) will be persisted.
✓
Install Mechanism
Instruction-only skill with a single bash script; no install spec, no remote downloads, and no package manager use — lowest install risk.
ℹ
Credentials
The registry metadata lists no required env vars, but the script honors CONFIG_DIR (override), XDG_DATA_HOME, and HOME for storage location. This is reasonable, but CONFIG_DIR is not declared as a required/provided env in metadata. Also: because data and history are stored under the user's data directory, those files may contain sensitive information if used to store secrets.
✓
Persistence & Privilege
always:false and the skill is user-invocable only. The script only creates files under the user's data directory (~/.local/share/config by default) and does not modify global/system settings or other skills' configs.
Assessment
This appears to be a simple local-only config/log tool and is coherent with its description. Before using it: (1) don't store secrets or credentials with 'config add' because entries and history are persisted in plaintext under your user data directory; (2) note that 'remove' does not actually delete entries — review/modify the script if you need true removal; (3) if you expect 'run' to execute commands, update the implementation (it currently only echoes the input). If you are comfortable with plaintext local logs and/or audit those files in backups, this skill is reasonable to install.

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

latestvk97a50gntw9xka0xsn009t1fn1835yzb
393downloads
0stars
10versions
Updated 1mo ago
v2.0.1
MIT-0
@bytesagain1
latest
Download

Config

Multi-purpose configuration and data utility tool. Initialize settings, add entries, search records, and export data — all from the command line.

Commands

CommandDescription
config run <input>Execute the main function with the given input
config configShow the configuration file path ($DATA_DIR/config.json)
config statusDisplay current system status (shows "ready" when operational)
config initInitialize the data directory and prepare for first use
config listList all entries stored in the data log
config add <item>Add a new timestamped entry to the data log
config remove <item>Remove a specified entry
config search <term>Search entries by keyword (case-insensitive)
config exportExport all stored data to stdout
config infoShow version number and data directory path
config helpShow help with all available commands
config versionShow current version

Data Storage

  • Default data directory: ~/.local/share/config/
  • Data log: $DATA_DIR/data.log — stores all added entries with timestamps
  • History log: $DATA_DIR/history.log — timestamped record of every command executed
  • Override the storage location by setting the CONFIG_DIR environment variable

Requirements

  • Bash 4+ (uses set -euo pipefail)
  • No external dependencies, API keys, or network access required
  • Fully offline and local — data never leaves your machine

When to Use

  1. Bootstrapping a new project — Run init to create the data directory and get a clean starting point for configuration tracking
  2. Logging configuration changes — Use add to record timestamped configuration decisions, environment changes, or deployment notes
  3. Searching through config history — Find specific entries with search to trace when a setting was last changed
  4. Exporting settings for backup — Dump all stored entries with export and redirect to a file for version control or sharing
  5. Quick status checks in scripts — Use status and info in automation pipelines to verify the tool is ready before proceeding

Examples

# Initialize the config data directory
config init

# Record a configuration change
config add "Set DATABASE_URL to production endpoint"

# Record another entry
config add "Enabled rate limiting: 100 req/min"

# List all recorded entries
config list

# Search for entries related to a keyword
config search "database"

# Export all data to a backup file
config export > config-backup.txt

# Check system status
config status

# View version and storage location
config info

How It Works

The tool maintains a simple date-stamped text log (data.log). Each add command appends a new line with the current date and your input. Every command execution is also logged to history.log for audit trails. The search command performs a case-insensitive grep, and export outputs the full data log to stdout.

Tips

  • Use config config to find where the config JSON file is stored — handy for automated backup
  • Pipe export into other tools: config export | wc -l to count entries
  • Combine with cron or CI/CD: log config drifts automatically with config add "$(diff old new)"
  • Run config help at any time to see the complete command reference

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...