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.

1.41x

Quality

51%

Does it follow best practices?

Impact

75%

1.41x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/close-automation/SKILL.md

Quality

Discovery

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.

The description is strong in specificity and distinctiveness, clearly naming the platform (Close CRM via Rube MCP/Composio) and listing concrete actions. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms lean toward technical naming rather than natural user language.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Close CRM, managing sales leads, logging calls, sending SMS, or tracking sales activities.'

Include more natural user-facing trigger terms like 'contacts', 'deals', 'sales pipeline', 'follow-up', or 'close.com' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'create leads, manage calls/SMS, handle tasks, and track notes.' Also includes the operational guidance to 'search tools first for current schemas.'	3 / 3
Completeness	Clearly answers 'what does this do' (automate Close CRM tasks with specific actions), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain context rather than stated with trigger guidance.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Close CRM', 'leads', 'calls', 'SMS', 'tasks', 'notes', and 'Rube MCP (Composio)', but misses common user variations like 'contacts', 'deals', 'pipeline', 'follow-up', or 'close.com'. Users might not naturally say 'Rube MCP' or 'Composio'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific platform combination of 'Close CRM' and 'Rube MCP (Composio)'. This is unlikely to conflict with other skills given the narrow, well-defined niche.	3 / 3
	Total	10 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is functional but overly verbose, repeating structural patterns and information Claude already knows. It provides useful tool names and parameter lists but lacks truly executable examples — the 'code blocks' are prose, not actual invocations. The content would benefit significantly from condensation (a lean quick-reference table with a few concrete invocation examples would be more effective than the current expanded format).

Suggestions

Cut the document by at least 50%: remove 'When to use' descriptions, consolidate pitfalls into a single section, and eliminate explanations of concepts Claude already knows (e.g., ISO 8601, what rate limits are, that deletion is permanent).

Replace the prose-formatted-as-code blocks in 'Common Patterns' with actual tool invocation examples showing real parameter values (e.g., a complete RUBE_SEARCH_TOOLS call followed by CLOSE_CREATE_LEAD with sample data).

Add explicit validation/confirmation steps for destructive operations like CLOSE_DELETE_CALL (e.g., retrieve the call first to confirm it's the right one before deleting).

Consider restructuring around the quick reference table as the primary content, with brief notes on non-obvious pitfalls only (custom field ID format, lead vs contact distinction).

Dimension	Reasoning	Score
Conciseness	The skill is highly verbose and repetitive. Each workflow section follows the same template with 'When to use', 'Tool sequence', 'Key parameters', and 'Pitfalls' even when the content is trivial. Much of the information (e.g., explaining that lead_id is required, that deletion is permanent, what ISO 8601 is) is knowledge Claude already has. The 'Common Patterns' section repeats information already covered in the workflows. The document could be cut by 60%+ without losing actionable content.	1 / 3
Actionability	The skill provides tool names and parameter lists, which is somewhat concrete, but lacks executable code examples. The 'code blocks' in Common Patterns are just prose descriptions formatted as code, not actual executable commands. There are no real examples showing actual tool invocations with sample parameter values. The setup section is reasonably actionable with its numbered steps.	2 / 3
Workflow Clarity	The setup workflow has clear sequencing with a validation checkpoint (confirm ACTIVE status). However, the core workflows are mostly single-step operations presented as workflows. The delete operation (destructive) lacks any confirmation or validation step, and bulk operations mention implementing delays but provide no concrete validation pattern. Missing feedback loops for destructive operations caps this at 2.	2 / 3
Progressive Disclosure	The content is a monolithic document with no references to supporting files. All content is inline, including detailed pitfalls and patterns that could be separated. The quick reference table at the end is helpful, but the document would benefit from splitting detailed parameter documentation and pitfalls into separate reference files. However, with no bundle files provided, the single-file approach is understandable.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: davepoon/buildwithclaude
Commit: d065ead

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.