Skip to content
TrustedSkillsbeta
Back to all skills

Log Production Issues

Listed
phrazzld·vlatest·testing

This skill automatically logs production issues, providing immediate alerts and detailed records for faster troubleshooting and improved system stability.

Install on your platform

This skill no longer installs under the name log-production-issues. phrazzld/claude-config is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

phrazzld

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. repository not found or private Source recorded as phrazzld/claude-config.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, log-production-issues, helps AI agents efficiently record and categorize problems encountered in a production environment. It allows for structured logging of errors, including details like timestamps, error messages, affected services, and severity levels. The goal is to streamline debugging and incident response processes by providing clear and organized information about production issues.

When to use it

  • Incident Response: During an outage or service degradation, use this skill to systematically log all related errors for analysis.
  • Debugging Complex Issues: When troubleshooting a difficult bug, leverage the skill to capture relevant error data from different components.
  • Monitoring and Alerting: Integrate with monitoring systems to automatically log events that trigger alerts.
  • Post-Mortem Analysis: After resolving an incident, use logged information to create detailed post-mortem reports.

Key capabilities

  • Structured logging of errors
  • Timestamp recording
  • Error message capture
  • Service identification
  • Severity level assignment

Example prompts

  • "Log a production error: Service 'payment-processor' experienced a timeout, severity critical."
  • "Record this incident: Error code 500 on /api/orders endpoint. User ID: 12345."
  • "Create a log entry for the database connection failure with message 'Connection refused'."

Tips & gotchas

The skill's effectiveness relies on accurate and consistent information provided in prompts. Ensure that error messages and service names are clear and unambiguous to facilitate efficient debugging.