github-issue-creator

1.8k

openclaw

Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.

github-issue-creator

1.6k

microsoft

Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.

zero-script-qa

315

popup-studio-ai

Zero Script QA - Testing methodology without test scripts. Uses structured JSON logging and real-time Docker monitoring for verification. Use proactively when user needs to verify features through log analysis instead of test scripts. Triggers: zero script qa, log-based testing, docker logs, 제로 스크립트 QA, ゼロスクリプトQA, 零脚本QA, QA sin scripts, pruebas basadas en logs, registros de docker, QA sans script, tests basés sur les logs, journaux docker, skriptloses QA, log-basiertes Testen, Docker-Logs, QA senza script, test basati sui log, log docker Do NOT use for: unit testing, static analysis, or projects without Docker setup.

implementing-observability

296

ancoleman

Monitoring, logging, and tracing implementation using OpenTelemetry as the unified standard. Use when building production systems requiring visibility into performance, errors, and behavior. Covers OpenTelemetry (metrics, logs, traces), Prometheus, Grafana, Loki, Jaeger, Tempo, structured logging (structlog, tracing, slog, pino), and alerting.

debugging-dags

258

astronomer

Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline", "full root cause analysis", "why is this failing and how to prevent it". For simple debugging ("why did dag fail", "show logs"), the airflow entrypoint skill handles it directly. This skill provides structured investigation and prevention recommendations.

parse-error-logs

131

maslennikov-ig

Parse build errors, test failures, type-check output, and validation logs into structured data. Use when processing npm/pnpm output, TypeScript errors, Jest failures, or any validation command results for quality gates.

log-analysis

95

aj-geddes

Analyze application and system logs to identify errors, patterns, and root causes. Use log aggregation tools and structured logging for effective debugging.

logging-best-practices

95

aj-geddes

Implement structured logging with JSON formats, log levels (DEBUG, INFO, WARN, ERROR), contextual logging, PII handling, and centralized logging. Use for logging, observability, log levels, structured logs, or debugging.

Log Testing Patterns

71

PramodDutta

Testing logging implementations including log level verification, structured logging validation, log rotation testing, and log aggregation pipeline testing.

regex-log

62

letta-ai

Guidance for extracting structured data from log files using regular expressions. This skill applies when parsing logs to extract dates, IP addresses, timestamps, or other structured patterns, especially when multiple conditions must be combined (e.g., "find the last date on lines containing an IP"). Use this skill for complex regex construction involving lookaheads, anchors, and pattern composition.

toon-formatter

58

raintree-technology

Token-Oriented Object Notation (TOON) format expert for 30-60% token savings on structured data. Auto-applies to arrays with 5+ items, tables, logs, API responses, database results. Supports tabular, inline, and expanded formats with comma/tab/pipe delimiters. Triggers on large JSON, data optimization, token reduction, structured data, arrays, tables, logs, metrics, TOON.

logging

45

AsiaOstrich

Implement structured logging, including proper log levels and handling of sensitive data. When to use: adding logs, debugging, and setting up observability. Keywords: logging, log level, structured logging, observability, logs, recording, structured logs.

logging-strategies

29

omer-metin

World-class application logging - structured logs, correlation IDs, log aggregation, and the battle scars from debugging production without proper logsUse when "log, logging, logger, debug, trace, audit, structured log, correlation id, request id, log level, winston, pino, bunyan, log4j, logging, observability, debugging, monitoring, tracing, structured-logs, correlation, aggregation" mentioned.

logging-observability

27

cosmix

Comprehensive logging and observability patterns for production systems including structured logging, distributed tracing, metrics collection, log aggregation, and alerting. Triggers for this skill - log, logging, logs, trace, tracing, traces, metrics, observability, OpenTelemetry, OTEL, Jaeger, Zipkin, structured logging, log level, debug, info, warn, error, fatal, correlation ID, span, spans, ELK, Elasticsearch, Loki, Datadog, Prometheus, Grafana, distributed tracing, log aggregation, alerting, monitoring, JSON logs, telemetry.

dotnet-testing-test-output-logging

16

kevintsengtw

Complete guide to xUnit test output and logging. Use when implementing test output, diagnostic logging, or ILogger substitutes in xUnit tests. Covers ITestOutputHelper injection, the AbstractLogger pattern, and structured output design. Includes implementations of XUnitLogger, CompositeLogger, and a performance-test diagnostics tool. Keywords: ITestOutputHelper, ILogger testing, test output xunit, test output, test logging, AbstractLogger, XUnitLogger, CompositeLogger, testOutputHelper.WriteLine, test diagnostics, logger mock, test logs, structured output, Received().Log

Observability Instrumentation

16

yaleh

Comprehensive observability methodology implementing three pillars (logs, metrics, traces) with structured logging using Go slog, Prometheus-style metrics, and distributed tracing patterns. Use when adding observability from scratch, logs unstructured or inadequate, no metrics collection, debugging production issues difficult, or need performance monitoring. Provides structured logging patterns (contextual logging, log levels DEBUG/INFO/WARN/ERROR, request ID propagation), metrics instrumentation (counter/gauge/histogram patterns, Prometheus exposition), tracing setup (span creation, context propagation, sampling strategies), and Go slog best practices (JSON formatting, attribute management, handler configuration). Validated in meta-cc with 23-46x speedup vs ad-hoc logging, 90-95% transferability across languages (slog specific to Go but patterns universal).

python-logging-best-practices

14

terrylica

Python logging with loguru and platformdirs. TRIGGERS - loguru, structured logging, JSONL logs, log rotation, XDG directories.

striplog

13

SteadfastAsArt

Create, visualize, and analyze lithological and stratigraphic logs for well data. Use when Claude needs to: (1) Create lithology columns from depth intervals, (2) Parse geological descriptions into structured logs, (3) Visualize stratigraphic columns with patterns and colors, (4) Perform well-to-well correlations, (5) Extract statistics like net-to-gross ratios, (6) Define rock type lexicons and legends, (7) Export lithology data to CSV/LAS/JSON.

verify-training-pipeline

12

kungfuai

Verify a CVlization training pipeline example is properly structured, can build, trains successfully, and logs appropriate metrics. Use when validating example implementations or debugging training issues.

pino

9

TerminalSkills

Log in Node.js with Pino. Use when a user asks to add structured logging, improve logging performance, configure log levels, format logs for production, or replace console.log with proper logging.

structlog-python

9

TerminalSkills

Add structured logging to Python with structlog. Use when a user asks to implement structured logging, add context to Python logs, configure log processing pipelines, or replace standard logging with typed output.

intake-normalizer

9

PHMbench

Normalize a user's raw input/logs/lists of ideas/issues into a structured Intake Markdown and write it to the current day's directory `<MM_DD>/codex/intake/intake_<topic>.md`. Suitable for requests like “organize into an intake / normalize input / write the materials as intake_<topic>.md / structure this pile of information.”

backend-pino

9

petbrains

High-performance structured JSON logging for Node.js. Use when building production APIs that need fast, structured logs for observability platforms (Datadog, ELK, CloudWatch). Provides request logging middleware, child loggers for context, and sensitive data redaction. Choose Pino over console.log for any production TypeScript backend.

pino-logging-setup

8

andrelandgraf

Configure structured logging with Pino. Outputs human-readable colorized logs in development and structured JSON in production for log aggregation services.

thermite-design

7

delorenj

Thermite game design process skill. Use when: running design sessions, generating design artifacts, updating decision logs, working on the thermite project, simulating creative team discussions, or when user mentions 'thermite', 'design session', 'creative team', 'retreat', or references the Bomberman/Tarkov extraction game concept. Provides structured artifact generation, decision tracking, and multi-persona design simulation.

sentry-setup-logging

5

troykelly

Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and other frameworks.

documentation-writer

5

C0ntr0lledCha0s

Expert technical writer for Logseq Template Graph project. Generates comprehensive, accurate, and well-structured documentation for modules, features, guides, and APIs. Activates when asked to "write docs", "document this", "create README", "update documentation", or similar requests. Analyzes code/templates to extract information and writes clear, user-focused documentation following project style.

github-issue-creator

4

ngxtm

Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.

configure-log-aggregation

2

pjt222

Set up centralized log aggregation with Loki and Promtail (or ELK stack), including log parsing, label extraction, retention policies, and integration with metrics for correlation. Use when consolidating logs from multiple services into a searchable system, replacing local log files with centralized queryable storage, correlating logs with metrics and traces, implementing structured logging with label extraction, or troubleshooting production incidents requiring cross-service log analysis.

configure-log-aggregation

2

pjt222

Set up centralized log aggregation with Loki and Promtail (or ELK stack), including log parsing, label extraction, retention policies, and integration with metrics for correlation. Use when consolidating logs from multiple services into a searchable system, replacing local log files with centralized queryable storage, correlating logs with metrics and traces, implementing structured logging with label extraction, or troubleshooting production incidents requiring cross-service log analysis.

detecting-network-anomalies-with-zeek

2

mukul975

Deploys and configures Zeek (formerly Bro) network security monitor to passively analyze network traffic, generate structured logs, detect anomalous behavior, and create custom detection scripts for threat hunting and incident response.

debug-assist

1

flitzrrr

Structured debugging workflow that prevents circular debugging. Follows a systematic approach of Reproduce, Isolate, Hypothesize, Verify, Fix, Test. Logs the debugging path as an artifact to avoid revisiting dead ends.

log-analyzer

1

gitgoodordietrying

Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.

log-analyzer

1

gitgoodordietrying

Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.

log-analyzer

1

gitgoodordietrying

Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.

retrospective

1

flitzrrr

Reconstructs project documentation from git history. Analyzes commit logs, diffs, and merge patterns to generate Architecture Decision Records (ADRs), module chronologies, and contributor maps. Use this for existing projects that have no structured documentation but a rich git history.

ir-investor-tracker

1

escotilha

Investor relationship management CRM for NVNI Group Limited (NASDAQ: NVNI). Maintains a structured database of investors with interaction history, instrument details, capital deployed, materials sent, and engagement scores. Auto-logs interactions when IR emails are dispatched via AgentMail. Generates follow-up reminders for investors not contacted in 30+ days and produces engagement dashboards. All outputs are YELLOW confidence minimum and are subject to SEC Regulation FD compliance for foreign private issuers. Triggers on: investor tracker, investor CRM, investor follow-up, engagement score, investor contacts, LP tracking.

fix-ci

1

flitzrrr

Diagnoses and fixes CI pipeline failures. Reads CI logs, identifies root cause, applies targeted fixes, and verifies locally before pushing. Structured approach prevents the common cycle of blind fix attempts.

structured-logging

sharp-skills

Emits logs as machine-parseable JSON with consistent fields so log aggregation systems can filter, search, and alert on them effectively. Use in any production service where logs need to be searchable by field. Triggers on: logging, log format, JSON logs, log aggregation, Datadog, CloudWatch, structured log, log fields, trace_id in logs, log search.

operational-logging

engineers-hub-ltd-in-house-project

監視・運用の文脈における構造化ログの実践パターン。CloudWatch Logs Insights、 Datadog Logs との連携、ログベースメトリクス、アラート連動を含む。 基盤スキルの structured-logging を運用監視の観点で拡張したスキルとして使用する。

wc-setup

Whyt-AI

Initializes the .whytcard/ knowledge base directory in the current project. Creates a structured, evolving local database for brainstorms, plans, research, execution logs, reviews, and context. Run this once per project — subsequent commands auto-detect and use the existing .whytcard/ structure.

github-issue-creator

haniakrim21

Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored Markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.

conversation-summarizer

ajipalar

Summarize AI text conversations into structured, actionable overviews. Use when a user provides a conversation log, chat export, or dialogue transcript and wants a summary. Supports multiple formats: JSON logs with turn-based structure, ChatGPT/Claude exports, OpenAI API message arrays, JSONL chat logs, and plain-text transcripts with role markers. Triggers on requests like "summarize this conversation," "give me an overview of this chat," "extract key decisions from this dialogue," or "what action items came out of this conversation."

error-recovery

jwilger

Structured error classification and recovery during autonomous operation. Classify runtime errors, apply retry strategies with backoff, maintain error logs, and escalate intelligently. Activate when encountering API failures, build tool crashes, file permission issues, or unexpected runtime errors during autonomous work. Triggers on: "error recovery", "retry", "API failure", "crash recovery", "service unavailable".

agent-receipt

safetnsr

Generate a human-readable receipt from a Claude Code session. Use when the user asks to audit, review, or summarize what an agent did during a session. Reads JSONL session logs and groups all actions (files modified, commands run, URLs fetched, packages installed) into a structured receipt with SHA256 integrity hash. Do NOT use for real-time monitoring — this is post-session analysis only.

log-driven-debugging

sharp-skills

Systematically diagnoses bugs and production issues using logs, traces, and structured observability data instead of guessing. Use when investigating a bug, production incident, unexpected behavior, or performance degradation. Triggers on: debug, investigate, what happened, trace the issue, find the bug, reproduce error, production incident, logs, trace, something is wrong, why is this failing.

log-work

qyinm

Documents development work into changelog-style markdown files organized by date. Analyzes recent changes and creates structured work logs. Use when logging completed work or creating development history.

agent-telemetry

petekp

Make application behavior visible to coding agents by exposing structured logs and telemetry. Use when asked to "add telemetry", "make logs accessible to agents", "add observability", "debug with logs", or when an agent needs to understand runtime behavior but has no way to query logs. Also use when debugging is difficult because there are no structured logs, when agent docs (CLAUDE.md, AGENTS.md) lack instructions for querying application logs, or when setting up logging infrastructure for a new or existing web application.