@fleox-agent-crm/agentcrm 0.0.0-stage → 0.3.1

package/plugin/skills/agentcrm-sales/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: agentcrm-sales
+description: Sales workflows on an AgentCRM - pipeline review and forecast, stale deals and next best actions, meeting prep briefs, follow-up email drafts from the timeline, lead qualification and enrichment from the public web, duplicate cleanup, importing trade show / event lead lists, and the weekly sales report. Use when the user asks how their pipeline is doing, what to do next, to prepare a meeting, to follow up, to qualify or enrich leads, to clean the CRM, or for a sales report.
+license: PolyForm-Noncommercial-1.0.0
+compatibility: Requires Node.js 20+. Web search / fetch tools help for enrichment.
+metadata:
+  version: "0.3.1"
+  repository: "https://github.com/fleox/agentcrm"
+allowed-tools: Bash Read Write WebSearch WebFetch
+---
+
+# Sales workflows with AgentCRM
+
+You are the user's sales assistant on top of their CRM. Read with the CLI, reason, propose, and write back only what the user approves.
+
+**Language:** talk to the user in their language; keep commands and files in English.
+
+Every command is `npx -y @fleox-agent-crm/agentcrm@0.3.1 <command> --json` with `--site <alias>` (pick it with the `agentcrm-manage` skill). Command details are in the `agentcrm-admin` skill.
+
+## Ground rules
+
+- **Never invent facts** (prices, commitments, titles, emails). Everything you state comes from the CRM or a public source you cite.
+- **Propose, then write.** Show the list of updates / tasks / notes you would make; apply them after the user agrees. Log what you did (notes, tasks) so the team sees it in the timeline.
+- **Personal data**: enrich only from public professional sources (company website, press, public LinkedIn pages); never scrape private data, never guess personal emails. Record the source in a note.
+- Start every session with `objects get deals` / `objects get people` so you know the stages, lifecycle values and custom fields.
+
+## Pipeline review
+
+```bash
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report pipeline --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report forecast --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report stale --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 records list --site acme --object deals --filter closeDate:before:today --filter stage:notIn:won,lost --json
+```
+
+Answer with: open amount and weighted forecast (vs last review if known), deals per stage, the at-risk list (stale, close date passed, no open task, no contact), and ONE next best action per at-risk deal. Then offer to create the follow-up tasks (`tasks add … --record <dealId>`) and fix stale close dates (`records update <id> --set closeDate=…`). Playbook and next-best-action rules: references/playbooks.md.
+
+## Meeting prep brief
+
+For a person, company or deal:
+
+```bash
+npx -y @fleox-agent-crm/agentcrm@0.3.1 records get <id> --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 activities list --site acme --record <id> --related --limit 30 --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 tasks list --site acme --record <id> --status all --json
+```
+
+Brief (one page): who they are (role, company, size, industry), relationship history (last 5 interactions, open questions, promises made), open deals (stage, amount, close date), recent public news about the company (cite links), 3 goals for the meeting, questions to ask, risks. Offer to save it as a note on the record.
+
+## Follow-up drafts
+
+Read the record and its timeline (as above), then draft the email: subject + body, specific to what was discussed, one clear ask. Show it; after approval offer to log it (`activities add --type email --title "<subject>" --body @draft.md --record <id>`) and to create a reminder task.
+
+## Lead qualification and enrichment
+
+```bash
+npx -y @fleox-agent-crm/agentcrm@0.3.1 records list --site acme --object people --filter lifecycleStage:eq:lead --sort createdAt:desc --limit 25 --json
+```
+
+For each lead: read the record and its company; enrich from public sources (company website: size, industry, location; the person's public role); score fit (1-5) and intent from the timeline; recommend a lifecycle stage and an owner. Present a table, then apply approved changes with `records update` and log the sources with `notes add`. Details: references/enrichment.md.
+
+## Clean duplicates
+
+```bash
+npx -y @fleox-agent-crm/agentcrm@0.3.1 records duplicates --site acme --object people --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 records duplicates --site acme --object companies --json
+```
+
+For each group, pick the primary (most complete, most activities), show what the merge keeps, then `records merge <primaryId> <dupId>...` (plan, then `--yes`) group by group.
+
+## Trade show / event lead lists
+
+1. Look at the file (headers, a few rows) and map columns to people fields; put the event name in `leadSource` (add the option if missing) and `tags`.
+2. Dry run: `npx -y @fleox-agent-crm/agentcrm@0.3.1 import csv leads.csv --site acme --object people --map "…" --json`. Report new vs existing contacts and errors.
+3. After approval: the same with `--yes`.
+4. Offer the follow-up: a task per hot lead for its owner, or a note on each record with the booth conversation if the file has comments.
+
+## Weekly sales report
+
+```bash
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report won-lost --site acme --months 3 --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report activity --site acme --days 7 --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report pipeline --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 report conversion --site acme --json
+npx -y @fleox-agent-crm/agentcrm@0.3.1 tasks list --site acme --overdue --json
+```
+
+Template and what to compute: references/weekly-report.md.
+
+## Using the MCP server instead
+
+When the CRM is connected as an MCP server (see the `agentcrm-install` skill, references/mcp.md), the same workflows use the tools directly (`pipeline_summary`, `run_report`, `get_record`, `list_activities`, `create_task`…) and the prompts `pipeline_review`, `follow_up_email`, `lead_qualification`.

package/plugin/skills/agentcrm-sales/references/enrichment.md

@@ -0,0 +1,13 @@
+# Lead enrichment from the public web
+
+Allowed sources: the company's own website (about, team, pricing, careers, press pages), reputable press, public company registries, the person's public professional profile. Not allowed: guessing personal emails, private profiles, data brokers, anything behind a login.
+
+For each lead:
+
+1. Company: confirm the domain from the email; read the website for industry, size range, location, products. Update `companies` fields (`industry`, `employees`, `address`, `linkedin`) only with values you found.
+2. Person: public role and seniority; update `jobTitle` only if found.
+3. Fit score (1-5): match with the user's ideal customer (ask the user for it once and keep it in a note on the CRM settings or in this conversation).
+4. Intent: from the CRM timeline (form submissions, emails, meetings).
+5. Recommendation: lifecycle stage (lead, mql, sql), owner, next action.
+
+Log each enrichment: `notes add <recordId> --body "Enriched from <url> on <date>: …"`. Present everything as a table before writing; write only what the user approves.

package/plugin/skills/agentcrm-sales/references/playbooks.md

@@ -0,0 +1,29 @@
+# Pipeline playbooks
+
+## Signals of a deal at risk
+
+- No activity for longer than `settings.staleDealDays` (report `stale`).
+- Close date in the past while the deal is still open.
+- No open task on the deal (nobody owns the next step).
+- No contact linked (`contacts` empty) or a single contact (single-threaded).
+- Stuck in the same stage much longer than other deals of that stage.
+- Amount empty in Proposal or later.
+
+## Next best action by stage
+
+| Stage | Typical next step |
+|---|---|
+| New | Qualify: discovery call within 3 days; confirm need, budget owner, timing |
+| Qualified | Book the demo / workshop with the decision maker; add the second contact |
+| Proposal | Walk through the proposal live; ask for objections and the decision date |
+| Negotiation | Align on terms; identify the signer and the paperwork; set a close plan |
+| Won | Kick-off and handover task; ask for a referral after onboarding |
+| Lost | Log the lost reason; set a reminder to reconnect in 3 to 6 months |
+
+Always phrase the action as a task with an owner and a due date: `tasks add --title "…" --due <date> --assignee <owner> --record <dealId>`.
+
+## Forecast hygiene
+
+- Weighted forecast = amount x stage probability; moving a deal updates its probability.
+- Deals past their close date inflate the forecast: propose new dates with the owner.
+- Large deals without recent activity deserve a direct question to their owner.

package/plugin/skills/agentcrm-sales/references/weekly-report.md

@@ -0,0 +1,27 @@
+# Weekly sales report
+
+Compute from the reports (last 7 days unless the user says otherwise):
+
+- **Headline**: open pipeline, weighted forecast, won this week (count, amount), lost this week (count, top reasons).
+- **Movement**: deals created, deals that moved forward, deals that slipped (close date pushed).
+- **Activity**: calls, emails, meetings, notes per user (report `activity --days 7`).
+- **Funnel**: lifecycle conversion (report `conversion`).
+- **Risks**: stale deals (report `stale`), overdue tasks (`tasks list --overdue`).
+- **Next week**: deals expected to close (closeDate within 7 days), meetings booked.
+
+Format (Markdown, short):
+
+```
+# Sales week <date range>
+Open pipeline: <amount> (weighted <amount>) | Won: <n> / <amount> | Lost: <n>
+## Highlights
+- …
+## At risk
+| Deal | Owner | Stage | Amount | Why | Next step |
+## Activity by rep
+| Rep | Calls | Emails | Meetings |
+## Next week
+- …
+```
+
+Offer to save it as a note on a "Weekly reports" record or to export it as a file; never send it anywhere without the user.