etkm-crm-operations

Name: etkm-crm-operations
Availability: InStock
Author: easttxkravmaga

Govern CRM pipeline, label, and automation decisions for Pipedrive.

Updated Feb 20, 2026

Search Tags:#automation #workflow #crm #notion #pipedrive #arc-classification

Ready to run

npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-crm-operations

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing and governance for ETKM CRM and automation, unifying Pipedrive pipelines, stages, labels, and automation logic under a single, consistent standard.

Core Features & Use Cases

Routing brain for all ETKM CRM and automation work, including pipelines, stages, labels, automation triggers, and data references stored in Notion.
Defines clear decision logic for deal transitions, arc classification, and cross-tool integrations (n8n, Calendly, Claude-Manus API).
Enforces governance rules and clear handoffs between Claude and Manus to prevent drift and ensure compliance with the CRM blueprint.
Use Case: Plan and troubleshoot a new pipeline or remediation of divergent stage logic with a single source of truth.

Quick Start

Load this skill when planning or troubleshooting ETKM Pipedrive pipelines, labels, and automation to align Claude with the CRM architecture.

Frequently Asked Questions about etkm-crm-operations

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

FAQPage Schema

How do I unify Pipedrive pipeline stages and automation triggers under a single governance standard?▼

Unifying Pipedrive pipeline stages and automation triggers requires a central routing brain that defines clear decision logic for deal transitions and enforces governance rules to prevent workflow drift across integrated tools.

What is the best way to troubleshoot divergent CRM stage logic and pipeline remediation?▼

Troubleshooting divergent CRM stage logic and pipeline remediation involves aligning your automation architecture against a single source of truth that defines atomic belt label operations and governs cross-tool integration mappings.

Can I use Notion data as a source of truth for Pipedrive pipeline architecture references?▼

Yes, you can use Notion data as a source of truth for Pipedrive pipeline architecture references by defining Notion-sourced CRM architecture references within your routing brain to replace legacy components and enforce governance.

How do I govern handoffs between Claude and Manus for cross-tool CRM automation?▼

Governing handoffs between Claude and Manus for cross-tool CRM automation requires enforcing clear governance rules and handoff protocols that prevent drift and ensure compliance with the defined CRM blueprint.

Does this approach support arc classification and deal transitions for n8n and Calendly integrations?▼

Yes, this approach supports arc classification and deal transitions by defining clear decision logic for cross-tool integrations including n8n, Calendly, and Notion data to orchestrate your CRM automation workflow.