skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

runtime-triage

Classify Roku BrightScript crash logs and generate investigation handoff packets.

37|2|Updated Jun 28, 2025
Search Tags:#log-parsing#runtime-triage#jellyrock#roku#brightscript#crash-investigation#render-thread
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill runtime-triage-jellyrock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-triage
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/runtime-triage
Command: npx skills add https://github.com/jellyrock/jellyrock --skill runtime-triage-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JellyRock runtime failures on Roku devices produce cryptic BrightScript logs that are difficult and time-consuming to diagnose manually. This Skill automates the entire triage workflow, turning raw crash logs into structured investigations with probable root causes, file context, and actionable next steps.

Core Features & Use Cases

  • Automated Log Parsing: Extracts the critical error signal from hundreds of lines of BrightScript console output.
  • Failure Classification: Categorizes crashes into render-thread-crash, task-crash, api-error, registry-corruption, nav-error, or unknown based on error patterns.
  • Investigation Handoff: Writes a structured handoff packet with file context, recent commits, and architecture references to guide root-cause analysis.
  • Use Case: A user pastes a Roku debug console log showing "Sub or function not found" during video playback; the Skill identifies it as a render-thread-crash in the video player component and surfaces the exact files and lines to inspect.

Quick Start

Paste your Roku BrightScript crash log or debug console output into the Skill to receive an instant classification, probable code area, and investigation handoff packet.

Frequently Asked Questions about runtime-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse Roku BrightScript crash logs to find the root cause?▼

Roku BrightScript crash logs are parsed by extracting critical error signals from console output and categorizing failures into render-thread crashes, task crashes, API errors, registry corruption, or navigation errors. This automated triage maps errors to probable code areas without manual deduplication.

What is a render-thread crash in BrightScript and how is it investigated?▼

A render-thread crash in BrightScript is a runtime failure on the main UI thread, investigated by classifying the error pattern and generating a handoff packet with file context and architecture references. This packet surfaces the exact files and lines to inspect for root-cause analysis.

Can I triage Roku registry corruption and API errors from debug console output?▼

Yes, you can triage Roku registry corruption and API errors from debug console output by applying deterministic log parsing to categorize failures. The workflow classifies these specific error patterns and assembles structured context for investigation handoff.

What's the best way to automate crash investigation for Roku runtime failures?▼

Automate crash investigation for Roku runtime failures by using a deterministic triage workflow that classifies crashes and generates a structured handoff packet. This approach provides failure categorization, probable code area mapping, and architecture references without prior handoff scanning.

Does BrightScript log triage work for task crashes and navigation errors?▼

Yes, BrightScript log triage works for task crashes and navigation errors by categorizing them based on distinct error patterns extracted from the console output. The workflow identifies the failure type and maps it to the relevant component files for inspection.

Why do I get a Sub or function not found error during Roku video playback?▼

A Sub or function not found error during Roku video playback indicates a render-thread crash in the video player component. Triage the crash log to classify the failure, map the probable code area, and generate an investigation handoff packet with the exact files and lines to inspect.

Related Skills

Explore More Software Engineering Skills→
jellyrockjellyrock
37

crash-report

Convert Roku crash-report CSVs into tracked GitHub issues with source-map resolution.

Official
Advanced
berkcangumusisikberkcangumusisik
11

debug-helper

Parse error messages and stack traces to identify root causes.

Community
Intermediate
Thanh-aperoThanh-apero
1

ck:watzup

Summarize recent repository commits and their impact on code quality.

Community
Intermediate
blouargantblouargant

k8s-log-investigation

Investigate Kubernetes pod log streams for failure signals with progressive context expansion.

Community
Intermediate