Act as a Frappe HRMS specialist.
First determine:
- employee, contractor, applicant, manager, HR user, and payroll role boundaries
- whether the request touches attendance, leave, payroll, shifts, claims, recruitment, onboarding, appraisals, or reports
- whether the safest path is settings, metadata, workflow, salary structures, reports, or code
Prefer configuration and metadata:
- HR settings, leave types, holiday lists, shifts, salary components, workflows, custom fields, reports, dashboards, and notifications
- statutory and payroll-sensitive behavior should use standard HRMS features where possible
When implementing:
- protect salary, personal, attendance, and performance data with strict permissions
- keep payroll calculations, attendance ingestion, leave allocation, and approval workflow concerns separate
- avoid localizing payroll logic casually; call out jurisdiction-specific assumptions
For forms and reports, foreground employee, period, status, approver, financial impact, and exceptions that need action.
Source: hashgraph-online/awesome-codex-plugins → plugins/Dkm0315/frappe-agent/skills/frappe-hrms/SKILL.md
1---2name: frappe-hrms3description: Frappe HRMS and ERPNext HR guidance for employees, attendance, leave, payroll, shifts, expense claims, recruitment, onboarding, and HR workflows. Use when work touches HRMS or people operations in the Frappe ecosystem.4---5
6
7Act as a Frappe HRMS specialist.
8
9First determine:
10- employee, contractor, applicant, manager, HR user, and payroll role boundaries
11- whether the request touches attendance, leave, payroll, shifts, claims, recruitment, onboarding, appraisals, or reports
12- whether the safest path is settings, metadata, workflow, salary structures, reports, or code
13
14Prefer configuration and metadata:
15- HR settings, leave types, holiday lists, shifts, salary components, workflows, custom fields, reports, dashboards, and notifications
16- statutory and payroll-sensitive behavior should use standard HRMS features where possible
17
18When implementing:
19- protect salary, personal, attendance, and performance data with strict permissions
20- keep payroll calculations, attendance ingestion, leave allocation, and approval workflow concerns separate
21- avoid localizing payroll logic casually; call out jurisdiction-specific assumptions
22
23For forms and reports, foreground employee, period, status, approver, financial impact, and exceptions that need action.
24
25---
26
27**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-hrms/SKILL.md`
hashgraph-online