Automated summary
Analyzes the workshop application log from inside OpenShell and produces incident artifacts, including a JSON summary and a Markdown report.
Strengths
- Requires copying the source into /sandbox and writing scripts and outputs there, keeping the analysis contained.
- Requires parsing records before summarizing and computing specific metrics: levels, services, statuses, failing endpoints, slow requests, and p95 latency.
- Explicitly separates application errors (level=ERROR) from HTTP 5xx errors and forbids assigning an incident severity without a provided rubric.
- Includes reading the artifacts back before reporting success.
Limitations
- Relies on an OpenShell environment and a fixed fixture path (/workshop/data/sample_app.log).
- Does not cover live collection or monitoring; it works on a provided log.
- The report structure is prescribed, leaving limited room for alternate formats.
Use it when you need an incident summary, error spikes, or latency patterns from the workshop log inside OpenShell.
Avoid it for running a live production incident or analyzing logs outside the intended environment and fixture file.
Security analysis
SafeThe skill operates on a virtual log fixture, copies data into /sandbox, writes Python scripts and reports under /sandbox, and explicitly avoids nested sandboxes and credential exposure. No destructive, exfiltrating, obfuscated, or safety-disabling actions are instructed.
No concerns found
How this analysis is madeExamples
Analyze /workshop/data/sample_app.log in OpenShell. Copy it to /sandbox, parse it, and produce /sandbox/incident_summary.json and /sandbox/incident_report.md with error counts, 5xx counts, p95 latency, slow requests, timeline, suspected cause, and next actions. Read both files back.There’s an error spike in the workshop app log. Using incident-log-analysis, compute counts by level, service, status, and failing endpoint, keep level=ERROR separate from HTTP 5xx counts, and write the incident report artifacts under /sandbox.Investigate slow requests and p95 latency in /workshop/data/sample_app.log. Parse the records, then generate /sandbox/incident_summary.json and /sandbox/incident_report.md with evidence, timeline, suspected cause, and recommended next actions.name: incident-log-analysis description: Analyze the workshop application log from inside OpenShell and produce incident artifacts.
Incident Log Analysis
Use this skill for incident summaries, error spikes, latency patterns, and remediation recommendations.
Instructions
- Remember that the parent agent, subagent, Python process, and filesystem tools already run inside OpenShell.
- Treat
/workshop/data/sample_app.logas the virtual source fixture, backed by/app/workshop/data/sample_app.log. - Copy source data into
/sandboxbefore analysis. - Write Python scripts and generated files under
/sandbox. - Parse records before summarizing and compute counts by level, service, status, failing endpoint, slow requests, p95 latency, and first/last errors.
- Keep
level=ERRORcounts separate from HTTP 5xx counts, and do not assign an incident severity unless the participant provides a severity rubric. - Write
/sandbox/incident_summary.jsonand/sandbox/incident_report.md. - Read the artifacts back before reporting success.
- Do not create or call a nested sandbox and do not expose credentials.
Report Shape
# Incident Report
## Executive Summary
## Evidence
## Timeline
## Suspected Cause
## Recommended Next Actions
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/incident-log-analysis-mrwakcty/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/incident-log-analysis-mrwakcty' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/incident-log-analysis-mrwakcty/download' --output '.skill-downloads/incident-log-analysis-mrwakcty/SKILL.md.part' && mv '.skill-downloads/incident-log-analysis-mrwakcty/SKILL.md.part' '.skill-downloads/incident-log-analysis-mrwakcty/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/incident-log-analysis-mrwakcty/SKILL.md' && test -s '.skill-downloads/incident-log-analysis-mrwakcty/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/incident-log-analysis' && cp -R '.skill-downloads/incident-log-analysis-mrwakcty' '.claude/skills/incident-log-analysis'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/incident-log-analysis-mrwakcty'openskills read 'incident-log-analysis-mrwakcty'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/incident-log-analysis-mrwakcty/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.