Individual skill
frappe-crm
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.
plugins/Dkm0315/frappe-agent/skills/frappe-crm/SKILL.md
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,532
- 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.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
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