From connectwise
Use when opening a new ConnectWise service ticket — e.g. "open a ticket for Acme", "log a new issue: printer down at the front desk", "create a ticket and assign it to me". Resolves company, board, status, priority, and contact, then creates a well-formed ticket.
How this skill is triggered — by the user, by Claude, or both
Slash command
/connectwise:create-ticketThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a request into a properly-formed ticket on the right board — not a bare summary that dispatch has to clean up.
Turn a request into a properly-formed ticket on the right board — not a bare summary that dispatch has to clean up.
psa_create_ticket — create it (only summary + company are strictly required)psa_list_boards — find valid board namespsa_get_board_info — valid statuses / types / subtypes for a boardpsa_get_company / psa_search_contacts — resolve company and contact"acme") or confirm via psa_get_company. If fuzzy, psa_search_companies and confirm.psa_list_boards lists valid names — board drives which statuses/types are legal.psa_get_board_info before setting them, or omit and let ConnectWise default. Never guess a status name.psa_search_contacts filtered to the company; match by name/email.summary (≤100 chars) and an initialDescription with the real detail (symptoms, affected user/device, when it started, impact). Set severity/impact if the user signals urgency."Printer down at Acme front desk, urgent"
Resolve company="acme", board "Help Desk", priority via psa_get_board_info, then:
psa_create_ticket {
summary: "Front desk printer offline",
companyIdentifier: "acme",
board: "Help Desk",
priority: "Priority 2 - High",
initialDescription: "Front-desk shared printer is offline and unreachable...",
severity: "High", impact: "Medium"
}
psa_get_board_info.summary ≤ 100 chars; put detail in initialDescription.npx claudepluginhub patrickking67/connectwise-mcp --plugin connectwiseGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.