CtrlK
BlogDocsLog inGet started
Tessl Logo

hubspot-automation

Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.

83

1.37x
Quality

76%

Does it follow best practices?

Impact

96%

1.37x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/hubspot-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The content is well-structured, actionable, and concise with strong per-workflow sequencing and validation cues. Main improvement is deduplicating pitfalls and adding explicit validate→fix→retry loops for batch/destructive operations.

Suggestions

Consolidate the per-workflow 'Pitfalls' into the 'Known Pitfalls' section (or vice versa) to remove repetition and tighten conciseness.

Add an explicit validate→fix→retry loop for batch and custom-property creation workflows to push workflow clarity toward 5.

Promote a couple of the tool-sequence examples into copy-paste-ready parameter snippets to lift actionability.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's knowledge — no padding about what HubSpot or CRM is — though the 'Known Pitfalls' section repeats pitfalls already listed per workflow, a minor trim opportunity.

4 / 5

Actionability

Concrete tool slugs, exact parameter shapes (filterGroups, properties, inputs), and specific error conditions (400 'Property values were not valid') give mostly executable guidance, just shy of copy-paste-ready code blocks.

4 / 5

Workflow Clarity

Each workflow has a 'When to use', a numbered tool sequence tagged Prerequisite/Required/Optional, and validation cues (confirm ACTIVE before running, search-before-create, max 100 batching), with only light validate→fix→retry loops.

4 / 5

Progressive Disclosure

Single-file skill with no bundle files, organized into clearly labeled sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) that are easy to navigate; good structure with minor consolidation gaps.

4 / 5

Total

16

/

20

Passed

Description

77%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.

The description is specific, well-keyworded, and clearly niche, but it omits an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' sentence would lift the completeness and overall score.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user needs to create, search, or update HubSpot CRM records (contacts, companies, deals, tickets) or manage CRM properties.'

Surface a couple of discrete actions (create, search, update, batch) in the description to strengthen specificity.

DimensionReasoningScore

Specificity

Names the domain and enumerates concrete CRM objects (contacts, companies, deals, tickets, properties) plus the integration mechanism (Rube MCP, Composio), with only minor gaps in naming discrete actions like create/search/update.

4 / 5

Completeness

It clearly states the 'what' (automate HubSpot CRM operations) but lacks any explicit 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Comprehensive natural-term coverage including 'HubSpot', 'CRM', individual object names, 'Rube MCP', and 'Composio' — phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The HubSpot + Rube/Composio niche is sharply scoped with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

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
davepoon/buildwithclaude
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.