Create Ticket

Generate standardized Kira TicketPayloads from incident analysis outputs.

3|Updated Apr 16, 2026

Search Tags:#automation #sre #root-cause #ticketing #incident-analysis #kira

Ready to run

npx skills add https://github.com/rhpds/athena-aiops-deep-agent --skill create-ticket-rhpds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Create Ticket
Source: https://github.com/rhpds/athena-aiops-deep-agent/tree/main/skills/create-ticket
Command: npx skills add https://github.com/rhpds/athena-aiops-deep-agent --skill create-ticket-rhpds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of standardized Kira TicketPayloads from incident analysis outputs, reducing manual formatting errors and ensuring consistency across tickets.

Core Features & Use Cases

Enforces and documents all required fields for a Kira TicketPayload (title, description, area, confidence, risk, stage, recommended_action, affected_systems, skills, issues, agent_name).
Provides a structured template that includes sections for Summary, Evidence, Root Cause, and Impact.
Supports generation of sub-issues for distinct problems found within a single incident, enabling granular tracking and remediation.

Quick Start

Provide a complete TicketPayload for a new incident by filling in all required fields and adding any relevant sub-issues.

Frequently Asked Questions about Create Ticket

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

FAQPage Schema

How do I convert incident analysis outputs into a structured ticketing format?▼

Incident analysis outputs are converted into structured tickets by generating a standardized payload with required fields like title, area, risk, and a description containing Summary, Evidence, Root Cause, and Impact sections. This ensures consistent formatting across all incident tickets.

What is the best way to automate Kira ticket creation from failed automation jobs?▼

Automating Kira ticket creation from failed automation jobs requires mapping the incident data to a standardized TicketPayload, ensuring fields like affected_systems, confidence, and recommended_action are populated to reduce manual formatting errors.

Can I generate sub-issues for distinct problems found within a single IT operations incident?▼

Yes, sub-issues can be generated for distinct problems found within a single IT operations incident, enabling granular tracking and remediation of individual root-cause analyses within the primary ticket.

Do I need specific SRE agent details when creating a root-cause analysis ticket?▼

Yes, a root-cause analysis ticket requires an agent_name field set to the designated SRE agent, along with other mandatory fields like stage, skills, and issues to ensure proper incident tracking and accountability.

What required fields are enforced when creating a ticket payload for IT operations incidents?▼

Required fields enforced for IT operations incident tickets include title, description, area, confidence, risk, stage, recommended_action, affected_systems, skills, issues, and agent_name to maintain standardized documentation.

Why does my incident ticket payload fail validation during root-cause analysis?▼

Incident ticket payload validation fails during root-cause analysis if required fields such as title, area, confidence, risk, stage, recommended_action, affected_systems, skills, issues, or agent_name are missing or incorrectly formatted.