How do I install the Uips Log Parser skill?

Run npx skillmds@latest add cprima-agents/uips-log-parser in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Uips Log Parser safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Uips Log Parser?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Uips Log Parser free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Uips Log Parser?

cprima-agents (@cprima-agents) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Uips Log Parser by cprima-agents — Agent Skill

Name: Uips Log Parser
Author: cprima-agents

Uips Log Parser

Parse and analyse UiPath Studio local execution logs to diagnose automation runs. Use when a developer asks about errors, warnings, duration, or status of a UiPath process run; when troubleshooting a failed, interrupted, or slow automation; when searching for a specific message across multiple runs. Triggers on: UiPath log, execution log, Studio run, robot error, job failed, process crashed, how long did it run, find in log.

cprima-agents 738f4b6 2 files · 20.1 KB Updated Sep 17, 2026

File contents

UiPath Studio Execution Log Parser

Parse local UiPath Studio execution logs grouped by job run (jobId).

Run the script

# Last job (default)
uv run skills/uips-log-parser/scripts/parse_logs.py

# Specific file
uv run skills/uips-log-parser/scripts/parse_logs.py --file "C:/Users/<user>/Downloads/2026-03-25_Execution.log"

# Last N runs from auto-discovered logs
uv run skills/uips-log-parser/scripts/parse_logs.py --last 5

# All runs, errors only
uv run skills/uips-log-parser/scripts/parse_logs.py --all --errors-only

# Search for a string across all runs
uv run skills/uips-log-parser/scripts/parse_logs.py --all --needle "Object reference"

# Show all log entries including Trace/Verbose (framework internals)
uv run skills/uips-log-parser/scripts/parse_logs.py --min-level Trace

# Duration between two copied log lines
uv run skills/uips-log-parser/scripts/parse_logs.py --duration "LINE1" "LINE2"

# Structured output for further processing
uv run skills/uips-log-parser/scripts/parse_logs.py --last 3 --format json

All diagnostics go to stderr; --format json sends clean JSON to stdout.

Understanding the output

Each run shows a status flag:

Flag	Meaning
`[ OK ]`	Execution ended normally, no errors
`[FAIL]`	Execution ended normally, with errors
`[ .. ]`	No "execution ended" message — may still be running, was interrupted, or log is truncated

Do not assume [ .. ] means failure. The run may be active right now.

Log auto-discovery

The script searches these locations by default:

%LOCALAPPDATA%\UiPath\Logs\ — Studio / attended Robot (user-level)
C:\ProgramData\UiPath\Logs\ — Robot service (system-level)

Use --log-dir PATH to override, or --file PATH to point at a single file.

Key CLI flags

Flag	Default	Purpose
`--last N`	1	Show last N runs
`--all`	off	Show all runs
`--days N`	7	Discovery lookback window
`--date YYYY-MM-DD`	—	Filter to one day
`--process NAME`	—	Filter by process name (substring)
`--needle TEXT`	—	Filter runs containing TEXT; highlights matches
`--errors-only`	off	Show only runs with errors
`--warnings`	off	Also show warning details
`--min-level LEVEL`	—	Show all entries ≥ LEVEL (Trace/Verbose/Information/…) in an "All entries" section
`--format json\|text`	text	Output format
`--list-files`	off	Show discovered files and exit

Windows encoding

UiPath log messages may contain Unicode characters (e.g. →) that crash the script when the Windows console uses its default cp1252 encoding. Set one of these before running:

$env:PYTHONUTF8 = "1"

or per-invocation:

$env:PYTHONUTF8 = "1"; uv run skills/uips-log-parser/scripts/parse_logs.py --min-level Trace

Gotchas

Log files start with a UTF-8 BOM (\xEF\xBB\xBF) — the script strips it automatically.
The [ .. ] status does not indicate a crash when the user is actively developing in Studio.
Duration (totalExecutionTime) is only present on the final "execution ended" entry. If the run is open, duration will be null in JSON / ? in text.
Multiple runs per day are in the same file, separated only by jobId.
The execution_log_data/ subfolder contains a SQLite DB (cloud-synced data) — the script does not read it.

---name: uips-log-parserdescription: Parse and analyse UiPath Studio local execution logs to diagnose automation runs. Use when a developer asks about errors, warnings, duration, or status of a UiPath process run; when troubleshooting a failed, interrupted, or slow automation; when searching for a specific message across multiple runs. Triggers on: UiPath log, execution log, Studio run, robot error, job failed, process crashed, how long did it run, find in log.license: Apache-2.0---# UiPath Studio Execution Log ParserParse local UiPath Studio execution logs grouped by job run (`jobId`).## Run the script```bash# Last job (default)uv run skills/uips-log-parser/scripts/parse_logs.py# Specific fileuv run skills/uips-log-parser/scripts/parse_logs.py --file "C:/Users/<user>/Downloads/2026-03-25_Execution.log"# Last N runs from auto-discovered logsuv run skills/uips-log-parser/scripts/parse_logs.py --last 5# All runs, errors onlyuv run skills/uips-log-parser/scripts/parse_logs.py --all --errors-only# Search for a string across all runsuv run skills/uips-log-parser/scripts/parse_logs.py --all --needle "Object reference"# Show all log entries including Trace/Verbose (framework internals)uv run skills/uips-log-parser/scripts/parse_logs.py --min-level Trace# Duration between two copied log linesuv run skills/uips-log-parser/scripts/parse_logs.py --duration "LINE1" "LINE2"# Structured output for further processinguv run skills/uips-log-parser/scripts/parse_logs.py --last 3 --format json```All diagnostics go to stderr; `--format json` sends clean JSON to stdout.## Understanding the outputEach run shows a status flag:| Flag | Meaning ||------|---------|| `[ OK ]` | Execution ended normally, no errors || `[FAIL]` | Execution ended normally, with errors || `[ .. ]` | No "execution ended" message — may still be running, was interrupted, or log is truncated |**Do not assume `[ .. ]` means failure.** The run may be active right now.## Log auto-discoveryThe script searches these locations by default:- `%LOCALAPPDATA%\UiPath\Logs\` — Studio / attended Robot (user-level)- `C:\ProgramData\UiPath\Logs\` — Robot service (system-level)Use `--log-dir PATH` to override, or `--file PATH` to point at a single file.## Key CLI flags| Flag | Default | Purpose ||------|---------|---------|| `--last N` | 1 | Show last N runs || `--all` | off | Show all runs || `--days N` | 7 | Discovery lookback window || `--date YYYY-MM-DD` | — | Filter to one day || `--process NAME` | — | Filter by process name (substring) || `--needle TEXT` | — | Filter runs containing TEXT; highlights matches || `--errors-only` | off | Show only runs with errors || `--warnings` | off | Also show warning details || `--min-level LEVEL` | — | Show all entries ≥ LEVEL (Trace/Verbose/Information/…) in an "All entries" section || `--format json\|text` | text | Output format || `--list-files` | off | Show discovered files and exit |## Windows encodingUiPath log messages may contain Unicode characters (e.g. `→`) that crash the script when the Windows console uses its default `cp1252` encoding. Set one of these before running:```powershell$env:PYTHONUTF8 = "1"```or per-invocation:```powershell$env:PYTHONUTF8 = "1"; uv run skills/uips-log-parser/scripts/parse_logs.py --min-level Trace```## Gotchas- Log files start with a UTF-8 BOM (`\xEF\xBB\xBF`) — the script strips it automatically.- The `[ .. ]` status does **not** indicate a crash when the user is actively developing in Studio.- Duration (`totalExecutionTime`) is only present on the final "execution ended" entry. If the run is open, duration will be `null` in JSON / `?` in text.- Multiple runs per day are in the same file, separated only by `jobId`.- The `execution_log_data/` subfolder contains a SQLite DB (cloud-synced data) — the script does not read it.

Frequently asked questions