CtrlK
BlogDocsLog inGet started
Tessl Logo

hubspot-pipeline-health

Use when reviewing HubSpot pipeline health, forecasts, stale deals, slipping close dates, or open deal risks.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A tight, well-structured instruction skill that names specific tools, fields, defaults, and an explicit output contract, with clear sequencing and checkpoints. Minor term vagueness ("high-signal deals") is the only soft spot in an otherwise exemplary body.

Suggestions

Define "high-signal deals" concretely (e.g., above a value threshold, in late stages, or recently touched) so step 5 is unambiguous.

Consider splitting the run-on risk-flag sentence in "Risk And Output" into a short bullet list for faster scanning.

DimensionReasoningScore

Conciseness

The body is lean with no concept primers or filler; every line (named tools, fields, defaults, output contract) earns its place and assumes Claude already knows deals, fields, and forecasts.

3 / 3

Actionability

It specifies concrete tools (get_user_details, get_properties, search_crm_objects, get_crm_objects, manage_crm_objects), named fields (dealname, amount, dealstage, pipeline, closedate), a default scope, and an explicit output structure, which is actionable guidance well above the "some concrete guidance but incomplete" bar; the only soft spot is the undefined term "high-signal deals."

3 / 3

Workflow Clarity

The numbered 1-5 sequence is clearly ordered with explicit checkpoints: confirm read access, check total and paginate, state unavailable signals, and gate write actions (manage_crm_objects) until after the confirmation table.

3 / 3

Progressive Disclosure

As an under-50-line single-purpose skill with no bundle files, its well-organized Workflow/Risk-And-Output sections plus a clearly signaled one-level reference to a sibling skill ([../hubspot/SKILL.md] for access, pagination, write approvals) meet the bar for clean overview navigation.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concise, domain-specific description with explicit "Use when" triggers and natural user phrasing. Its only weakness is that the concrete actions live mostly in the body rather than being enumerated here, leaving the "what" somewhat action-light.

Suggestions

Optionally surface 2-3 concrete actions in the description (e.g., "flag at-risk deals, summarize hygiene patterns, recommend follow-ups") to lift specificity from naming the domain toward listing multiple actions.

Add a common phrasing variant like "deal review" or "pipeline review" to broaden trigger coverage for users who say "review my pipeline."

DimensionReasoningScore

Specificity

It names a concrete domain and several review targets ("forecasts, stale deals, slipping close dates, or open deal risks") but centers on a single verb ("reviewing") rather than listing multiple distinct actions, so it lands at "names domain and some actions, but not comprehensive."

2 / 3

Completeness

It explicitly states the activity and domain ("reviewing HubSpot pipeline health") for the "what" and opens with an explicit "Use when..." trigger list for the "when," satisfying both halves with an explicit trigger.

3 / 3

Trigger Term Quality

Phrases like "pipeline health, forecasts, stale deals, slipping close dates, or open deal risks" are natural terms a sales/revops user would actually say, giving good coverage of domain-natural keywords.

3 / 3

Distinctiveness Conflict Risk

The HubSpot-pipeline/sales-deal niche is narrow and specific, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.