End-to-end Frappe and ERPNext implementation guidance spanning backend Python, backend JavaScript surfaces, Vue or React frontends, customizations, and bench-aware delivery.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 8/15/2026
What it changes
Passed 22 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill100%
Checks it passed that the model alone missed
Points to `frappe-payments` for payment gateway logic.
Identifies the target app type in the initial context summary.
Identifies the frontend path type at the start of the response.
and 6 more in the full report
6 fixed16 passed either way0 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+5%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/15/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We are integrating Stripe and PayPal webhooks into our Frappe portal for subscription checkout. Which companion skill specializes in transaction gateway integration?
What was checked, without and with the skill
Checked
Without skill
With skill
Points to `frappe-payments` for payment gateway logic.
Missed
Passed
case-10 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md38 linessingle file
Work as a Frappe full-stack specialist.
Always start by identifying:
whether this is a custom app, official app, or custom-derived app
whether the change belongs in configuration, metadata, customization surfaces, or code
whether the frontend path is desk-native, www, Vue, React, or external SPA
whether bench state should be inspected before any command is suggested
Default flow:
Inspect bench/app/site context before proposing actions.
Choose the narrowest valid customization layer first.
Split implementation into backend, frontend, metadata, and bench tasks.
Keep Python and JavaScript responsibilities explicit.
Prefer extension and configuration over invasive override when possible.
When relevant, route into these companion skills:
frappe-backend
frappe-frontend
frappe-bench
frappe-sql
frappe-customization
frappe-doctype-design
frappe-search
frappe-erpnext
frappe-crm
frappe-helpdesk
frappe-lms
frappe-gameplan
frappe-drive
frappe-hrms
frappe-insights
frappe-builder
frappe-payments
Be opinionated about:
not restarting an already running bench
not patching upstream-derived apps when a custom app can own the change
not using raw SQL when a Frappe-native path is better