frappe-helpdesk

Frappe Helpdesk implementation and customization guidance for ticket intake, SLAs, assignment, portals, knowledge base, notifications, and support workflows.

Skill by Dkm0315

IndexedMIT★ 26

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dkm0315-frappe-helpdesk

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/frappe-helpdesk

What's inside

Skill 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.
License: MIT
Instructions: 21 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

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.

From Dkm0315/frappe-agent, MIT.

Signals

Stars: 26
Forks: 4
Open issues: 1
Last commit (this folder): Jun 27, 2026 (4 months ago)
Last release: May 16, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/Dkm0315/frappe-agent
Website: hol.org/registry/plugins/dhairya-marwaha%2Ffrappe-agent
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Dkm0315

Cite this page

frappe-helpdesk skill. Agent Mart. https://agentmart.dev/skills/dkm0315-frappe-helpdesk (last updated 2026-10-24)