frappe-agent-architect
Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication…
Use when building Query Reports, Script Reports, or configuring Report Builder, including chart data integration. Prevents report errors from wrong column definitions, missing permissions, and incorrect data formatting. Covers Query Report (SQL-based), Script Report
$ npx -y skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-syntax-reports --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/frappe-syntax-reportsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when building Query Reports, Script Reports, or configuring Report Builder, including chart data integration. Prevents report errors from wrong column definitions, missing permissions, and incorrect data formatting. Covers Query Report (SQL-based), Script Report
name: frappe-syntax-reports description: > Use when building Query Reports, Script Reports, or configuring Report Builder, including chart data integration. Prevents report errors from wrong column definitions, missing permissions, and incorrect data formatting. Covers Query Report (SQL-based), Script Report (Python-based), Report Builder, report columns definition, filters, chart_data, report permissions, prepared_report. Keywords: Query Report, Script Report, Report Builder, report columns, filters, chart_data, frappe.query_report, prepared_report, report columns, how to build report, report not showing data, chart in report.. license: MIT compatibility: "Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16." metadata: author: OpenAEC-Foundation version: "2.0"
| Type | Code Required | Use Case | Permission | |------|--------------|----------|------------| | Report Builder | None | Simple single-DocType listing with filters, group by | Any user | | Query Report | SQL only | Direct SQL queries, legacy column format | System Manager | | Script Report (Standard) | Python + JS | Complex logic, charts, summaries, trees | Administrator + Developer Mode | | Script Report (Custom) | Python in UI | Quick custom reports without app deployment | System Manager |
def execute(filters=None):
columns = [...] # List of dicts
data = [...] # List of dicts or lists
message = "..." # Optional: HTML message above report
chart = {...} # Optional: chart configuration
report_summary = [...] # Optional: summary cards
skip_total_row = False # Optional: suppress auto-total
return columns, data, message, chart, report_summary, skip_total_rowcolumns = [
{
"fieldname": "customer",
"label": _("Customer"),
"fieldtype": "Link",
"options": "Customer",
"width": 200
},
{
"fieldname": "amount",
"label": _("Amount"),
"fieldtype": "Currency",
"options": "currency", # field in row holding currency code
"width": 120
}
]SELECT name as "Sales Order:Link/Sales Order:200", customer as "Customer:Link/Customer:180", grand_total as "Total:Currency:120", transaction_date as "Date:Date:100" FROM `tabSales Order` WHERE docstatus = 1
Format: `"Label:Fieldtype/Options:Width"` — Options only needed for Link, Dynamic Link, Currency.
frappe.query_reports["My Report"] = {
filters: [
{
fieldname: "company",
label: __("Company"),
fieldtype: "Link",
options: "Company",
default: frappe.defaults.get_user_default("company"),
reqd: 1
},
{
fieldname: "from_date",
label: __("From Date"),
fieldtype: "Date",
default: frappe.datetime.add_months(frappe.datetime.get_today(), -1)
},
{
fieldname: "status",
label: __("Status"),
fieldtype: "Select",
options: "\nDraft\nSubmitted\nCancelled"
}
]
};Need a report?
├─ Simple list/group of one DocType → Report Builder
│ (no code, UI-only, supports Group By with Count/Sum/Avg)
├─ Direct SQL query, no Python logic needed → Query Report
│ (SQL in Report doc, column format in aliases)
├─ Complex logic, calculations, charts → Script Report (Standard)
│ (Python .py + JS .js files, requires Developer Mode)
└─ Quick one-off with Python but no app deploy → Script Report (Custom)
(Python in Report doc UI, System Manager can create)Script Report returns what? ├─ Just data → return columns, data ├─ Data + chart → return columns, data, None, chart ├─ Data + summary → return columns, data, None, None, report_summary ├─ Data + message → return columns, data, message └─ Everything → return columns, data, message, chart, report_summary, skip_total_row
| Fieldtype | Options Required | Notes | |-----------|-----------------|-------| | `Data` | No | Plain text | | `Link` | DocType name | Clickable link to document | | `Dynamic Link` | Fieldname holding DocType | Pair with a column containing DocType | | `Currency` | Currency field or code | Fieldname in row that holds currency | | `Float` | No | Decimal number | | `Int` | No | Integer | | `Percent` | No | Shows percentage bar | | `Date` | No | Date display | | `Datetime` | No | Date + time | | `Check` | No | Boolean checkbox | | `Select` | No | Dropdown value | | `Text` | No | Long text | | `HTML` | No | Raw HTML rendering |
| Fieldtype | Options | Behavior | |-----------|---------|----------| | `Link` | DocType name | Autocomplete from DocType | | `Select` | Newline-separated values | Dropdown with fixed options | | `Date` | — | Date picker | | `DateRange` | — | Returns `[from_date, to_date]` list | | `Check` | — | Boolean toggle | | `Dynamic Link` | Fieldname of Link filter | Depends on another filter value | | `Data` | — | Free text input | | `Int` | — | Numeric input | | `MultiSelectList` | DocType name | Multiple value selection |
chart = {
"data": {
"labels": ["Jan", "Feb", "Mar", "Apr"],
"datasets": [
{"name": _("Revenue"), "values": [100, 200, 150, 300]},
{"name": _("Expense"), "values": [80, 150, 120, 250]}
]
},
"type": "bar", # bar, line, pie, donut, percentage
"fieldtype": "Currency",
"options": "currency",
"currency": "USD",
"colors": ["#5e64ff", "#ffa00a"] # Optional custom colors
}60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations
Repo: Impertio-Studio/Frappe_Claude_Skill_Package
Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication…
Use when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files. Prevents wasted debugging time…
Use when receiving vague or unclear ERPNext/Frappe development requests that need interpretation. Transforms requirements like 'make invoice auto-calculate' or…
Use when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors. Prevents failed migrations from…
Use when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls. Checks generated code before deployment, validates against all…
Use when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting. Covers external API…