triage

Extract FreshService ticket details and create linked GitHub issues.

2|3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/psd401/psd-claude-coding-system --skill triage-psd401
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/psd401/psd-claude-coding-system/tree/main/plugins/psd-claude-coding-system/skills/triage
Command: npx skills add https://github.com/psd401/psd-claude-coding-system --skill triage-psd401

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

FreshService ticket triage can be slow and error-prone, leading to delays in engineering response. This Skill automates the extraction of essential ticket details and the creation of a structured GitHub issue, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Automatic ticket interpretation: Fetches FreshService ticket data, including subject, description, requester, and conversations, and formats it into a comprehensive GitHub issue body.
  • GitHub issue creation: Creates a new GitHub issue from the triaged data and links back to the FreshService ticket for traceability.
  • Ticket update workflow: Adds a reply to the FreshService ticket and updates its status to reflect progress.
  • Use Case: A support team receives a bug report in FreshService; the skill produces a ready-to-submit GitHub issue with clear reproduction steps and context.

Quick Start

/triage <ticket-id>

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate triage of FreshService tickets into GitHub issues?

Automate ticket triage by extracting FreshService ticket details and generating GitHub issues with a single command. The Skill fetches subject, description, requester, and conversation data, formats it into a structured GitHub issue body, creates the issue, and updates the ticket status—eliminating manual formatting and reducing engineering response delays.

Can I link FreshService tickets to GitHub issues for traceability?

Yes. When the Skill creates a GitHub issue from a FreshService ticket, it maintains bidirectional traceability by embedding the FreshService ticket reference in the issue body and adding a reply to the original ticket linking back to the GitHub issue, ensuring support and engineering teams stay coordinated.

What data does the Skill extract from FreshService tickets?

The Skill extracts ticket subject, description, requester information, and full conversation history from FreshService. It then formats this data into a comprehensive GitHub issue body with clear context, reproduction steps, and metadata, ready for engineering teams to act on immediately.

How do I get started with automating ticket triage?

Run `/triage <ticket-id>` to start. The Skill requires FreshService and GitHub API credentials for ticket retrieval, issue creation, and status updates. It validates credentials, fetches the ticket, formats the data, creates the GitHub issue, and updates the FreshService ticket status in one workflow.

Does this work for support teams using both FreshService and GitHub?

Yes. This Skill is designed for support workflows where FreshService handles incoming tickets and GitHub manages engineering tasks. It bridges both platforms by automatically converting support tickets into actionable GitHub issues with full context, reducing handoff delays and manual interpretation.

What happens after a GitHub issue is created from a ticket?

The Skill updates the FreshService ticket status to reflect progress and adds a reply containing the GitHub issue link for traceability. This keeps the support team informed of where the ticket stands in the engineering workflow while maintaining a complete audit trail.