aim-docker-datastore

Inspect Kafka, Redis, and PostgreSQL state in local AIM Docker datastores.

4|Updated May 17, 2026
One-click install
npx skills add https://github.com/hellopoisonx/aim --skill aim-docker-datastore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aim-docker-datastore
Source: https://github.com/hellopoisonx/aim/tree/main/skills/aim-docker-datastore
Command: npx skills add https://github.com/hellopoisonx/aim --skill aim-docker-datastore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps troubleshoot AIM’s local Docker environment by inspecting Kafka, Redis, and PostgreSQL state directly through project extension tools, avoiding guesswork and repetitive manual command running.

Core Features & Use Cases

  • Docker datastore health checks: Verify whether Kafka/Redis/PostgreSQL containers are running and reachable before deeper investigation.
  • Kafka topic and consumer troubleshooting: List topics and groups, inspect topic details, and consume a small number of messages to confirm events and delivery behavior.
  • Redis key/value investigation: Check connectivity, inspect server info/dbsize, and locate relevant keys using scan-based patterns (plus TTL/type/get when needed).
  • PostgreSQL schema and read-only queries: List databases/tables, describe tables, and run safe read-only SQL to confirm whether expected data has been persisted.
  • Use case: When message delivery, presence/typing/read receipts, or registration/friend flows appear broken, use this Skill to check the corresponding Kafka events and verify persistence in aim_logic/aim_auth and related tables.

Quick Start

Ask the AI: “Check whether my local AIM Docker Kafka/Redis/PostgreSQL datastores are healthy and show what topics and key presence-related keys look like.”

Frequently Asked Questions about aim-docker-datastore

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

FAQPage Schema
How do I troubleshoot Kafka, Redis, and PostgreSQL in a local Docker compose environment?

Troubleshoot local Docker datastores by inspecting Kafka topics, Redis keys, and PostgreSQL state directly through extension tools, avoiding manual command running. This verifies messaging, presence, and persistence failures without requiring Docker commands.

Why are my AIM message delivery and presence features broken in Docker?

Message delivery and presence failures often stem from unhealthy Docker datastores. Inspect Kafka topics and consumer groups to confirm event delivery, check Redis keys for presence states, and verify persistence in PostgreSQL tables.

Can I run safe PostgreSQL queries to inspect data persistence in Docker containers?

Yes, you can run safe read-only PostgreSQL queries to verify data persistence. The Skill lists databases and tables, describes schemas, and executes read-only SQL against aim_logic and aim_auth tables to confirm expected records.

What is the best way to check if my local Docker datastores are running and reachable?

Check Docker datastore health by verifying whether Kafka, Redis, and PostgreSQL containers are running and reachable. The Skill proactively gathers evidence using extension tools to validate container connectivity before deeper investigation.

How do I inspect Kafka topics and sample messages without running Docker commands?

Inspect Kafka topics and sample messages by listing topic and consumer group details, then consuming a small number of events. This confirms event delivery behavior and messaging state directly through the aim_kafka extension tool.

Does this approach require manual Docker commands to investigate Redis keys?

No, investigating Redis keys does not require manual Docker commands. The Skill uses the aim_redis extension tool to check connectivity, inspect server info and dbsize, and locate relevant keys using scan-based patterns with TTL and type checks.