logging-rule

Enforce request-centric structured logging for backend code and API routes.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/nagy-ag/MediaEchoRomania --skill logging-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-rule
Source: https://github.com/nagy-ag/MediaEchoRomania/tree/main/.agents/skills/logging-rule
Command: npx skills add https://github.com/nagy-ag/MediaEchoRomania --skill logging-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces consistent, request-centric structured logging across backend code, API routes, Convex functions, and Python workers, preventing scattered console logs and enabling powerful, context-rich event querying.

Core Features & Use Cases

  • Wide Event Logging: Ensures each request or job emits a single, comprehensive event with all relevant debugging context.
  • Queryable Data: Transforms logs into structured data, making debugging and analysis efficient.
  • Use Case: Debug a complex user authentication flow by querying a single event that includes request details, client information, and infrastructure context, rather than piecing together multiple scattered log lines.

Quick Start

Use the logging-rule skill to ensure all new backend API routes implement request-centric wide event logging.

Frequently Asked Questions about logging-rule

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

FAQPage Schema
What is request-centric structured logging and how does it improve backend debugging?

Request-centric structured logging standardizes backend log output into wide events containing identity, event structure, and deployment context. This transforms scattered console logs into queryable data for efficient analysis across distributed systems.

How do I implement structured logging for API routes and Python workers?

You implement structured logging by enforcing a single wide event per request or job, requiring inclusion of identity, client information, infrastructure context, and high cardinality fields to standardize log output across backend code and Python workers.

Does this structured logging approach work with Convex functions?

Yes, this structured logging approach works with Convex functions by enforcing request-centric wide event logging. It standardizes log output to include deployment context and high cardinality fields for effective analysis across distributed systems.

Why are wide events better than scattered console logs for debugging distributed systems?

Wide events are better for debugging distributed systems because each request emits a single comprehensive event with all relevant debugging context. This prevents scattered console logs and enables powerful, context-rich event querying for efficient analysis.

Can I query a complex user authentication flow using structured logging?

Yes, you can query a complex user authentication flow by retrieving a single structured event that includes request details, client information, and infrastructure context, rather than piecing together multiple scattered log lines for debugging.