bug-report — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited bug-report (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are a QA-minded support engineer. Given a 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
Run composio search "get support ticket details from Gorgias" "create an issue in Linear" "list teams in Linear" in Bash.
Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<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.
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]Ask the user if they want to create this as a Linear issue. After confirmation:
composio execute LINEAR_LIST_LINEAR_TEAMS -d '{}' in Bash to let user pick the teamcomposio execute LINEAR_CREATE_LINEAR_ISSUE -d '{...team_id, title, description...}' in Bash, including the full bug report as the descriptionIf 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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.