--- title: "Gorgias bug report writer" type: "skill" url: "https://useaiblocks.com/skills/gorgias-bug-report-writer" updated: "2026-10-28" first_published: "2026-10-25" job: "Help your customers" tested: true licence: "MIT" source: "https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/bug-report" instructions: "https://useaiblocks.com/skills/gorgias-bug-report-writer/SKILL.md" --- # Gorgias bug report writer > Share a Gorgias ticket. Get a bug report with known steps, evidence and missing details, then choose whether to create a Linear issue. Use a Composio setup linked to Gorgias and share the ticket number. It reads the thread and separates expected behaviour, reported behaviour, evidence and gaps. Get a bug report to review. If you approve creating a Linear issue, it asks for the team, creates the issue and returns its link. Missing steps and impact stay marked for follow-up. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-bug-report-writer - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-bug-report-writer/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-bug-report-writer.zip - JSON version: https://useaiblocks.com/skills/gorgias-bug-report-writer.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-bug-report-writer" ## What you give it - A Gorgias ticket number for a reported bug. - The Linear team that should get the issue (optional). ## What you get - A bug report with title, steps, expected and actual results, impact and quoted evidence. - A list of details missing from the ticket, and what to ask the customer. - A Linear issue link, only after you approve the report and pick the team (optional). ## Example: what goes in and what comes out ### What goes in - Your Gorgias ticket number for a reported bug - Which Linear team should get the issue (optional, only if you create one) ### Before you start - An AI that can run Composio CLI commands - Gorgias connected through Composio - Linear connected through Composio (only to create an issue) ### What comes out - **Bug Report header**: The ticket source, reporter, date reported and a severity rating of Critical, High, Medium or Low. - **Title and Description**: A clear bug title, not the ticket subject, and a one or two sentence summary. - **Steps to Reproduce**: Numbered steps taken from the customer thread, with gaps flagged as missing. - **Expected Behavior and Actual Behavior**: What should have happened, next to what the customer says happened. - **Environment and Evidence**: Browser, system, account details, quoted error messages, and screenshots or IDs the customer mentioned. - **Impact**: How many users are affected, whether a workaround exists, and any revenue impact if it can be found. - **Additional Context**: Other useful details from the thread, plus a list of missing information to ask the customer for. - **Linear issue link**: Only if you approve: a new issue in the team you pick, with the full report inside. ## Use it when - A customer writes in about something broken and your engineers need a clear report. - A ticket thread has grown long and nobody has pulled out the steps to reproduce. - You want to hand a bug to engineering without retyping the customer's words. - You need to know what to ask the customer before the bug can be fixed. ## Skip it when - The ticket is a feature request or a billing question: reply to the customer yourself or ask a support lead, since this tool only reads bug reports. - You have no Composio access to Gorgias or Linear: paste the ticket text into your AI and ask for a bug report by hand. - You want a bug fixed or the cause found: send the finished report to your engineers, because this tool only writes the report. ## How to use it 1. Use an AI that can run commands and read skill files. Install Composio CLI and connect Gorgias. Connect Linear too if you want an issue. 2. Add the downloaded folder to your AI and ask it to run the Gorgias bug report writer. 3. Give it the ticket number of a bug report. Say which ticket it is. 4. Read the report. Check the steps and the missing details, and fix anything that looks wrong. 5. If you want a Linear issue, say yes and pick the team. Nothing is created before you approve. 6. If a step says Gorgias is not connected, run the link command your AI shows, then try again. ## What to do next - [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator): Support issue cause investigator - [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer): Escalation brief writer - [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer): Support ticket help article writer ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/bug-report, shared under the MIT licence (original name: bug-report). - [bug-report skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/bug-report), Composio: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Bug Report Generator You are a QA-minded support engineer. Given a [Gorgias](https://composio.dev/toolkits/gorgias) ticket that describes a bug, extract a structured, engineering-ready bug report and optionally create it as a Linear issue. The user's input is: $ARGUMENTS ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **Your question** (yours): the decision or problem, and what a good outcome looks like. - **A tool connection** (yours): an AI connected to an outside tool or service, such as an MCP server. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for your question, a tool connection. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. **Tools that do this best:** - **Gorgias and Linear:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "get support ticket details from Gorgias" "create an issue in Linear" "list teams in Linear"` in Bash. #### Step 2: Fetch ticket Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in Bash. Parse the JSON output and extract all messages to understand the full bug context. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry. #### Step 3: Build the bug report Analyze the ticket thread and extract: ``` ## Bug Report **Source:** Gorgias Ticket #[ID] **Reporter:** [Customer name/email] **Date Reported:** [date] **Severity:** [Critical/High/Medium/Low] ### Title [Clear, specific bug title - not the ticket subject verbatim] ### Description [1-2 sentence summary of the bug] ### Steps to Reproduce 1. [Step 1] 2. [Step 2] 3. [Step 3] ### Expected Behavior [What should happen] ### Actual Behavior [What actually happens] ### Environment - Browser/OS: [if mentioned] - Account/Plan: [if relevant] - API version: [if applicable] ### Evidence - [Screenshots mentioned by customer] - [Error messages quoted] - [Logs or IDs referenced] ### Impact - **Users affected:** [single user / multiple / all] - **Workaround available:** [yes/no + description] - **Revenue impact:** [if determinable] ### Additional Context [Anything else from the thread that's relevant] ``` #### Step 4: Offer to create Linear issue Ask the user if they want to create this as a Linear issue. After confirmation: 1. Run `composio execute LINEAR_LIST_LINEAR_TEAMS -d '{}'` in Bash to let user pick the team 2. Run `composio execute LINEAR_CREATE_LINEAR_ISSUE -d '{...team_id, title, description...}'` in Bash, including the full bug report as the description 3. Parse the JSON output and return the Linear issue link If info is missing from the ticket (e.g., no repro steps), explicitly flag what's missing and suggest the agent ask the customer for it. ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator). It takes the audit report. - The [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer). It takes the audit report. - The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the audit report. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.