ensue

Manage Delibera ENSUE memory keys, permissions, and cross-org access.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/leomanza/delibera.xyz --skill ensue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ensue
Source: https://github.com/leomanza/delibera.xyz/tree/main/.claude/skills/ensue
Command: npx skills add https://github.com/leomanza/delibera.xyz --skill ensue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensue Memory Network integration becomes confusing when coordinator and worker agents cannot reliably read/write shared state, coordinate task progress, or publish final results; this Skill helps you implement, debug, and correctly operate the Delibera-specific memory key namespace, permissions, and API flows.

Core Features & Use Cases

  • Delibera-specific ENSUE integration: Centralizes how to create, read, update, delete, list, and search memory keys used by both coordinator and workers.
  • Correct coordination state management: Covers the expected key layout for coordination/ (status, tally, task tracking, coordinator config) and worker/ (identity, reasoning, knowledge, state).
  • Agent provisioning and permission setup: Guides coordinator org self-registration in the buy flow, worker group creation, read grants, invite link handling, and making proposal results publicly readable.
  • Cross-org access and real-time updates: Supports worker-to-coordinator reads (including @org-name/ key prefix conventions) and uses subscriptions to react to task assignment changes.

Quick Start

Use the ensue skill to implement or debug Delibera memory coordination by targeting the correct ENSUE API endpoints, environment variables, and the required key namespace conventions for coordinator, worker, and public proposal results.

Frequently Asked Questions about ensue

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

FAQPage Schema
How do I resolve coordinator-worker agent coordination failures in shared memory networks?

Agent coordination failures in shared memory networks are resolved by enforcing correct Delibera key namespace conventions for `coordination/` and `worker/` directories to manage status, tallies, and task tracking state.

How do I set up cross-org access for agents reading shared memory keys?

Cross-org access for shared memory keys is set up by configuring worker-to-coordinator reads using the `@org-name/` key prefix convention, granting read permissions, and publishing results via the make_public namespace.

What is the correct key hierarchy for managing agent task progress in a memory network?

The correct key hierarchy for managing agent task progress separates state into `coordination/` for status and tally tracking, and `worker/` for identity, reasoning, knowledge, and state updates.

How do I provision a coordinator agent and assign worker permissions in Delibera?

Coordinator agent provisioning involves self-registering the coordinator org in the buy flow, creating worker groups, handling invite links, and assigning read grants to coordinate shared state operations.

Does the ENSUE memory API require JSON-RPC tool invocations for agent state updates?

Yes, the ENSUE memory API requires JSON-RPC tool invocations to properly execute reads, writes, and searches across coordinator and worker agent state.

Why are my worker agents not reacting to task assignment changes in the memory network?

Worker agents fail to react to task assignment changes when subscriptions to the ENSUE memory network are not configured to monitor real-time updates in the `coordination/` key namespace.