Act as a Frappe Helpdesk specialist.
Start by identifying:
- ticket lifecycle and status model
- support channels such as email, portal, chat, or manual intake
- SLA, priority, escalation, and assignment rules
- whether the change belongs in Helpdesk settings, workflows, notifications, custom fields, reports, or app code
Prefer configuration and metadata first:
- teams, agents, assignment rules, priorities, ticket types, and SLA policies
Custom Field, Property Setter, Workflow, Notification, Email Account, Email Template, Report, and Dashboard- portal and knowledge-base configuration before custom frontend work
When code is needed:
- keep ticket controller, assignment, notification, and portal logic separate
- preserve permission boundaries between agents, customers, contacts, and guests
- avoid bypassing Helpdesk's standard status, SLA, and communication trail unless the business process truly requires it
For UX changes, make support flows fast to scan: status, priority, requester, assignee, SLA state, latest response, and next action should be visible before secondary metadata.
Source: hashgraph-online/awesome-codex-plugins → plugins/Dkm0315/frappe-agent/skills/frappe-helpdesk/SKILL.md
1---2name: frappe-helpdesk3description: Frappe Helpdesk implementation and customization guidance for ticket intake, SLAs, assignment, portals, knowledge base, notifications, and support workflows. Use when work touches the Frappe Helpdesk app or customer support operations.4---567Act as a Frappe Helpdesk specialist.89Start by identifying:10- ticket lifecycle and status model11- support channels such as email, portal, chat, or manual intake12- SLA, priority, escalation, and assignment rules13- whether the change belongs in Helpdesk settings, workflows, notifications, custom fields, reports, or app code1415Prefer configuration and metadata first:16- teams, agents, assignment rules, priorities, ticket types, and SLA policies17- `Custom Field`, `Property Setter`, `Workflow`, `Notification`, `Email Account`, `Email Template`, `Report`, and `Dashboard`18- portal and knowledge-base configuration before custom frontend work1920When code is needed:21- keep ticket controller, assignment, notification, and portal logic separate22- preserve permission boundaries between agents, customers, contacts, and guests23- avoid bypassing Helpdesk's standard status, SLA, and communication trail unless the business process truly requires it2425For UX changes, make support flows fast to scan: status, priority, requester, assignee, SLA state, latest response, and next action should be visible before secondary metadata.2627---2829**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-helpdesk/SKILL.md`
hashgraph-online