Chitin Chronicle

What This Skill Does

Chitin Chronicle is a sophisticated, git-backed content coordination framework specifically engineered for multi-agent environments. When running multiple AI agents like Vesper and Ember, the risk of publishing duplicate content or stepping on each other's toes during long-form narrative projects is high. This skill serves as a centralized, immutable ledger that tracks publication history, content timelines, and active workspace claims. By integrating with local git repositories, it ensures that every editorial decision—from drafting to final publication—is synced and serialized, preventing collisions and providing a clear audit trail of your AI's production workflow.

Installation

To integrate Chitin Chronicle into your existing OpenClaw setup, execute the following installation command in your terminal: clawhub install openclaw/skills/skills/adroidian/chitin-chronicle

Once installed, finalize the configuration by adding the editorial status check to your AGENTS.md file. This ensures that every time your agent initializes, it performs a boot-time awareness check of the current editorial state. Append the following path to your startup section: /home/aaron/.openclaw/workspace/skills/chitin-chronicle/editorial/boot-check.sh

Use Cases

• Coordinated Narrative Publishing: Syncing complex multi-part series (like "Day 1" through "Day 30") across agents so that one agent handles the creative drafting while another manages the deployment pipeline.
• Preventing Duplicate Output: Automatically blocking a second agent from "publishing" to Substack if the first agent has already initiated the upload or recorded the link.
• Editorial Audit Trails: maintaining a permanent history of what was posted, where, and when, allowing human operators to quickly trace content history via the local ledger.

Example Prompts

1. "Check the current editorial status to see if 'day-15' has been claimed or published yet."
2. "Claim 'day-15' for the 'substack' channel so no other agents try to work on it."
3. "Release my previous claim on 'day-14' as I am no longer pursuing that publication."

Tips & Limitations

• TTL Expiration: Always remember that claims expire after 2 hours. If your process takes longer, ensure your agent refreshes the claim.
• Git Dependency: This skill relies on local git commits for persistence; ensure your workspace is configured to allow auto-commits to the ledger directory.
• Collaboration: This tool is designed for autonomous agent coordination. Avoid manually editing the .claim files, as this can lead to out-of-sync states between agents.