crm-operations

Name: crm-operations
Availability: InStock
Author: Saleshandy

Orchestrate gated reads and writes against Saleshandy CRM via MCP.

1|Updated Apr 28, 2026

Search Tags:#validation #crm #bulk-update #audit-log #saleshandy

Ready to run

npx skills add https://github.com/saleshandy/outreach-superpower --skill crm-operations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: crm-operations
Source: https://github.com/saleshandy/outreach-superpower/tree/main/skills/crm-operations
Command: npx skills add https://github.com/saleshandy/outreach-superpower --skill crm-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely manage Saleshandy CRM data by coordinating reads and writes with strict confirmation gates to prevent destructive changes.

Core Features & Use Cases

Bulk update prospects, enrollments, and statuses with explicit confirmations and audit logging.
Enforce per-record confirmation for destructive actions and maintain an append-only log.
Control actions across sequences to ensure compliance, data integrity, and traceability.

Quick Start

Type the initial request in plain language to trigger gated CRM operations; you will be prompted to confirm destructive actions with explicit gates and to review current state before execution.

Frequently Asked Questions about crm-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely perform bulk updates in CRM without accidental data loss?▼

Safely perform bulk CRM updates by orchestrating writes with explicit confirmation gates. The system enforces read-before-write validation and per-record confirmation for destructive actions to prevent accidental data loss.

What is the best way to manage sequence enrollments and DNC actions for prospects?▼

Manage sequence enrollments and DNC actions by triggering gated CRM operations through plain language requests. The workflow applies safeguards to large operations, ensuring compliance and data integrity across one or many prospects.

How does the audit trail work for CRM status changes and deletions?▼

The audit trail works by appending every executed CRM status change and deletion to an append-only log file named crm-actions.md. This maintains strict traceability and compliance for all destructive and non-destructive operations.

Do I need to review prospect data before running a bulk CRM update?▼

Yes, you must review prospect data before running a bulk CRM update because the system enforces a strict read-before-write requirement. You will be prompted to review the current state and explicitly confirm actions before execution.

Can I use plain language to trigger destructive CRM operations?▼

Yes, you can type initial requests in plain language to trigger destructive CRM operations like deletions and DNC actions. The system automatically applies explicit approval gates, requiring your confirmation before executing any irreversible changes.

What are the limitations when managing large prospect operations across sequences?▼

When managing large prospect operations across sequences, limitations include mandatory per-record confirmations for destructive actions and enforced safeguards for large operations. These constraints prevent unapproved bulk changes and ensure data integrity.