Ue Log Analyzer
v1.0.0Analyze Unreal Engine log files for errors, warnings, crashes, and performance issues. Use when: (1) User provides UE log file, (2) Analyzing crash dumps, (3...
⭐ 1· 371·0 current·0 all-time
byVincent@vincentwilliam
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (UE log analysis) match the SKILL.md instructions: searching logs for errors/warnings, crash GUIDs, timing, and project-specific patterns. It requires no extra credentials or installs, which is proportional to a log-analysis helper.
Instruction Scope
The instructions are limited to searching and summarizing provided UE log files and giving likely causes/fixes, which fits the stated purpose. However, the Quick Start references a 'nodes' tool to read logs from a paired computer and a 'read' command for local files; these tools are not declared in requirements and imply an external mechanism for obtaining files. That dependency is ambiguous and should be clarified before use. The SKILL.md does not instruct the agent to collect or transmit logs to external endpoints.
Install Mechanism
No install spec or code files are present; this is instruction-only so nothing is written to disk by the skill itself. That is the lowest-risk install profile.
Credentials
The skill requests no environment variables, credentials, or config paths. This is appropriate for a tool that analyzes files the user provides. Note: UE logs may contain sensitive information (paths, user IDs, potentially API keys or tokens) — the skill does not request secrets but the user should avoid supplying logs that contain sensitive data.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or elevated privileges and does not attempt to modify other skills or global agent configuration.
Assessment
This skill is an instruction-only UE log analyzer and appears coherent for that purpose. Before installing, confirm whether your agent environment provides the 'nodes' and 'read' helpers the SKILL.md mentions (they are not declared). Only supply log files you are comfortable sharing — logs can include PII or secrets. If you need the skill to pull logs from another machine, verify and authorize the specific mechanism (paired computer/node access) rather than granting broad file access. If you want higher assurance, request the author to declare any helper tools and to document exactly how files are accessed.Like a lobster shell, security has layers — review code before you run it.
latestvk973gkwrsdbw027kt8fn5d7trh8242y0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.