Awesome Claude Prompts Unofficial

Diagnose a failure from a console screenshot

Attach a dashboard screenshot in Claude Code; it explains why the resource is failing and lists the exact commands to fix it, each with a check.

Task: Diagnose a failure from a console screenshot · Other tasks

Fill in the details

Attach the screenshot itself in Claude Code. This page cannot attach images.

Optional. The tools the fix commands should use.

Optional. When it started, what changed, what you already tried.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

2 required fields are empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • A cloud console or dashboard shows that something is broken, and you want the cause explained and turned into commands you can run, rather than clicking through menus.
  • You can attach the screenshot in Claude Code first: drag it into the window, paste it with Ctrl+V (Alt+V on Windows and WSL), or give Claude the image file path. This site cannot attach images for you.
  • You are on call for a system you know only partly, and you want each fix step to come with a way to check that it worked before you move to the next one.

When not to use it

  • The useful information is text, such as an error message or a log excerpt. Paste the text instead, or use the error debugging or incident templates, because text is easier to quote and search than a picture of it.
  • The screenshot shows customer data, secrets or internal details you are not allowed to share with an AI tool. Crop or redact it first, or follow your incident policy.
  • You need Claude to confirm the diagnosis against the live system, but the command line tool is not installed or signed in where Claude Code runs. Set that up first, or treat the answer as a hypothesis to check yourself.

Why this structure

  • The opening line says what the screenshot shows and which resource is failing, so Claude knows where to look in the image and what counts as the problem.
  • The rule to quote what it reads from the screenshot makes Claude show its evidence. If it misreads a status or a number, you can see that straight away.
  • Asking Claude to say what is cut off or unreadable makes gaps in a partial screenshot visible, instead of leaving them to be filled with a plausible guess.
  • Read-only commands are allowed, so Claude can confirm the diagnosis if the tools are available, but any command that changes resources comes back to you to run.
  • Each fix command comes with a check and the report ends with risks and undo steps, so you can stop at the first step that does not behave as expected.

Example input (fictional)

What is failing
the checkout-api pod in the payments namespace
What the screenshot shows
our Kubernetes dashboard
Command line tools you use
kubectl and gcloud
What you have noticed so far
The pod has been Pending since the 10:40 deploy. Other pods in the cluster are also slow to schedule.

Follow-ups to send Claude

  • Run the read-only checks from step 3 yourself and show me the output before I run any fix.
  • Write the fix as a short runbook entry for the team: symptom, cause, commands, and how to confirm the fix.
  • What alert or dashboard panel would have shown this problem earlier? Suggest one we could add.

Common mistakes

  • Attaching a cropped screenshot that hides the status column, the timestamps or the error banner. Include the whole panel, or several screenshots.
  • Running every fix command at once. Run them one at a time and check each result, because a later command often depends on the earlier one having worked.
  • Forgetting to name the resource. A dashboard often shows many items, and Claude may diagnose the wrong one.
  • Investigate a production incident: Give Claude Code the symptom and when it started; it checks logs, recent deploys and config changes, then names the most likely cause with evidence.
  • Debug an error: Turn an error message and the code around it into a ranked list of likely causes, a check for each, and a fix you can try.
  • Query logs in plain English: Ask Claude Code a question about your logs; it writes a read-only query, runs it, and shows the query, the results and what stands out.

See all templates

Sources