Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/frappe-agent-interpreter
Use when receiving vague or unclear ERPNext/Frappe development requests that need interpretation. Transforms requirements like 'make invoice auto-calculate' or 'add approval workflow' into concrete technical specifications. Determines which Frappe mechanisms to use and maps to the full 60-skill catalog. Keywords: vague requirement, clarify scope, translate business need, technical spec, implementation plan.
Passed 16 of 22 test cases with the skill, and 3 of 22 without it.
and 30 more in the full report
16 fixed0 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a vague request from my client: 'We need a system that prevents sales orders from being confirmed if the customer's credit limit is exceeded, and sends a notification to the accounts team.' I need you to translate this loose feature request into a complete technical spec document. Please structure your response with sections for the summary, clarified business context, an implementation details table (covering DocTypes, triggers, mechanism, and targeted version), numbered data flow steps, error handling approach, mapped frappe catalog skills needed, and validation criteria to test the solution.
| Checked | Without skill | With skill |
|---|---|---|
| Includes a markdown heading for technical specification | Passed | Passed |
| Structures implementation details using a two-column table with Aspect and Value headers | Missed | Passed |
| Lists required skills using checkbox formatting with frappe skill identifiers | Missed | Passed |
The instructions your model reads when the skill loads.
Transforms vague or incomplete Frappe/ERPNext development requests into clear, actionable technical specifications mapped to the full 60-skill catalog.
Purpose: Bridge the gap between "what the user wants" and "what needs to be built"
USER REQUEST ANALYSIS
|
+-- Request is vague/incomplete
| "Make the invoice do something when submitted"
| --> USE THIS AGENT
|
+-- Request lacks technical specifics
| "Add approval before order confirmation"
| --> USE THIS AGENT
|
+-- Multiple implementation paths possible
| "Automate inventory updates"
| --> USE THIS AGENT
|
+-- Request has clear technical specs already
| "Create Server Script on validate for Sales Invoice"
| --> Skip agent, use relevant frappe-* skills directly
STEP 1: EXTRACT INTENT
- What is the business problem?
- What should happen? When? To what data?
- Who should be affected (roles/users)?
STEP 2: IDENTIFY TRIGGER CONTEXT
- Document lifecycle event? (save/submit/cancel)
- User action? (button click, field change)
- Time-based? (daily, hourly, cron)
test cases passed, vs 3 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.