skills.rest
useatrium
useatriumOFFICIAL
Explore all skills by this author →
GitHub

auth-failure-log-triage

Investigate authentication and authorization failures in VictoriaLogs runtime logs.

4|2|Updated Jun 10, 2026
Search Tags:#authorization#authentication#oauth#api proxy#secret resolution#credential failures#victorialogs
One-click install
npx skills add https://github.com/useatrium/atrium --skill auth-failure-log-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auth-failure-log-triage
Source: https://github.com/useatrium/atrium/tree/main/centaur/.agents/skills/auth-failure-log-triage
Command: npx skills add https://github.com/useatrium/atrium --skill auth-failure-log-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose authentication, authorization, credential, API proxy, OAuth, token, and secret-resolution failures using live runtime evidence instead of unsupported assumptions or premature configuration changes.

Core Features & Use Cases

  • Evidence-first investigation: Queries VictoriaLogs before recommending secret, permission, or integration changes.
  • Targeted troubleshooting: Investigates failures by integration, host, thread key, execution ID, pod, service, or time window.
  • Failure classification: Distinguishes upstream 401, 403, and 503 responses from local proxy or secret-resolution failures while preserving sensitive secret values.
  • Use Case: When an API integration returns unauthorized or unavailable errors, use this Skill to identify the affected service, inspect relevant traces, summarize supported evidence, and request missing diagnostic details if logs are unavailable.

Quick Start

Use the auth-failure-log-triage skill to investigate the reported integration failure in VictoriaLogs and summarize the evidence without exposing secret values.

Frequently Asked Questions about auth-failure-log-triage

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

FAQPage Schema
How do I investigate API 401 and 403 authentication failures using runtime logs?▼

Trace OAuth and token authorization failures by querying VictoriaLogs for live runtime evidence. This isolates upstream service denials from local proxy errors by inspecting host, pod, and execution ID logs without exposing secret values.

Why does my API integration return unauthorized or forbidden errors?▼

API integration unauthorized errors stem from upstream 401, 403, or 503 responses, or local secret-resolution failures. Query VictoriaLogs to classify whether the denial originates from the upstream service or local proxy configuration.

How do I troubleshoot secret-resolution failures without exposing sensitive credential values?▼

Troubleshoot secret-resolution failures by querying VictoriaLogs to summarize runtime evidence. This classifies local credential problems and requests missing diagnostic context while ensuring sensitive secret values are never exposed.

Can I use VictoriaLogs to diagnose OAuth and credential failures across specific pods or hosts?▼

Yes, VictoriaLogs supports targeted troubleshooting of OAuth and credential failures by querying specific integration, host, pod, thread key, or execution ID parameters to isolate the source of authorization denials.

What is the best way to triage 503 service unavailable errors in an API proxy?▼

Triage 503 service unavailable API proxy errors by querying VictoriaLogs for live runtime evidence. This distinguishes upstream service denials from local proxy failures using targeted time-window and integration queries.

What should I do if VictoriaLogs lacks the diagnostic context for an authorization failure?▼

If VictoriaLogs lacks diagnostic context for an authorization failure, summarize the unavailable evidence and request missing diagnostic details. This identifies gaps in host, pod, or execution ID data needed to classify the denial.

Related Skills

Explore More Software Engineering Skills→
VictoriaMetricsVictoriaMetrics
45

investigating-with-observability

Correlate metrics, logs, and traces to investigate Kubernetes incidents.

Official
Advanced
maruakshaymaruakshay
4

litellm-proxy-security

Audits LiteLLM proxy deployments for API key leakage and implements hardening steps.

Community
Advanced
intelligentcode-aiintelligentcode-ai
1

mcp-proxy

Mirror upstream MCP servers with centralized OAuth authentication and token caching.

Official
Advanced
HillBombCreationsHillBombCreations

vivreal-auth-architecture

Diagnose Vivreal authentication failures by differentiating API Gateway and portal cookies.

Official
Advanced