ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified utilities Safety 4/5

tribe-protocol

MANDATORY trust lookup for every non-owner interaction. Query tribe.db to check entity trust tier, channel access, and data boundaries before responding. Run 'tribe init' on first install. Use 'tribe lookup <discord_id>' before every non-owner response.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/cheenu1092-oss/tribe-protocol
Or

What This Skill Does

The tribe-protocol skill provides a mandatory, systematic trust-based filtering mechanism for OpenClaw AI agents. It acts as the gatekeeper for all non-owner interactions, ensuring that the AI dynamically adjusts its data transparency, conversational tone, and access rights based on an entity's pre-defined trust tier. By maintaining a local SQLite-backed registry, the agent can verify if an interlocutor is a trusted 'Tribe' member, a limited 'Acquaintance,' or a 'Blocked' entity before processing or disclosing any information. This architectural layer adds a crucial security perimeter to any autonomous agent operating in public or collaborative digital spaces.

Installation

Installation is managed via the ClawHub CLI. Ensure your environment has the sqlite3 dependency installed. Run the following command in your terminal: clawhub install openclaw/skills/skills/cheenu1092-oss/tribe-protocol

Once installed, you must perform the initialization sequence once per workspace to build the database schema and identify the owner: ./scripts/tribe.sh init --bot-name <name> --bot-discord-id <id> --human-name <admin> --human-discord-id <admin_id>

Use Cases

This skill is essential for any OpenClaw bot deployed in multi-user environments such as Discord or professional slack channels. It is primarily used to prevent unauthorized access to sensitive bot context, protect system resources from abuse by malicious actors, and allow for granular permission management where team members can collaborate while limiting data exposure to casual visitors. It is particularly effective for community management bots that need to distinguish between long-term contributors and temporary users.

Example Prompts

  1. "Check the current trust status of the user with Discord ID 987654321 to see if I can share the project roadmap."
  2. "Update the trust tier for Yajat to 3 and add the reason: 'Contributor to core repository'."
  3. "List all current entities in the roster to verify who has access to the private channel."

Tips & Limitations

Always prioritize the 'tribe-protocol' lookup as the very first operation in your bot's middleware stack. If a lookup is bypassed, the bot risks exposing private data to unauthorized tiers. The system relies on the integrity of the TRIBE.md file; ensure this file is not publicly exposed in your repository. Note that the system is currently limited to SQLite; for distributed multi-bot systems, you may need to override the TRIBE_DB environment variable to a shared networked drive or database instance. Always keep a log of changes to trust tiers for auditing purposes.

Metadata

Stars3875
Views1
Updated2026-04-07
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-cheenu1092-oss-tribe-protocol": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#security#trust-management#access-control#openclaw#permissions
Safety Score: 4/5

Flags: file-read, file-write