charm-skate

Store persistent key-value state for shell scripts using KEY[@DB] namespaces.

Updated Apr 8, 2026

Search Tags:#shell #namespace #key-value #state #persist #stdin #skate

Ready to run

npx skills add https://github.com/ClankerGuru/opsx --skill charm-skate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: charm-skate
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/charm-skate
Command: npx skills add https://github.com/ClankerGuru/opsx --skill charm-skate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a shell script needs a tiny local key-value store — storing release tags, last-used branches, cached answers, or shared config across script runs without a real database. Covers every skate subcommand, the KEY[@DB] namespace syntax, reading values from stdin, binary values, and list output shapes.

Core Features & Use Cases

Persist a small key-value data store across script executions.
Support for the KEY[@DB] namespace, reading values from stdin, binary values, and list output formats.
Suitable for caching configuration, results, and metadata in automation workflows.

Quick Start

Initialize the skate state store and perform set/get operations to persist values across script runs.

Frequently Asked Questions about charm-skate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I persist a small key-value store across shell script executions?▼

You can persist a small key-value store across shell script executions by using a lightweight local state tool. It stores cached values and shared config without requiring a real database, enabling cross-run data retrieval.

What is the KEY[@DB] namespace syntax for shell state management?▼

The KEY[@DB] namespace syntax allows you to target specific data stores when managing shell state. By appending @DB to a key, you can isolate and organize cached values or configuration data across different automation workflows.

Can I read values from stdin to store binary data in a shell script?▼

Yes, you can read values directly from stdin to store binary-safe data in your shell script. This enables you to capture and persist complex input streams or binary values without losing data integrity during automation.

What is the best way to cache configuration and metadata in automation workflows?▼

The best way to cache configuration and metadata in automation workflows is using a tiny local state store. It provides fast cross-run retrieval for release tags, last-used branches, and shared config without database overhead.

Does this approach work for generating list output formats from cached state?▼

Yes, this approach works for generating list output formats from cached state. It supports formatting stored key-value data into lists, allowing scripts to easily iterate over multiple values during workflow execution.