> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qoder.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Case 25: Browser Crash Log Extraction

## Scenario

Alex is a backend engineer. The team uses an internal crash log platform. When something breaks, he opens the browser, logs in, finds the crash, copies the stack trace, pastes into a doc, and analyzes. Simple but repetitive. Login sessions expire, so he re-enters credentials often.

## Prompt Example

```plaintext theme={null}
Extract crash info from our internal platform:
1. Open browser, go to http://crash.internal.company.com
2. Log in if needed (credentials saved in browser)
3. Search for crash ID: CRASH-2024-03-001
4. Extract the full stack trace
5. Save as Markdown, filename includes crash ID
6. Briefly analyze the stack and suggest likely causes
```

## What QoderWork Did

QoderWork opened the browser, logged in, searched, extracted the stack trace, saved it as Markdown, and added a short analysis (e.g., "NullPointerException at UserService.java:128—possible uninitialized user object").

## Ongoing Use

Alex packaged this as a Skill. For each alert: "Extract and analyze crash CRASH-2024-03-002." QoderWork does the work; he reviews the analysis.

## Key Metrics

| Metric   | Result                          |
| -------- | ------------------------------- |
| Use case | Typical dev workflow automation |
| Fit      | Simple, high-frequency task     |
| Value    | Extract + analyze in one step   |

## Pro Tips

Use **browser automation + Skill** for "simple but frequent" tasks.

Alex’s flow: same steps every time (login → search crash ID → copy stack). He added "analyze the stack and suggest causes" so QoderWork does both extraction and first-pass diagnosis. As a Skill: "Extract and analyze crash CRASH-xxx" with the ID as the only variable. **High-frequency, low-complexity tasks are ideal for automation.**