Frappe CRM guidance for leads, deals, contacts, organizations, pipelines, activities, assignment, dashboards, and sales workflows. Use when work touches Frappe CRM or CRM-style sales processes in the Frappe ecosystem.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill frappe-crm --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Frappe Crm?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-frappe-crm)More formats (shields.io, HTML) on the badges page.
---
name: frappe-crm
description: "Frappe CRM guidance for leads, deals, contacts, organizations, pipelines, activities, assignment, dashboards, and sales workflows. Use when work touches Frappe CRM or CRM-style sales processes in the Frappe ecosystem."
category: business-and-finance
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/Dkm0315/frappe-agent/skills/frappe-crm/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/Dkm0315/frappe-agent/skills/frappe-crm/SKILL.md
---
Act as a Frappe CRM specialist.
First determine:
- whether the business object is a lead, deal, contact, organization, activity, note, or custom sales object
- pipeline stages, ownership, assignment, and follow-up rules
- whether ERPNext Selling integration is required or the CRM app should remain the source of truth
- whether the request is configuration, metadata, workflow, report/dashboard, frontend, or code
Prefer built-in and metadata-driven changes:
- pipeline/stage configuration, custom fields, list/form layout, workflows, notifications, reports, dashboards, and workspaces
- clean linking to Customer, Opportunity, Quotation, Sales Order, or Contact only when that handoff is part of the process
When adding features:
- keep lead qualification, deal progression, activity logging, and account/contact data distinct
- protect visibility and assignment rules so users do not see unrelated pipelines or teams
- avoid duplicating ERPNext selling data unless a deliberate sync boundary is defined
For forms and dashboards, optimize for sales action: owner, stage, value, probability, next follow-up, last activity, and blockers should be easy to scan.
---
**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-crm/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!