{"id":87677,"plugin_id":"plugin_asdk_app_6ac768a541148191adc9588132f9f44c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T18:08:40.620Z","digest":"0c81ed0667b223c0f4ebafa3bbd44a89737fd7cdc0ecd0f1f80bfeee4b9a379d","against":null,"payload":{"description":"Review Captino leads and contacts - list new or recent leads, search a contact by name, email or phone, see which funnel a lead came from, their opt-ins, activity and meetings, and pipeline counts per status. Use when the user asks \"any new leads\", \"who signed up this week\", \"show my leads\", \"find contact X\", \"what did this lead do\", \"where did this lead come from\", or \"how many leads, opportunities or customers do I have\".","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":453}],"name":"leads","skill_md_contents":"---\nname: leads\ndescription: Review Captino leads and contacts - list new or recent leads, search a contact by name, email or phone, see which funnel a lead came from, their opt-ins, activity and meetings, and pipeline counts per status. Use when the user asks \"any new leads\", \"who signed up this week\", \"show my leads\", \"find contact X\", \"what did this lead do\", \"where did this lead come from\", or \"how many leads, opportunities or customers do I have\".\n---\n\n# Leads\n\nRead-only review of leads and contacts from the Captino MCP server. To change\na lead (status, value, note, meeting) use the `lead-followup` skill.\n\n## Prerequisites\n\nUses the Captino MCP tools `list_leads`, `list_contacts`, `get_contact`,\n`get_contact_activity`, `list_contact_opt_ins`, `get_contact_pipeline_stats`\nand `get_contact_options`. Needs **Contact: read** access, granted when\nconnecting Captino. If the tools are missing or fail with 401/403, run the\n`captino-setup` skill.\n\n## Domain facts\n\n- Pipeline `status` progression: `Contact` (captured from an opt-in) →\n  `Lead` (submitted a form or was promoted) → `Opportunity` (deal under\n  negotiation) → `Customer` (closed). `Lost` means they left the process.\n  So \"leads\" in the narrow sense is `status = Lead`; \"everyone who signed up\"\n  is all statuses. Ask or state which one you used when it matters.\n- `qualityStatus`: `Pending` (not reviewed), `Good`, `NotRelevant`, `Spam`.\n- Lists are paged: `page` (1-based) and `itemsPerPage` (max 100). Responses\n  include `hasNextPage` and `totalPages`.\n- Contacts beyond the subscription limit are hidden. When a response has\n  `hiddenContacts > 0`, always tell the user how many are hidden and that\n  upgrading the plan reveals them.\n- There is no server-side date filter. For \"this week\" or \"since Monday\",\n  order by `createdAt` descending and stop paging once `createdAt` is older\n  than the cutoff.\n\n## Workflow\n\n### New or recent leads\n\n1. Call `list_leads` (or `list_contacts` with `status` if the user means\n   another stage) with `itemsPerPage: 50`. `list_leads` is newest first.\n   For `list_contacts` pass `orderBy: \"createdAt\"`, `descending: true`.\n2. Filter by the cutoff date locally. Page further only while the last item is\n   still inside the period.\n3. Present a table: name, email, status, quality, created (date only),\n   deal value if non-zero. Group by day if there are more than ~15.\n4. If the user wants the source funnel for each lead, call\n   `list_contact_opt_ins` per lead (this is one call per contact, so do it\n   for at most ~10 leads unless asked) and add a \"Source funnel\" column.\n\n### Find a contact\n\n1. `list_contacts` with `query` set to the name, email or phone fragment.\n2. If exactly one result, call `get_contact` for full details. If several,\n   show them and ask which one.\n\n### What did this lead do\n\n1. Resolve the contact as above.\n2. `get_contact_activity` returns `funnelActivities` (per funnel: visits,\n   opt-ins, form submissions with timestamps), `meetings` and `lastActivity`.\n3. `list_contact_opt_ins` returns each form sign-up with `funnelName`,\n   `funnelStepId`, `acceptedTerms`, `timeZone`, `createdAt`.\n4. Summarise as a short timeline: first seen, funnels touched, forms submitted,\n   meetings held or scheduled, last activity. Note if `acceptedTerms` is false.\n\n### Pipeline counts\n\nCall `get_contact_pipeline_stats`. It returns `contacts`, `leads`,\n`opportunities`, `customers`, `lost` and `totalValue`. Present as one row per\nstage. Compute a simple win rate = `customers / (customers + lost)` only when\nboth are non-zero.\n\n## Reporting\n\nLead with the answer (\"You got 12 new leads this week, 9 from Spring Campaign\"),\nthen the table. Keep personal data to what the user needs; don't dump notes or\nphone numbers unless asked. Suggest `lead-followup` when the user's next step is\nto qualify or move a lead.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}