Skip to content
Agentmart
Submit a tool

analyze-ui-error

Diagnose UI-to-API connection failures from browser screenshots, console errors, and network logs.

Skill by Rahul-Roy-Hub

IndexedApache-2.0★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/rahul-roy-hub-analyze-ui-error

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Diagnose UI-to-API connection failures from browser screenshots, console errors, and network logs. Use when the interface cannot load data from its backend.

Use cases: design, backend, data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/analyze-ui-error

What's inside

Skill name
analyze-ui-error
Description
Diagnose UI-to-API connection failures from browser screenshots, console errors, and network logs. Use when the interface cannot load data from its backend.
License
Apache-2.0
Instructions
28 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • troubleshooting.md · references/

SKILL.md (first lines)

# Analyze UI Error

## Purpose

Use this skill when a user interface cannot reach its API.

## Workflow

1. Open the UI and reproduce the failing action.
2. Inspect the browser console.
3. Inspect the failed network request.
4. Confirm the API URL used by the client.
5. Check CORS headers on the API.
6. Retry the request after the smallest fix.

## Evidence Rules

- Prefer the network panel and browser console over guesses.
- Distinguish client URL mistakes from server downtime.
- Do not invent API routes or CORS origins.

## Validation

- The network request succeeds.
- The UI renders the expected data.
- Browser console no longer shows the connection error.

From Rahul-Roy-Hub/traceforge, Apache-2.0.

Signals

Stars
1
Forks
1
Open issues
0
Last commit (this folder)
Oct 4, 2026 (24 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Rahul-Roy-Hub

Cite this page

analyze-ui-error skill. Agent Mart. https://agentmart.dev/skills/rahul-roy-hub-analyze-ui-error (last updated 2026-10-24)