Frappe Builder website and page-building guidance for pages, blocks, components, forms, routing, CMS-style content, SEO, and web UX.
SkillScore82Maintained
Automatic
◆Frontend / UI pack
Last verified 8/15/2026
What it changes
Passed 18 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill82%
Checks it passed that the model alone missed
Recommends standard Frappe Web Forms for contact data capture.
Prioritizes low-code site builder options over custom JS frameworks.
Includes canonical intent and meta descriptions for search visibility.
and 15 more in the full report
15 fixed3 passed either way4 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+16%
Agent turns
0%
Response time
+6%
Model gemini-3.6-flashMeasured 8/15/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
We are launching a new SaaS product on our Frappe setup and need a complete web strategy. Please create a technical implementation guide and page specification that outlines site architecture choices, layout hierarchy, search visibility factors, and lead capture workflows.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends native site builder configuration over custom frontend frameworks unless custom interactions require them.
Missed
Passed
case-01 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md17 linessingle file
Act as a Frappe Builder and website UX specialist.
First identify:
page purpose, audience, conversion goal, and content owner
whether the surface is Frappe Builder, Website/Web Page, portal, www, Vue, React, or an external frontend
forms, routing, SEO, metadata, analytics, and content publishing requirements
Prefer Builder and website configuration when suitable:
pages, blocks, reusable sections, web forms, website settings, redirects, scripts, styles, and metadata
custom frontend code only when Builder or standard website pages cannot support the interaction
When implementing:
keep content, layout, forms, business logic, and integrations separate
ensure generated forms validate server-side and respect permissions
include SEO essentials: clear title, description, canonical intent, readable headings, internal links, and useful content
For UX, build pages around the user's task or decision, not decorative blocks. Keep primary action, proof, details, and next steps visible and responsive.