CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/close-automation/SKILL.md

The canonical home for this skill is close-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

A well-structured, actionable single-file skill with concrete tool guidance and clear setup validation, weakened by redundant pitfall sections, a boilerplate closing line, and missing validation on the destructive delete workflow.

Suggestions

Add an explicit validation/confirmation step to the Delete Activities workflow (e.g., confirm the call_id and warn before irreversible deletion) so destructive operations have a checkpoint.

De-duplicate the per-workflow 'Pitfalls' against the consolidated 'Known Pitfalls' section and remove the boilerplate 'When to Use' sentence to tighten conciseness.

Consider extracting the ID-format and rate-limit reference material into a references/ file so the body stays a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific content, but per-workflow 'Pitfalls' sections overlap the consolidated 'Known Pitfalls' section, and the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') is boilerplate padding.

3 / 5

Actionability

Provides concrete tool slugs (e.g., CLOSE_CREATE_LEAD), key parameters, and ID formats; no executable call examples, but the dynamic-schema constraint ('Always call RUBE_SEARCH_TOOLS first') justifies that gap, fitting anchor 4.

4 / 5

Workflow Clarity

Setup includes a validation checkpoint ('Confirm connection status shows ACTIVE'), but the destructive Delete Activities workflow has no confirm/validate step despite flagging 'Deletion is permanent,' so workflow clarity is capped at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

No bundle files exist and the ~207-line body is organized into clearly labeled sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference), fitting anchor 4 with minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description that clearly names the domain and several concrete actions with low conflict risk, but it omits an explicit 'when to use' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user wants to manage Close CRM leads, log calls/SMS, or track tasks and notes').

Expand the action list to cover more of Close's surface (email, opportunities, lead search) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the Close CRM domain and several concrete actions ('create leads, manage calls/SMS, handle tasks, and track notes'), matching anchor 4; not 5 because coverage is not comprehensive (no email/opportunity/deal actions).

4 / 5

Completeness

Has a clear 'what' (automate Close CRM tasks via Rube MCP with named actions) but no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural user-facing terms ('Close CRM', 'leads', 'calls/SMS', 'tasks', 'notes') with good coverage, but lacks synonym variants that would reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Close CRM automation via Rube MCP/Composio) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.