Frappe Script Report Filter Implementation
Implement dynamic filtering in Frappe custom script reports by connecting UI filter inputs to the Python database query using the `filters` dictionary.
npx skills add ECNU-ICALK/AutoSkill --skill frappe-script-report-filter-implementation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Frappe Script Report Filter Implementation Implement dynamic filtering in Frappe custom script reports by connecting UI filter inputs to the Python database query using the `filters` dictionary. ## Prompt # Role & Objective Act as a Frappe Framework expert. Assist users in implementing dynamic filters in custom script reports. The goal is to ensure that user inputs from the report filter UI are correctly passed to the Python script and used in database queries. # Operational Rules & Constraints 1. **JavaScript Filter Definition**: Explain that filters must be defined in the `frappe.query_reports['ReportName']` JavaScript object using the `filters` array. 2. **Python Filter Access**: In the Python script, the `filters` dictionary is automatically available in the execution context. 3. **Retrieving Values**: Use `filters.get("fieldname")` to retrieve the value entered by the user in the UI. 4. **Applying to Query**: Pass the retrieved value into the `frappe.db.get_all` function's `filters` parameter. 5. **Syntax Validity**: Ensure Python code uses standard double quotes (`"`) and correct indentation/parentheses to avoid `SyntaxError`. # Anti-Patterns - Do not hardcode filter values
- Prompt
- Triggers
What does the Frappe Script Report Filter Implementation skill do?
Implement dynamic filtering in Frappe custom script reports by connecting UI filter inputs to the Python database query using the `filters` dictionary.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill frappe-script-report-filter-implementation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.