CRM Engine

Full CRM with accounts, leads, deals, contacts, pipelines, and work orders — built for AI agents.

This skill appears to be a legitimate API-driven CRM, but there are important unknowns you should resolve before enabling it: - Gateway trust: the skill points to https://gateway.mcfagentic.com. Verify the operator, privacy policy, and SLA. Do not send real customer data until you trust the endpoint. - Payment flow: the SKILL.md says calls require x402 (USDC on Base). Ask the author for explicit instructions: smart contract addresses, how to include payment in requests, and whether the skill will ever ask for private keys or wallet seed phrases. Never provide private keys or seed phrases to the agent or skill. - Test with limits: if you enable it, run tests with synthetic data and the smallest possible payment or a sandbox environment. Monitor and limit spend (rate limits, daily caps) if possible. - Restrict autonomy: consider disabling autonomous invocation or require explicit user approval for actions that may incur cost. Log and review every outbound call until you’re confident. - Data protection: the skill will send PII (contacts, emails) to the external gateway; ensure this is acceptable under your privacy/compliance rules. If the vendor cannot clearly document the payment/auth flow and provide verifiable identity for the gateway, treat the integration as high risk and avoid enabling it for production data.

Type: OpenClaw Skill Name: mcf-crm-engine Version: 1.0.0 The skill bundle provides documentation and metadata for a CRM API (mcf-crm-engine) designed for AI agents. It defines standard CRM operations such as managing accounts, leads, and deals via a payment-gated API (gateway.mcfagentic.com). No executable code is present, and the instructions in SKILL.md are strictly functional and aligned with the stated purpose without any signs of prompt injection or malicious intent.