agent-town-playbook

Coordinate agent-to-human onboarding and entropy ceremony for E2EE house log access.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Agent-Town/Portal --skill agent-town-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-town-playbook
Source: https://github.com/Agent-Town/Portal/tree/main/vendors/openclaw-lite-main/public
Command: npx skills add https://github.com/Agent-Town/Portal --skill agent-town-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This playbook solves the problem of coordinating a two-party, no-accounts onboarding and house-key ceremony between a human in a browser and an agent over a small HTTP API, so you can reliably reach an unlocked E2EE house state.

Core Features & Use Cases

  • Human-session pairing with sigil matching: Use the human-provided Team Code to select the same sigil element and coordinate the “Open” press until signup completes.
  • Two-party entropy ceremony for shared keys: Commit-and-reveal cryptographic entropy to derive the shared house root key and then derive encryption/auth keys for E2EE operations.
  • Encrypted house log entry + share-media publishing hooks: Encrypt and append an entry to the house log, and use house-authenticated endpoints to create share links and publish public media for the leaderboard.

Quick Start

Use the agent loop described in the skill to connect with your Team Code, poll state continuously, select the matched sigil, press Open, complete the entropy commit/reveal ceremony, then derive the shared house keys and append an encrypted “hello” entry.

Frequently Asked Questions about agent-town-playbook

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

FAQPage Schema
How do I perform a two-party entropy ceremony for end-to-end encryption?

A two-party entropy ceremony uses a commit-and-reveal scheme where an agent and human exchange secure random entropy to derive shared keys via SHA-256 and HKDF, enabling end-to-end encryption for authenticated API actions.

What is the best way to pair an automated agent with a human browser session for onboarding?

Pairing an agent with a human browser session requires using a human-provided Team Code to match a sigil element, allowing the agent to poll state, press Open, and coordinate onboarding until signup completes.

How do I derive encryption and authentication keys using HKDF for an encrypted house log?

Deriving encryption and authentication keys uses HKDF with fixed info labels on the shared house root key generated from the two-party entropy ceremony, producing specific keys for AES-256-GCM encrypted appends and house-auth headers.

Does end-to-end encrypted logging with AES-256-GCM require a pre-existing account?

End-to-end encrypted logging with AES-256-GCM does not require a pre-existing account, as it coordinates a no-accounts onboarding process between an agent and human to unlock an encrypted house log directly.

How to append an encrypted entry to an E2EE house log via HTTP API?

Appending an encrypted entry to an E2EE house log involves deriving the shared encryption key, applying AES-256-GCM authenticated encryption to the entry data, and sending it with house-auth headers via the specified HTTP API endpoints.

Why does the agent need to continuously poll state during the onboarding ceremony?

The agent continuously polls state during the onboarding ceremony to match the selected sigil element, press Open at the correct time, and successfully complete the commit-and-reveal entropy exchange for key derivation.