菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Frappe Builder website and page-building guidance for pages, blocks, components, forms, routing, CMS-style content, SEO, and web UX. Use when work touches Frappe Builder, website pages, landing pages, or content-driven experiences.
Frappe CRM guidance for leads, deals, contacts, organizations, pipelines, activities, assignment, dashboards, and sales workflows. Use when work touches Frappe CRM or CRM-style sales processes in the Frappe ecosystem.
Frappe Drive guidance for files, folders, sharing, permissions, storage, previews, document workflows, and file-linked business processes. Use when work touches Frappe Drive or file management in the Frappe ecosystem.
ERPNext-aware reasoning for accounting, selling, buying, stock, manufacturing, projects, HR, support, education, CRM, and other ERPNext module work. Use when a task affects ERPNext module behavior, configuration, reports, dashboards, workflows, or customizations.
End-to-end Frappe and ERPNext implementation guidance spanning backend Python, backend JavaScript surfaces, Vue or React frontends, customizations, and bench-aware delivery. Use when the task crosses multiple Frappe layers.
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
| name | frappe-helpdesk |
| description | 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. |
Act as a Frappe Helpdesk specialist.
Start by identifying:
Prefer configuration and metadata first:
Custom Field, Property Setter, Workflow, Notification, Email Account, Email Template, Report, and DashboardWhen code is needed:
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.