erpnext-impl-serverscripts

Guide ERPNext server-script implementation decisions across v14–v16.

163|53|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package --skill erpnext-impl-serverscripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erpnext-impl-serverscripts
Source: https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package/tree/main/skills/source/impl/erpnext-impl-serverscripts
Command: npx skills add https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package --skill erpnext-impl-serverscripts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The ERPNext Server Script implementation guide helps teams decide how to implement client/server features, by mapping when to use server scripts, controllers, APIs, and scheduler hooks, reducing production issues.

Core Features & Use Cases

  • Comprehensive decision trees for selecting Script Type (Document Event, API, Scheduler, Permission Query)
  • Workflows and anti-patterns to avoid common ERPNext pitfalls
  • Real-world examples and templates to accelerate safe server-side development

Quick Start

Read the decision trees to choose your Script Type and apply the patterns to implement your first server script with proper validation.

Frequently Asked Questions about erpnext-impl-serverscripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I use ERPNext server scripts instead of custom controllers?

Use ERPNext server scripts for rapid feature implementation without modifying controllers. Decision trees map exact scenarios for selecting script types over controllers to avoid production issues.

How do I choose the right server script type in ERPNext?

Selecting the right server script type requires analyzing your trigger. Decision trees guide choosing among Document Event, API, Scheduler, and Permission Query scripts based on specific ERPNext feature requirements.

What are common anti-patterns and limitations when implementing ERPNext server scripts?

Common ERPNext server script anti-patterns include overstepping sandbox limitations and misusing schedulers. Implementation workflows and best practices help avoid these pitfalls and ensure safe server-side development.

Can I implement document events and permission queries using ERPNext server scripts?

Yes, ERPNext server scripts support document events and permission queries. Real-world templates and patterns accelerate safe implementation of these server-side features across v14-v16.

What is the best way to structure an ERPNext server script implementation workflow?

The best way to structure an ERPNext server script implementation is following defined workflows. Step-by-step patterns guide development from validation to execution, reducing common production issues.