Orchestrate read-only investigations of Backstage OSS and Portal issues from code, configs, and logs.
npx skills add https://github.com/meganide/claude --skill support-debug
Please help me install this Agent Skill. Skill: support-debug Source: https://github.com/meganide/claude/tree/main/skills/support-debug Command: npx skills add https://github.com/meganide/claude --skill support-debug
This Skill helps support teams investigate Backstage OSS and Portal issues by collecting, validating, and organizing evidence from code, configuration, and logs, enabling rigorous root-cause analysis without making changes.
To begin a session, trigger the support-debug skill, gather the complete ticket context, fetch the full conversation, retrieve the current Portal config, search for known issues and relevant docs, then compile findings into a structured report.
High-intent search queries and answers about installing and using this skill.
You can investigate Backstage Portal issues by collecting and validating evidence from code, configs, and logs. This read-only root-cause analysis approach determines root causes without modifying systems, producing traceable references and customer-ready summaries.
The best way to structure support investigations is through a formal validation workflow that handles ticket context and cross-repo checks. This method organizes evidence from logs and documentation to produce actionable findings with traceable references for effective remediation.
Yes, you can investigate misconfigurations and plugin bugs using cross-repo exploration. This process gathers and validates evidence across different codebases simultaneously, ensuring comprehensive root-cause analysis without making system changes.
Backstage OSS investigations can use a formal validation workflow to process support tickets. This workflow collects ticket context, searches known issues, and validates evidence from documentation and logs to ensure accurate root-cause analysis.
To compile support findings into a customer-friendly summary, aggregate validated evidence and traceable references from your investigation. This structured output translates technical root-cause analysis into recommended remediation steps for the customer.
The limitation of read-only investigation for deployment problems is that it determines root causes without modifying systems. It restricts analysts to collecting and validating evidence, meaning direct remediation must be handled separately after the report is generated.
martinjlowmRetrieve Zendesk ticket metadata and full comment threads with attachments.
swghoshDiagnose software bugs through evidence-based root cause analysis.
gleanworkSearch internal source code across repositories to identify patterns and ownership.
colajacquin-eLaunch Code OSS with remote debugging and automate UI interactions via agent-browser.
