diagnose-run
Skill71 starsChanged 36 days agoMITView on GitHub
Diagnose a failed, degraded, slow, or suspicious investment-analysis run from repository logs and generated artifacts. Use for run failures, missing outputs, unexpected verdicts, timeouts, or cost anomalies.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- appsec-foundry/appsec-advisortheir own version, first seen Oct 17, 2026
- matt-whitaker/claude-team-exampletheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- appsec-foundry/appsec-advisor★ 18same name
- matt-whitaker/claude-team-example★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-agentSkill
- analyze-tickerSkill
- maintain-agent-metadataSkill
- run-pipelineSkill
- run-testsSkill
- add-agentSkill
- analyze-tickerSkill
- diagnose-runSkill
- run-testsSkill
- validation-batchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use tracked diagnostic programs when they match the evidence:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Diagnose an analysis run
Diagnose from evidence before proposing changes. Generated artifacts under results/
and runtime logs are outputs of normal execution, not instruction dependencies.
- Identify the requested ticker, mode, invocation, approximate time, and expected output. Do not infer these from unrelated local history.
- Inspect the retained artifact and its validity, failure classification, execution summary, binding telemetry, and tool/LLM diagnostics. Never reproduce credentials, request headers, raw provider payloads, or environment-file content.
- Separate the first causal failure from downstream symptoms. Distinguish application defects from provider refusal, rate limiting, network failure, invalid input, unavailable optional services, and expected degraded behavior.
- Use tracked diagnostic programs when they match the evidence:
scripts/scan_batch_health.pyfor a batch or freshness check.scripts/summarize_quick_slow_tail.pyfor quick-mode timeout tails.scripts/cost_report.pyfor saved cost and binding rollups.scripts/mcp_smoke.pyfor an explicitly requested MCP connectivity check.
- Trace the owning code from
src/runtime_diagnostics/,src/runtime_services.py,src/tooling/, or the relevant provider adapter. Check retry and fallback paths. For timeout incidents, inspectsrc/llm_runtime/timeouts.pyandsrc/llm_runtime/run_deadline.py: separate request, invocation, node and ticker scopes, admission refusal, transport timeout and external watchdog termination. Inspect retained dispatch records for effective tier, remaining allowance and attempt limits; distinguish configured SDK limits from observed requests. Trace both canonical and legacy construction, plus direct writer/health callers. A timeout cluster alone does not establish provider capacity or physical retry counts. Check publication validity and recorded cost after failure or recovery. - Report cause, confidence, evidence, user impact, and the smallest plausible fix.
For operational timeouts, verify the allowance is resolved before request creation, and that inspection remains bounded and fail-closed. Tool/data scopes read the enclosing deadline without rebinding it around their judge. Embedding requests use live configuration and the caller's allowance; the cached startup probe is a separate scope and must not inherit a short caller deadline.
For MCP, verify timeout values reach the SDK's HTTP, session and tool-call parameters. Check allowance again between initialization, catalog acquisition and tool dispatch; a session's initial timeout is not the next operation's remaining budget. Follow the spent-allowance error path outside the session body so it does not destabilize the SDK's task-group cleanup.
Diagnosis alone does not authorize code edits, a paid rerun, a network probe, or a credentialed integration test. Ask before taking those actions unless the user already requested them explicitly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

