Frappe full-stack app builder
Build full-stack Frappe Framework apps end-to-end — DocTypes, controllers, whitelisted APIs, bench sites, desk and portal UI, background jobs, permissions, tests — with progressive-disclosure reference docs
- What
- Build full-stack Frappe Framework apps end-to-end — DocTypes, controllers, whitelisted APIs, bench sites, desk and portal UI, background jobs, permissions, tests — with progressive-disclosure reference docs
- Cost
- Free
- Needs
- a working Frappe bench environment (Frappe/ERPNext installed, at least one bench site) — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @frappe's full-stack app-builder skill for the Frappe Framework. It teaches the agent to build or extend Frappe apps end-to-end — creating apps and bench sites, defining DocTypes and fields, writing controllers and lifecycle hooks, adding whitelisted REST APIs, working with `frappe.db` / `frappe.qb`, caching, realtime, background jobs, permissions and roles, testing, and Desk/portal UI — with strict operating rules (bare `bench`, always `--site`, `bench start` in background only, never duplicate a running instance) and progressive disclosure: load only the reference file needed for the current task from `references/`. Honest caveats: guidance only — the agent needs a real Frappe bench environment (Frappe/ERPNext install) to execute anything; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Frappe full-stack app builder is a free Muse skill for building Frappe Framework apps end-to-end: apps and bench sites, DocTypes and fields, controllers and lifecycle hooks, whitelisted REST APIs, frappe.db, caching, realtime, background jobs, permissions, testing, and Desk and portal UI. Its reference docs use progressive disclosure.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit ee6e615Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a working Frappe bench environment (Frappe/ERPNext installed, at least one bench site) — the skill is guidance the agent follows, not software to install Install "Frappe full-stack app builder" for me. It gives my agent @frappe's Frappe app-builder workflow: build or extend Frappe apps end-to-end (new apps and bench sites, DocTypes and fields, controllers and lifecycle hooks, whitelisted REST APIs, frappe.db/frappe.qb, caching, realtime, background jobs, permissions and roles, testing, Desk and portal UI), with strict operating rules (bare bench command, always --site, bench start in background only) and progressive disclosure of reference docs (load only the references/ file needed for the current task). IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/frappe/skills/ee6e61537a0131c5f2b33ab27cd0155744baeb22/skills/frappe-app-dev/SKILL.md Pinned version: install the code at commit ee6e61537a0131c5f2b33ab27cd0155744baeb22 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and the references/ folder) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "frappe-app-dev". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my bench directory and site; nothing else — it's a workflow). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- ee6e615 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.