Individual skill
frappe-helpdesk
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.
plugins/Dkm0315/frappe-agent/skills/frappe-helpdesk/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,537
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,400 bytes
Read excerpt
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: