Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Emitting Context Rich Events

ASecurity

guides logging through context-rich events at the granularity of significant operations. use when adding, changing, or reviewing logging, structured events, or instrumentation.

64 stars
0 votes
0 copies
2 views
Added 9/20/2026
ai-agentsgodebugginggit

Security Analysis

A100/100

Scanned 9/20/2026

$npx -y skills add bdsqqq/dots --skill emitting-context-rich-events --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Emitting Context Rich Events?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Emitting Context Rich Events
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bdsqqq-emitting-context-rich-events/badge)](https://www.skillsdirectory.com/skills/bdsqqq-emitting-context-rich-events)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: emitting-context-rich-events
description: "guides logging through context-rich events at the granularity of significant operations. use when adding, changing, or reviewing logging, structured events, or instrumentation."
---

# CONTEXT-RICH EVENTS \*\*

emit context-rich events at the granularity of significant operations.

source: [igorbedesqui.com pattern language](https://github.com/bdsqqq/igorbedesqui.com/blob/main/packages/pattern-language/context-rich-events.md).

**consider first**: [WORKFLOW = DATA](https://github.com/bdsqqq/igorbedesqui.com/blob/main/packages/pattern-language/workflow-equals-data.md)

**forces**: autonomous agents act on your behalf — you need to
reconstruct what happened after the fact. scattered log lines optimized
for writing (`log("payment failed")`) can't answer the questions you
actually ask during debugging: "which workflow, for which issue, at
what step, with what inputs?"

low-context logs force you to grep across files, correlate by timestamp,
and hope the right fields were included. they answer "something
happened" but not "what happened to THIS request." the more autonomous
the system, the wider the gap between what was logged and what you need
to know.

**therefore**: emit context-rich events at the granularity of significant
operations. each event carries the full context needed to understand that
operation in isolation — identifiers, business state, timing, outcome.
one event per operation, not many log lines scattered across the call
stack. transport (console, structured platform, both) is an orthogonal
decision.

**intended consequences**:

- ✓ debugging becomes querying — filter by workflow, step, outcome
- ✓ events are self-contained — no cross-referencing needed
- ✓ high-cardinality fields (workflow ID, issue ID) enable precise queries
- △ requires discipline — every call site must attach context, not just
  a message string
- △ event size grows with context; cost scales with dimensionality

**consider next**: [HUMAN-FRIENDLY IDENTIFIERS](https://github.com/bdsqqq/igorbedesqui.com/blob/main/packages/pattern-language/human-friendly-identifiers.md)

Attribution

bdsqqqbdsqqq
View sourceSee grades on GitHubMore from bdsqqq →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →