analyzing-messaging-layer
Use when analyzing event-driven systems, message queues, async processing, and pub/sub patterns
npx skills add majiayu000/claude-skill-registry --skill analyzing-messaging-layer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyzing Messaging Layer **Output:** `docs/unwind/layers/messaging/` (folder with index.md + section files) **Principles:** See `analysis-principles.md` - completeness, machine-readable, link to source, no commentary, incremental writes. ## Output Structure ``` docs/unwind/layers/messaging/ ├── index.md # Topic overview, event flow diagram ├── events.md # Event definitions & schemas ├── producers.md # Message producers └── consumers.md # Message consumers with retry config ``` For large codebases (10+ topics), split by topic: ``` docs/unwind/layers/messaging/ ├── index.md ├── order-events.md ├── user-events.md └── ... ``` ## Process (Incremental Writes) **Step 1: Setup** ```bash mkdir -p docs/unwind/layers/messaging/ ``` Write initial `index.md`: ```markdown # Messaging Layer ## Sections - [Events](events.md) - _pending_ - [Producers](producers.md) - _pending_ - [Consumers](consumers.md) - _pending_ ## Topics _Analysis in progress..._ ``` **Step 2: Analyze and write events.md** 1. Find all event/message classes 2. Include JSON schemas or Avro/Protobuf definitions 3. Write `events.md` immediately 4. Update `index.md` **Step 3: Analyze and write producers.md** 1. Find all publishe
- Output Structure
- Process (Incremental Writes)
- Output Format
- Mandatory Tagging
- Refresh Mode
mkdir -p docs/unwind/layers/messaging/
What does the analyzing-messaging-layer skill do?
Use when analyzing event-driven systems, message queues, async processing, and pub/sub patterns
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-messaging-layer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.