close-automation
Automate Close CRM Workflows
Sales teams lose time switching between CRM tasks and tool schemas. This skill guides Close CRM actions through Rube MCP with current schemas and safer ID handling.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "close-automation" from https://skillstore.io/skills/sickn33-close-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-close-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "close-automation". Create a lead for Acme with two contacts and a qualified status.
Expected outcome:
The assistant checks the current schema, asks for missing fields, then creates the Close lead with contacts and status.
Using "close-automation". Log a completed outbound call and create a follow-up task for tomorrow.
Expected outcome:
The assistant records the call details on the correct lead and creates a dated follow-up task for the assigned user.
Using "close-automation". Delete the duplicate call record with this call ID.
Expected outcome:
The assistant verifies the call ID, explains that deletion is permanent, and waits for explicit approval before deleting it.
Security Audit
Medium RiskMost static external command and system reconnaissance findings are false positives from Markdown formatting, Close tool names, and CRM identifiers. The real risks are the disclosed Rube MCP network dependency and business workflows that can send SMS messages or permanently delete call records.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (40)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-close-automation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-close-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-close-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-close-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-close-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). close-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-close-automation/audits/4BibTeX citation
@techreport{sickn33-sickn33-close-automation-2026,
author = {sickn33},
title = {close-automation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-close-automation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "close-automation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/sickn33-close-automation/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-close-automation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create Sales Leads
Create company leads with contact details, custom fields, and correct status IDs after checking the current tool schema.
Log Outreach Activity
Record calls, SMS messages, notes, and follow-up tasks against the correct Close lead and contact.
Maintain CRM Data Quality
Resolve Close object IDs, avoid common data model errors, and remove incorrect call records with approval.
Try These Prompts
Search the Rube Close tools first. Create a Close lead for this company with these contacts, status, and custom fields.
Find the correct lead and contact IDs. Log this outbound call with the status, duration, notes, and any follow-up task.
Confirm the recipient and message text with me. Then send or log the SMS in Close and create a follow-up task.
Resolve the lead, contact, note, and call IDs. Identify the incorrect call record and ask for confirmation before deletion.
Best Practices
- Search Rube tools before each workflow to confirm current schemas.
- Verify lead, contact, note, and call IDs before changing CRM data.
- Request explicit approval before outbound SMS messages or permanent deletion.
Avoid
- Creating leads before checking for duplicates in Close.
- Using display names where Close requires API IDs.
- Sending SMS messages or deleting calls without user confirmation.