nx-kv

Manages KV-backed todo lists for task claiming, intent confirmation, and completion reporting.

3|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ZHLX2005/sl --skill nx-kv-zhlx2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-kv
Source: https://github.com/ZHLX2005/sl/tree/main/skills/nx-kv
Command: npx skills add https://github.com/ZHLX2005/sl --skill nx-kv-zhlx2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams submit tasks into a shared KV-backed todo list, but agents on the consuming side often grab vague tasks, execute blindly, and never report back. This Skill standardizes the agent-side workflow: pull open tasks by topic, read the topic's context prompt, confirm intent with the user before acting, and backfill results on completion. ## Core Features & Use Cases - Task claiming workflow: An 8-step SOP covering login/workspace verification, fetching open tasks by topic, reading topic prompts, intent confirmation, clustering, and completion backfill via nx-kv todo done. - Full CLI command reference: Covers todo CRUD, freeze/unfreeze, topic and prompt management, workspace (group) switching, exit codes, error codes, and data structures. - Duplicate-id safety: Explains why ids are reused after tasks complete and how to disambiguate with --pick or --topic when operating on the done bucket. - Use Case: A user says "pick up my go-topic tasks." The agent verifies the workspace, runs nx-kv todo list --status open --topic go --json, reads the topic prompt, presents clarified tasks for confirmation, then completes and backfills each one. ## Quick Start Ask the agent to claim your pending tasks for a specific topic, for example: "领取 go 主题的任务,先确认意图再执行。"

Frequently Asked Questions about nx-kv

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

FAQPage Schema
How do I claim tasks from a KV todo list as an agent?

Run nx-kv todo list --status open --topic <topic> --json to fetch only pending tasks for that topic, then read the topic prompt with nx-kv prompt get. Confirm intent with the user before executing, and backfill each finished task with nx-kv todo done <id> --result.

How do I manage todo tasks with the nx-kv CLI?

nx-kv provides full CRUD: todo list, get, add, update, remove, plus done, freeze, and unfreeze. All list operations require login via nx-kv auth login, and adding a task requires the --topic flag.

What is the difference between nx-kv and kvcli?

Both connect to the same backend and data. nx-kv covers all four keys including freeze and topics, offers a web panel via nx-kv serve, and protects against duplicate-id operations, while kvcli only handles open and done buckets.

Why does nx-kv report multiple matches for one task id?

Ids are assigned only across open and freeze buckets, so completed tasks accumulate duplicate ids in the done bucket. When a command hits multiple entries, use --pick <n> or --topic <t> to disambiguate.

Why does nx-kv return no tasks when tasks exist?

Data is isolated by groupId, so you are likely in the wrong workspace. Check nx-kv group current and switch with nx-kv group use, or verify login state with nx-kv auth status.