Individual skill

frappe-builder

Frappe Builder website and page-building guidance for pages, blocks, components, forms, routing, CMS-style content, SEO, and web UX. Use when work touches Frappe Builder, website pages, landing pages, or content-driven experiences.

plugins/Dkm0315/frappe-agent/skills/frappe-builder/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

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