[MCP-frappe-skills] searchable Frappe skills for AI coding agents (MIT) (GitHub)

Frappe Framework
, ,
1

Hello,

Sharing a small open repo: GitHub - sbknext/forge-frappe-skill · GitHub

Why I built it:
AI coding agents work well with good context. The strongest ones (e.g. Claude Code, Codex)
handle Frappe reasonably, but most other / cheaper IDE + agent setups lose the framework
context on custom apps and generate outdated patterns — pre-v13 code, raw SQL instead of
Query Builder, missing permission checks, wrong hook usage. I wanted that Frappe knowledge
as something any agent can search + load on demand: DocTypes, controllers, hooks, Query
Builder, permissions, REST/RPC APIs, reports, testing, bench/ops.

The point is access: with these skills + free or self-hosted models (Kimi / Qwen / DeepSeek
via OpenRouter, Groq, or local), a student or a small business can build real Frappe apps
without depending on one expensive agent — near-zero API cost, and the same Frappe context
the best tools get. The direction around it: a searchable code-graph + secure-scan + test
pipeline for custom apps.

What’s in it right now:

  • ~471 granular reference skills + 11 installable core skills (plain SKILL.md / markdown)
  • Works via any MCP host or fully standalone (just the .md files — no lock-in)
  • Frappe-accurate (v13–v15): Query Builder, whitelist + permission checks, hook-based controllers

Credit — it builds on existing OSS, thanks to:

  • Impertio-Studio/frappe-skills, lubusIN/frappe-skills, the official Frappe docs, and netchampfaris, and google web scrap + claude code opus 4.8 verification

Sharing it so people can actually use it — and so it improves on its own as the community
adds and corrects skills. PRs, corrections, and missing topics welcome.

Note / tip: This repo is maintained with an AI harness in the backend, so you’ll
see frequent auto-improvements (skills getting added + corrected over time). Because of
that, treat it as evolving — not recommended for production code as-is.

Good path:
build and iterate on demo apps at any scale first; once you’re confident, point it at a
testing system to automate your tests; and eventually fold the verified pieces into prod
via server scripts, client scripts, and other customizations. Use judgement, review the
output — it’s context for your agent, not a substitute for review.

Thanks,
Sambhaji K

3 Likes
2

Hi, Did you take a look at this: GitHub - vyogotech/frappe-apps-manager: A comprehensive Claude Code plugin for Frappe Framework development, providing tools, commands, agents, and Skills to streamline your Frappe application development workflow. · GitHub?

2 Likes
3

Thanks @Varun — hadn’t seen vyogotech/frappe-apps-manager, will review it and add what’s
useful (with credit).

Also planned: v11–v16 + develop-branch coverage, so folks on legacy Frappe apps can use
these too — including clear guidance on when to use client script vs custom script vs
server script, and the cleanest way to export customizations + manage them across sites.

Appreciate the pointer :folded_hands:
also have a look at forge-frappe-skill/MISTAKES.md at main · sbknext/forge-frappe-skill · GitHub & forge-frappe-skill/PLAYBOOK.md at main · sbknext/forge-frappe-skill · GitHub

4

Thanks @kolate_sambhaji ,

The one I shared (under my org ) is loaded with lots of skills including client scripts etc.,

But mine is not having support for old frappe versions. I request you to check my skills and may be we can merge our work to have one strong repo ?

1 Like
5

Thanks @Varun — yes, went through vyogotech/frappe-apps-manager (great set, the
client-script / customization coverage is solid). I’ve started folding the net-new pieces
into forge-frappe-skill with credit to your repo (de-duped against what’s already there).

Fully agree on one strong repo — happy to merge. What I’m adding that complements yours:
v11–v16 + develop-branch coverage, so legacy-app teams are covered, plus client vs custom
vs server script decision guidance and customization export/management.

Could do it either way — you PR your skills in (kept under your attribution), or we
co-maintain and keep both in sync. Whatever’s least friction for you. Want to take it to
a quick call / GitHub issue to plan the merge?

Edit: Your skills also added here, you can review if needed skills: add 9 net-new from vyogotech + Venkatesh frappe-apps-manager … · sbknext/forge-frappe-skill@e1a9c74 · GitHub

1 Like
6

I can add you as a collaborator to my repo or merge your PR.

1 Like
7

@kolate_sambhaji @Varun

Its great to see spirit of co-operation rather than competition :+1:

2 Likes
8

@Varun i have send PR,

also there are other repository which you can try for testing
https://github.com/sbknext/forge-secure/pull/6#pullrequestreview-4458172108 this will be alternative to code review and find security related bugs using open llm.

9

Thanks buddy. Approved the PR

10

Can add codex to it as well?

11

@rijul in your /Users//.codex/rules folder you can add default rule to follow agents.md and in your project you can have agents.md to check this frappe skills (locally cloned files) whenever needed.