How do I install the Push To Crm skill?

Run npx skillmds@latest add catchintent/push-to-crm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Push To Crm safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Push To Crm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Push To Crm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Push To Crm?

CatchIntent (@catchintent) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Push To Crm by catchintent — Agent Skill

Name: Push To Crm
Author: CatchIntent

Push To Crm

Push saved leads into your CRM (HubSpot, Close, Pipedrive, or Zoho), then mark them pushed. Use when the user says "push these to my CRM", "send to HubSpot", "sync saved leads", or after a triage session leaves a pile of saved leads to action.

CatchIntent c7f6132 2.1 KB Updated Sep 17, 2026

File contents

Push To CRM

You are moving saved leads into the user's CRM. Confirm scope + provider before any write — and remember the push does not change lead status on its own.

What To Do

Identify the batch — User passes leadIds, or describe the batch. If unclear:
- lead_search with status: ['saved'], page size 50 (if multi-product, scope with productId — ask which one). Saved is the natural pile to push; don't push raw NEW leads.
- Show count + a quick table (name, title @ company, warmth).
Pick the provider — lead_push_to_crm takes provider: hubspot | close | pipedrive | zoho. Ask which CRM if not specified. One provider per push.
Confirm — Show the exact list of leadIds + the provider. Wait for explicit "go". No silent pushes.
Push — lead_push_to_crm with { leadIds, provider }. This can take the whole batch at once.
Mark pushed — The push does not auto-change status. After a successful push, lead_update_status each lead to pushed so the pipeline reflects reality. Confirm this step with the user too, and note that pushed is irreversible.
Summarize — Report: pushed N leads to {provider}, marked N as pushed. Flag any that failed.

Guidelines

Saved before pushed. Push the saved pile, not unreviewed NEW leads. If the queue is full of NEW leads, point at /daily-triage first.
Status is a separate step. lead_push_to_crm syncs the contact; it does not move the lead to pushed. Always follow with lead_update_status so the funnel counts are right.
pushed is one-way. Once a lead is pushed it can't be reverted — only push leads the user has truly committed to.
Confirm scope every time. Even if the user pushed yesterday, confirm the batch and provider before spending the action today.

---name: push-to-crmdescription: Push saved leads into your CRM (HubSpot, Close, Pipedrive, or Zoho), then mark them pushed. Use when the user says "push these to my CRM", "send to HubSpot", "sync saved leads", or after a triage session leaves a pile of saved leads to action.---# Push To CRMYou are moving saved leads into the user's CRM. Confirm scope + provider before any write — and remember the push does **not** change lead status on its own.## What To Do1. **Identify the batch** — User passes leadIds, or describe the batch. If unclear: - `lead_search` with `status: ['saved']`, page size 50 (if multi-product, scope with `productId` — ask which one). Saved is the natural pile to push; don't push raw NEW leads. - Show count + a quick table (name, title @ company, warmth).2. **Pick the provider** — `lead_push_to_crm` takes `provider`: `hubspot` | `close` | `pipedrive` | `zoho`. Ask which CRM if not specified. One provider per push.3. **Confirm** — Show the exact list of leadIds + the provider. Wait for explicit "go". No silent pushes.4. **Push** — `lead_push_to_crm` with `{ leadIds, provider }`. This can take the whole batch at once.5. **Mark pushed** — The push does **not** auto-change status. After a successful push, `lead_update_status` each lead to `pushed` so the pipeline reflects reality. Confirm this step with the user too, and note that **`pushed` is irreversible**.6. **Summarize** — Report: pushed N leads to {provider}, marked N as pushed. Flag any that failed.## Guidelines- **Saved before pushed.** Push the saved pile, not unreviewed NEW leads. If the queue is full of NEW leads, point at `/daily-triage` first.- **Status is a separate step.** `lead_push_to_crm` syncs the contact; it does not move the lead to `pushed`. Always follow with `lead_update_status` so the funnel counts are right.- **`pushed` is one-way.** Once a lead is `pushed` it can't be reverted — only push leads the user has truly committed to.- **Confirm scope every time.** Even if the user pushed yesterday, confirm the batch and provider before spending the action today.

Frequently asked questions