close-automation
Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill close-automation67
Quality
58%
Does it follow best practices?
Impact
75%
1.41xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/close-automation/SKILL.mdDiscovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description effectively communicates specific capabilities for Close CRM automation with concrete actions and a clear technical context (Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause that would help Claude know exactly when to select this skill, and could benefit from additional natural trigger terms users might employ when requesting CRM help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Close CRM, sales leads, customer tracking, or CRM automation.'
Include additional natural trigger terms like 'contacts', 'sales pipeline', 'follow-ups', 'customer management', or 'CRM' without the 'Close' qualifier for broader matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create leads, manage calls/SMS, handle tasks, and track notes.' Also includes operational guidance about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Close CRM tasks with specific actions), but lacks an explicit 'Use when...' clause. The when is only implied through the domain mention. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Close CRM', 'leads', 'calls', 'SMS', 'tasks', 'notes', but missing common variations users might say like 'contacts', 'follow-ups', 'sales pipeline', or 'CRM automation'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting 'Close CRM' via 'Rube MCP (Composio)' - unlikely to conflict with other skills due to the specific platform and integration method mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid structural organization and covers the Close CRM toolkit comprehensively, but falls short on actionability by lacking executable code examples. The workflows describe what to do but don't show how with concrete API call examples. Missing validation checkpoints for destructive operations and some verbose explanations of concepts Claude already understands reduce its effectiveness.
Suggestions
Add executable code examples showing actual MCP tool calls with realistic parameters (e.g., `RUBE_SEARCH_TOOLS` with query 'close' followed by actual tool invocation syntax)
Add validation checkpoints before destructive operations like DELETE_CALL (e.g., 'Confirm call_id exists by retrieving it first, then confirm with user before deletion')
Remove explanatory content about what leads/contacts are conceptually - focus on Close-specific quirks Claude wouldn't know
Convert the pseudo-code patterns (like 'ID Resolution') into actual executable tool call sequences
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanations (e.g., explaining what leads vs contacts are, which Claude would know). The data model diagram and some pitfall explanations could be tightened. | 2 / 3 |
Actionability | Provides tool names and parameter lists, but lacks executable code examples. The 'patterns' sections use pseudo-documentation format rather than actual API calls or copy-paste ready commands. | 2 / 3 |
Workflow Clarity | Workflows are listed with clear sequences, but validation/verification steps are missing. For destructive operations like CLOSE_DELETE_CALL, there's no confirmation or validation checkpoint before execution. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but everything is in one file. Some sections (like detailed pitfalls for each workflow) could be split out, and the external toolkit docs link is good but underutilized. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.