hubspot-integration

Authentication for single-account integrations

Quality

17%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/hubspot-integration/SKILL.md

Quality

Content

14%Scale 1-5

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

This skill is essentially a skeleton or outline with no substantive content. It lists topic headings and placeholder table rows but provides zero actionable guidance, no code examples, no concrete steps, and no real references. It would not help Claude perform any HubSpot integration task.

Suggestions

Add concrete, executable code examples for each pattern (e.g., OAuth token exchange, private app token usage in API calls, CRM CRUD operations with actual HTTP requests or SDK calls).

Replace the placeholder sharp edges table with real issues, specific descriptions, and inline solutions or links to actual documentation files.

Define a clear workflow with numbered steps for at least the primary use case (e.g., authenticating with a private app token and making a CRM API call), including validation/verification steps.

Either create and reference supporting bundle files (e.g., OAUTH.md, CRM_OPERATIONS.md) with detailed guidance, or inline the essential content directly in the skill.

Dimension	Reasoning	Score
Conciseness	The content is relatively short, but much of it is filler — the sharp edges table has placeholder 'Issue' and 'See docs' entries that add no value, and the 'When to Use' section is a tautological placeholder. It's not excessively verbose but wastes tokens on non-information.	3 / 5
Actionability	There is zero concrete, executable guidance anywhere. No code examples, no API endpoints, no commands, no specific steps. Every section is a vague label or placeholder with no actionable content.	1 / 5
Workflow Clarity	There are no steps, no sequences, no validation checkpoints. The skill lists pattern names (OAuth, Private App Token, CRUD) but never describes how to perform any of them. No workflow is defined.	1 / 5
Progressive Disclosure	The sharp edges table says 'See docs' repeatedly but never links to any actual documents. There are no bundle files, no referenced paths, and no structured navigation to deeper content. References are vague and unresolvable.	1 / 5
	Total	6 / 20 Passed

Description

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

This description is extremely terse and lacks actionable detail. It names a domain (authentication for single-account integrations) but fails to describe any concrete actions, provide trigger terms users would naturally use, or specify when Claude should select this skill. It would be very difficult for Claude to reliably choose this skill from a list of alternatives.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Configures API keys, generates OAuth tokens, and manages credentials for single-account service integrations.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up authentication, API keys, tokens, or credentials for a single-account integration.'

Include specific examples of integration types or authentication methods to improve trigger term coverage and distinctiveness, e.g., 'OAuth, API key, bearer token, service account.'

Dimension	Reasoning	Score
Specificity	Names the domain ('authentication', 'single-account integrations') but provides no concrete actions. It doesn't describe what the skill actually does—no verbs like 'configures', 'generates tokens', 'manages credentials', etc.	2 / 5
Completeness	There is no clear 'what does this do' beyond a vague noun phrase, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing.	1 / 5
Trigger Term Quality	'Authentication' is a relevant keyword, but 'single-account integrations' is somewhat technical jargon. Missing natural user terms like 'login', 'API key', 'credentials', 'OAuth', 'token', or specific integration names.	2 / 5
Distinctiveness Conflict Risk	'Single-account integrations' narrows the scope somewhat compared to generic authentication, but without specifying which integrations or what kind of authentication, it could still overlap with other auth-related skills.	3 / 5
	Total	8 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/hubspot-integration/SKILL.md
Commit: 57c135b

Reviewed: 4 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.