Skip to content

Dkm0315/frappe-agent / skills/frappe-crm

frappe-crm

Verified

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.

FileKindSize
SKILL.mdskill md1.4 KB
---
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.
---

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.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall