incident-report

Name: incident-report
Availability: InStock
Author: ludoplex

Generate standardized incident reports and escalation paths for Pearson Vue test centers.

Updated Aug 23, 2026

Search Tags:#templates #documentation #security #reporting #escalation #incident #test-center

Ready to run

npx skills add https://github.com/ludoplex/openclaw-deploy-template --skill incident-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-report
Source: https://github.com/ludoplex/openclaw-deploy-template/tree/main/openclaw-deploy-template/agents/pearsonvue/skills/incident-report
Command: npx skills add https://github.com/ludoplex/openclaw-deploy-template --skill incident-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test centers struggle with inconsistent incident reporting and slow escalation, leading to unresolved issues and delays in resolution. This Skill offers a standardized incident template, a defined taxonomy, and a clear escalation path to ensure timely responses.

Core Features & Use Cases

Incident Types: TECH (System/software failure, High), CAND (Candidate behavior, Medium), ENVR (Environment, Low), SECU (Security breach, Critical)
Immediate Actions: map codes to concrete actions and maintain audit trails
Documentation Template: fields for Date/Time, Exam/Candidate ID, Workstation, Incident Type, Description, Actions Taken, Witnesses, Attachments
Escalation: defined contacts and response targets aligned with severity levels
Support Numbers: US and UK numbers referenced in TOOLS.md for on-site reference
Use Case: standardize incident handling across Pearson Vue test centers

Quick Start

Describe the incident in natural language and let the skill generate a complete, labeled incident report using the provided template.

Frequently Asked Questions about incident-report

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

FAQPage Schema

How do I report a testing incident at a Pearson Vue test center?▼

To report a testing incident, describe the event in natural language and the system generates a standardized incident report using a predefined template with fields for Date/Time, Exam ID, Workstation, and Incident Type.

What types of test center incidents require formal escalation?▼

Formal escalation is required for technical failures (TECH), candidate behavior issues (CAND), environmental issues (ENVR), and security breaches (SECU), with each type mapped to a specific severity level and response target.

How do I escalate a security breach during a live exam?▼

Escalate a security breach by following the predefined escalation matrix for SECU incidents, which routes critical concerns to defined contacts and references support numbers in TOOLS.md for immediate on-site response.

Can I standardize documentation for candidate behavior issues during exams?▼

Yes, you can standardize documentation for candidate behavior issues by applying the CAND incident template, which captures candidate IDs, descriptions, actions taken, and witnesses to maintain a consistent audit trail.

What is the best way to maintain an audit trail for technical failures in a testing environment?▼

The best way to maintain an audit trail for technical failures is using the standardized incident template for TECH events, which maps severity codes to concrete actions and records all relevant workstation and system failure details.