LubusIN Frappe Skills
14 Frappe skills for DocTypes, APIs, Desk UI, Vue frontends, reports and tests, so the agent stops writing outdated patterns
- 69 ★ on the repository
- Last commit
Minimal access
Why this level
- The skills are plain text instructions and run nothing on their own
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/lubusin-frappe-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills are plain text instructions and run nothing on their own
This is third-party code. Review the repository files before installing.
What it does
The repository holds 14 skills for the Frappe framework. The `router` skill picks the right skill for a task, and `project-triage` first finds out the Frappe version, installed apps and project tooling. The rest cover custom apps with hooks and background jobs, DocTypes and controllers, REST and RPC APIs with permission checks, Desk customization, Vue 3 frontends on Frappe UI, print formats, reports, web forms, tests and Frappe Manager environments. Every skill follows one layout: when to use it, required inputs, a step-by-step procedure, verification, common failures and when to check the docs. Detail lives in `references/` folders, so the main file stays short. The authors say the draft was prepared with GPT-5.3 Codex from the official documentation and then reviewed by people.
Who it is for. Frappe and ERPNext developers who use Claude Code, Cursor or Codex and are tired of correcting outdated patterns in generated code.
Good fit when
- Your agent suggests pre-v13 Frappe patterns or skips permission checks in an API handler
- You need a new DocType with a controller and child tables and want the agent to follow the standard structure
- A Vue 3 frontend on Frappe UI is built from scratch with CRM, Helpdesk and HRMS as the reference
- A report needs a choice between Report Builder, an SQL query and a Script Report
- A local dev environment is brought up through Frappe Manager in Docker
Not a fit when
- The project does not use Frappe: the skills are entirely about its API and app structure
- You need live work against a Frappe site through tools: the Frappe Assistant Core MCP server fits that
- You want official skills from the Frappe team itself, published in a separate card
Example request
Install the lubusIN/frappe-skills skills and create a Request DocType with a child items table and permission checks in the APILimitations
The skills describe patterns for current Frappe versions, and advice may not fit older releases. Scope depends on how many skills you copied: `npx skills add` installs all of them, the `--skills` flag picks a subset. The author notes that the text was drafted by a model and then reviewed by people, so debatable points are worth checking against the Frappe docs. The skills only supply instructions and run nothing themselves, but the agent will execute the commands they suggest on your machine.
How to disable. Delete the skill folders from `~/.claude/skills/` or the project `.claude/skills/`. For Cursor the path is `~/.cursor/skills/`.
FAQ
How do I install the Frappe skills in Claude Code?
Run `npx skills add lubusIN/frappe-skills` in the project folder, or with `-g` for all projects. You can also clone the repository and copy the folders you need into `~/.claude/skills/`.
Can I install only some of the skills?
Yes. The flag `--skills=doctype-development,api-development` picks exactly those two. In a manual install you copy only the folders you want.
What works with the skills besides Claude Code?
Any agent that reads skills in the Agent Skills format. The README gives paths for Cursor and a generic recipe for the rest.
What does the project-triage skill do?
It collects project facts before any work starts: project type, Frappe version, installed apps and tooling. The other skills rely on that result.
How is this set different from the official Frappe skills?
It is a separate lubusIN project with 14 skills that carry a procedure, verification and failure modes. The official set lives in frappe/skills and has its own card.
Discussion
No questions or reviews yet.
Related
SkillsA set from the Frappe team: building apps on the framework, code review, security audit and getting a PR ready to merge
61 skills that teach Claude to write and run Frappe and ERPNext code for versions 14 to 16, from scripts to deployment.
15 skills for Claude Code and Codex: Laravel, Docker, UI, debugging, tests and docs in four ready plugin bundles
my-skills by akitaonrails
akitaonrails my-skills
Fabio Akita's personal set of 24 skills for Claude Code, Codex and opencode: releases, PR audits, security and fact-checking
Brooklyn skills: 25 portable agent skills for pull requests, triage, cleanup, UI checks and research
A set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| LubusIN Frappe Skills (this card) | no | 69 | ||
| Frappe Skills | yes | 166 | the official set from the Frappe team, while this is a separate lubusIN project with a procedure and verification in each skill | |
| Frappe Assistant Core | no | OAuth | 337 | an MCP server for live work against a Frappe site, while this holds knowledge and procedures only |
README in short
The front page lists 14 skills in four groups: core, development, UI with reports, and infrastructure with enterprise patterns. Next come two install paths and a description of the skill layout. The page closes with credits to WordPress Agent Skills and the Agent Skills specification.
README badge
Original SKILL.md
--- name: router description: Route to the appropriate Frappe skill based on task type. Use as the entry point when working on Frappe projects to determine which specialized skill to apply. --- # Frappe Router Route to the appropriate Frappe skill based on your task. ## When to use - First step when starting any Frappe-related work - To determine which specialized skill applies to your task ## Procedure ### 0) Identify task type | Task | Skill | |------|-------| | Understand project structure, versions, apps | → `project-triage` | | Scaffold new app, hooks, architecture, background jobs | → `app-development` | | Create/modify DocTypes, fields, controllers | → `doctype-development` | | Build REST/RPC APIs, webhooks, integrations | → `api-development` | | Customize Desk UI, form scripts, list views, JS API | → `desk-customization` | | Build Vue 3 frontends with Frappe UI, portals | → `frontend-development` | | UI/UX patterns from CRM/Helpdesk/HRMS | → `ui-patterns` | | Create print formats, email templates, Jinja, PDFs | → `printing-templates` | | Build reports (Builder, Query, Script) | → `reports` | | Create public web forms for data collection | → `web-forms` | | Write or run tests | → `testing` | | Set up dev environment with Docker/FM | → `frappe-manager` | | Build CRM/Helpdesk/enterprise systems | → `enterprise-patterns` | ### 1) Run triage first (recommended) Before deep work, run `project-triage` to understand: - Project type (bench/FM/standalone) - Frappe version - Installed apps - Available tooling ### 2) Combine skills as needed Complex tasks may require multiple skills: