CtrlK
BlogDocsLog inGet started
Tessl Logo

hubspot-integration

Authentication for single-account integrations

33

Quality

29%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hubspot-integration/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

33%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 body is a thin scaffold of section headers and pattern names with no executable guidance and a Sharp Edges table of pure placeholders. It is well-structured for a simple skill but provides no real workflow, validation, or actionable detail.

Suggestions

Replace the placeholder Sharp Edges table with real issue/severity/solution entries (or link to a reference file) instead of 'Issue | See docs'.

Add concrete, executable guidance: example OAuth 2.0 token-exchange calls, private-app header usage, and CRM object CRUD endpoints/code samples.

Provide an explicit sequenced workflow with validation checkpoints for batch and destructive CRM operations (e.g., validate before bulk update, confirm deletions).

DimensionReasoningScore

Conciseness

The body is short and not padded with concept explanations, but the Sharp Edges table is filled with placeholder rows ('Issue | high | See docs') that earn no place; not 2 because the prose itself is lean rather than verbose.

3 / 5

Actionability

Pattern and anti-pattern names are given (OAuth 2.0, Private App Token, CRUD, batching, webhooks) but there is no code, no endpoints, no commands, and the only guidance is 'See docs'; not 1 because named patterns are concrete-ish high-level hints, but no steps are executable.

2 / 5

Workflow Clarity

There is no sequence of steps at all — only lists of patterns and anti-patterns — and the batch/destructive operations noted (batching, CRUD) have no validation checkpoints, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files and is organized into clear sections (Patterns, Anti-Patterns, Sharp Edges, When to Use); the simple-skill exception supports a high score, but the generic 'When to Use' line and placeholder table keep it from 5.

4 / 5

Total

10

/

20

Passed

Description

25%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 a terse, generic authentication label with no concrete actions, no natural trigger terms, and no 'when to use' guidance. It neither specifies what HubSpot integration does nor distinguishes the skill from other auth/integration skills.

Suggestions

Rewrite the description to name concrete HubSpot actions (e.g., OAuth 2.0 handshake, private-app token auth, CRM object CRUD) instead of the generic 'Authentication' label.

Add an explicit 'Use when ...' clause with natural trigger phrases users would say, such as 'Use when connecting to HubSpot, syncing CRM contacts/deals, or setting up HubSpot OAuth for a single account'.

Tie the description explicitly to HubSpot to reduce overlap with other integration skills.

DimensionReasoningScore

Specificity

Names the domain ('Authentication') with a minimal qualifier ('single-account integrations') but lists no concrete actions, matching the 'Names the domain but actions are minimal or generic' anchor; not 3 because it lacks even one concrete action like OAuth flows or token handling.

2 / 5

Completeness

Provides a vague 'what' ('Authentication for single-account integrations') with no 'when' / 'Use when' clause; the missing trigger guidance caps completeness at 3, and the weak 'what' pulls it to 2.

2 / 5

Trigger Term Quality

Only the generic keyword 'Authentication' appears with technical phrasing and no natural user phrases a person would say; not 1 because a recognizable term is present, but the natural trigger phrases users actually voice are missing.

2 / 5

Distinctiveness Conflict Risk

A bare authentication description is very broad and would overlap with many integration skills; not 3 because nothing pins it to HubSpot specifically, raising conflict risk.

2 / 5

Total

8

/

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.