kv

Store and retrieve per-user JSON state via a namespaced CLI.

10|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/istota-project/istota --skill kv-istota-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kv
Source: https://github.com/istota-project/istota/tree/main/src/istota/skills/kv
Command: npx skills add https://github.com/istota-project/istota --skill kv-istota-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Key-Value store provides a lightweight, persistent means to store per-user runtime state as JSON blobs, enabling fast access across tasks without custom file I/O.

Core Features & Use Cases

  • Get/Set/Delete/List: operate on per-user, namespace-scoped keys with JSON-encoded values.
  • Namespaces & Sets (via set-ops): support grouping values under namespaces and manipulating JSON arrays with set-add/set-remove.
  • Sandboxing & Deferred Writes: optional sandbox mode defers writes to a directory for safe, auditable execution.
  • Use Case: maintain session data, feature flags, and lightweight metadata across multiple tasks.

Quick Start

Run istota-skill kv get <namespace> <key> to fetch a value.

Frequently Asked Questions about kv

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

FAQPage Schema
How do I persist per-user runtime state across multiple tasks?

Session data can be persisted by storing it as JSON blobs in a lightweight key-value store with namespaced keys. This approach enables fast access across tasks without requiring custom file I/O or external databases.

Can I group and manipulate JSON arrays in a persistent key-value store?

You can group JSON values under namespaces and manipulate JSON arrays using set-add and set-remove operations. This allows targeted updates to array-based feature flags or metadata without rewriting the entire JSON blob.

Does this key-value store support deferred writes for sandboxed execution?

Yes, the key-value store supports an optional sandbox mode that defers writes to a designated directory. This provides safe, auditable execution by staging write operations before they are committed to the persistent store.

What is the best way to store feature flags and lightweight metadata for interactive tasks?

The best way to store feature flags and lightweight metadata is using a persistent key-value store that handles JSON-encoded values. It provides simple get, set, delete, and list operations scoped to per-user namespaces.

How do I retrieve a specific value from a namespaced key-value store?

To retrieve a specific value, run the CLI get command with the target namespace and key as arguments. The store fetches the corresponding JSON blob from the persistent, namespace-scoped key.