Individual skill
frappe-hrms
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.
plugins/Dkm0315/frappe-agent/skills/frappe-hrms/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- 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,532
- Repository last updated
- Nov 6, 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,293 bytes
Read excerpt
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