Comprehensive skill for automating Pipedrive CRM and sales pipeline management.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpipedrive-automationExecute the skills CLI command in your project's root directory to begin installation:
Fetches pipedrive-automation from claude-office-skills/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pipedrive-automation. Access via /pipedrive-automation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
54
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
54
stars
Comprehensive skill for automating Pipedrive CRM and sales pipeline management.
PIPEDRIVE PIPELINE FLOW:
┌─────────────────────────────────────────────────────────┐
│ PIPELINE VIEW │
├──────────┬──────────┬──────────┬──────────┬────────────┤
│ Lead │ Contact │ Proposal │ Negoti- │ Won/ │
│ In │ Made │ Sent │ ation │ Lost │
├──────────┼──────────┼──────────┼──────────┼────────────┤
│ $15,000 │ $45,000 │ $80,000 │ $35,000 │ $125,000 │
│ 5 deals │ 8 deals │ 6 deals │ 3 deals │ 12 deals │
├──────────┼──────────┼──────────┼──────────┼────────────┤
│ ┌──────┐ │ ┌──────┐ │ ┌──────┐ │ ┌──────┐ │ │
│ │Acme │ │ │Tech │ │ │StartX│ │ │BigCo │ │ │
│ │$5,000│ │ │$12K │ │ │$25K │ │ │$20K │ │ │
│ └──────┘ │ └──────┘ │ └──────┘ │ └──────┘ │ │
└──────────┴──────────┴──────────┴──────────┴────────────┘
automations:
- name: new_deal_setup
trigger:
type: deal_created
actions:
- create_activity:
type: call
subject: "Initial discovery call"
due_days: 1
- send_email:
template: welcome_sequence
- add_label: "New"
- name: stage_progression
trigger:
type: deal_stage_changed
to_stage: "Proposal Sent"
actions:
- create_activity:
type: task
subject: "Follow up on proposal"
due_days: 3
- update_custom_field:
field: "Proposal Date"
value: "{{today}}"
- name: stale_deal_alert
trigger:
type: deal_rotting
days: 14
actions:
- send_notification:
to: owner
message: "Deal hasn't moved in 14 days"
- add_label: "At Risk"
deal_structure:
required_fields:
- title
- value
- organization
- stage
- owner
custom_fields:
- name: "Lead Source"
type: enum
options:
- "Inbound - Website"
- "Inbound - Referral"
- "Outbound - Cold"
- "Event"
- "Partner"
- name: "Product Interest"
type: set
options:
- "Product A"
- "Product B"
- "Services"
- name: "Decision Timeline"
type: enum
options:
- "< 1 month"
- "1-3 months"
- "3-6 months"
- "6+ months"
- name: "Proposal Amount"
type: monetary
- name: "Close Probability"
type: numeric
format: percentage
pipeline_config:
name: "Sales Pipeline"
stages:
- name: "Lead In"
probability: 10%
rotting_days: 7
- name: "Contact Made"
probability: 20%
rotting_days: 10
- name: "Needs Defined"
probability: 40%
rotting_days: 14
- name: "Proposal Sent"
probability: 60%
rotting_days: 14
- name: "Negotiation"
probability: 80%
rotting_days: 7
- name: "Won"
probability: 100%
- name: "Lost"
probability: 0%
activity_types:
- name: "Call"
icon: phone
default_duration: 15
- name: "Meeting"
icon: calendar
default_duration: 60
- name: "Email"
icon: mail
default_duration: 5
- name: "Task"
icon: checkbox
default_duration: 30
- name: "Demo"
icon: presentation
default_duration: 45
activity_workflows:
discovery_call_complete:
trigger:
activity_type: call
marked_done: true
deal_stage: "Lead In"
actions:
- move_deal_stage: "Contact Made"
- create_activity:
type: task
subject: "Send follow-up email"
due_days: 1
- update_deal:
custom_field: "First Contact Date"
value: "{{activity.done_time}}"
meeting_scheduled:
trigger:
activity_type: meeting
created: true
actions:
- send_email:
template: meeting_confirmation
to: "{{deal.contact}}"
- create_activity:
type: task
subject: "Prepare meeting agenda"
due_before_meeting: 1_day
email_templates:
- name: "Initial Outreach"
subject: "{{company}} + {{prospect_company}}"
body: |
Hi {{first_name}},
I noticed {Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in pipedrive-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: pipedrive-automation is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for pipedrive-automation matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend pipedrive-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: pipedrive-automation is focused, and the summary matches what you get after install.
Keeps context tight: pipedrive-automation is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend pipedrive-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
pipedrive-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for pipedrive-automation matched our evaluation — installs cleanly and behaves as described in the markdown.
pipedrive-automation has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 72