paradigmxyz/centaur / .agents/skills/auth-failure-log-triage
auth-failure-log-triage
VerifiedInvestigate reported auth, credential, permission, API proxy, 401, 403, 503, OAuth, token, or secret-resolution failures by querying VictoriaLogs first through the `vlogs` Code Mode connector. 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.1 KB |
SKILL.md
View on GitHub---
name: auth-failure-log-triage
description: "Investigate reported auth, credential, permission, API proxy, 401, 403, 503, OAuth, token, or secret-resolution failures by querying VictoriaLogs first through the `vlogs` Code Mode connector. 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."
---
# 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
1. Confirm the affected surface from the user message: tool/integration name, URL host, thread key, execution id, pod/service, and rough time window.
2. Query logs with the `vlogs` connector in Code Mode (`centaur-codemode exec --result-only`). `centaur-codemode load vlogs` prints every function and its arguments.
3. 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:
```js
return await tools.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:
```js
const thread_key = "THREAD_KEY";
const [trace, usage] = await Promise.allSettled([
tools.vlogs.thread_trace({ thread_key, start: "24h", limit: 500 }),
tools.vlogs.tool_usage_by_thread({ thread_key, start: "24h", limit: 200 }),
]);
return { trace, usage };
```
For a specific execution:
```js
return await tools.vlogs.execution_timeline({ execution_id: "EXECUTION_ID" });
```
4. If the direct query is empty, find labels first:
```js
const [services, fields, streams] = await Promise.allSettled([
tools.vlogs.field_values({ field: "service", query: "*proxy*", start: "24h", limit: 200 }),
tools.vlogs.field_names({ query: "service:iron-proxy", start: "24h" }),
tools.vlogs.streams({ query: "proxy", start: "24h" }),
]);
return { services, fields, streams };
```
5. 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |