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.
npx skills add majiayu000/claude-skill-registry --skill frappe-agent-interpreter --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 Code Interpreter Agent 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" ## When to Use This Agent ``` 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 ``` ## Interpretation Workflow ``` 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) - External event? (webhook, API call) STEP 3: DETERMINE MECHANISM - Client Scri
- When to Use This Agent
- Interpretation Workflow
- Mechanism Selection Matrix
- Clarifying Questions Framework
- 1. WHAT Questions
- 2. WHEN Questions
- 3. WHO Questions
- 4. WHERE Questions
- 5. ERROR Questions
- 6. VERSION Questions (v16 considerations)
- Output Specification Template
- Complete Skill Catalog (60 skills)
- Syntax Layer (11 skills)
- Core Layer (7 skills)
What does the frappe-agent-interpreter skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill frappe-agent-interpreter --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 majiayu000/claude-skill-registry, a repository with 534 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.