免费在 GitHub 公开

auth-failure-log-triage

Investigate authentication, permission, credential, OAuth, token, secret, and API proxy failures by checking live VictoriaLogs evidence first. Summarize relevant status codes and error details, and distinguish upstream denials from local proxy or secret resolution problems.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Investigate reported auth, credential, permission, API proxy, 401, 403, 503, OAuth, token, or secret-resolution failures by querying VictoriaLogs first. Use when a user says an integration auth failed, a tool got unauthorized/forbidden/service unavailable, an api-proxy request failed, or asks why credentials/secrets are not working.

paradigmxyz/centaur星标 1,407(GitHub 1,407 + cccskills 0)

实测评分未实测

查看安装方法

适用场景

Investigate a 401, 403, or 503 response
Trace an integration authentication failure
Check why a credential or secret is not resolving
Review an API proxy failure using runtime logs

包含的文件（1）

SKILL.md2.7 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Auth Failure Log Triage

When a user reports an auth, permission, credential, API proxy, OAuth, token, secret, 401, 403, or 503 failure, inspect live runtime evidence before proposing secret or permission changes.

Workflow

Confirm the affected surface from the user message: tool/integration name, URL host, thread key, execution id, pod/service, and rough time window.
Discover vlogs if needed:

call discover vlogs

Query likely auth failures in the last 24h, narrowing when the user gave a host, pod, thread, or execution id.

For Centaur API proxy / Iron Proxy issues:

call vlogs query '{"query":"kubernetes.pod_name:centaur-api-proxy-* AND (audit.status_code:401 OR audit.status_code:403 OR audit.status_code:503 OR \"failed to fetch secret\" OR unauthorized OR forbidden OR auth OR oauth OR token OR secret)","start":"24h","limit":100}'

For a specific thread:

call vlogs thread_trace '{"thread_key":"THREAD_KEY","start":"24h","limit":500}'
call vlogs tool_usage_by_thread '{"thread_key":"THREAD_KEY","start":"24h","limit":200}'

For a specific execution:

call vlogs execution_timeline '{"execution_id":"EXECUTION_ID"}'

If the direct query is empty, find labels first:

call vlogs field_values '{"field":"service","query":"*proxy*","start":"24h","limit":200}'
call vlogs field_names '{"query":"service:iron-proxy","start":"24h"}'
call vlogs streams '{"query":"proxy","start":"24h"}'

Summarize only what the logs support:

Counts by status code: 401, 403, 503.
Secret-resolution errors and the secret reference name, without exposing secret values.
Timestamp, pod, service, host, method, path, and status for concrete failures.
Whether auth transforms injected credentials, if shown by proxy fields such as request_transforms.
Distinguish upstream denial (audit.status_code=403) from local proxy/secret resolution failure (failed to fetch secret).

Output Rules

Lead with whether log evidence was found.
Do not claim a secret or permission is wrong unless logs show that.
Do not recommend secret rewiring until you have checked live vlogs evidence and compared the relevant error shape.
If no logs are found, say which query/window was checked and ask for the missing discriminator: time, thread key, execution id, host, or integration name.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

centaur

免费

Use an authenticated Centaur MCP deployment to find and call team-approved tools. It checks identity when permissions matter, follows the deployment’s current CLI help, and summarizes consequential changes with relevant identifiers or links.

中文简介正在准备中。当前显示英语简介。

Finding the right approved Centaur tool
Running an unfamiliar Centaur CLI command
Checking the signed-in user's permissions