Name: jumpcloud
Rating: 56.8 (1 reviews)
Author: membranedev

jumpcloud

JumpCloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with JumpCloud data.

Quality

65%

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/jumpcloud/SKILL.md

Quality

Content

67%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 delivers strong executable guidance with a clear, validated connection workflow and good section organization. Its weaknesses are minor marketing padding and inlined reference detail that could be externalized.

Suggestions

Remove marketing phrasing like 'single pane of glass' and 'focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Consider moving the clientAction state-handling detail and the proxy flag table into a separate reference file to improve progressive disclosure.

Clarify how to obtain CONNECTION_ID (e.g., from the connection ensure output) so the action and request examples are fully executable end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padding Claude does not need such as the marketing line 'single pane of glass' and 'so you can focus on the integration logic rather than auth plumbing', fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for login, connection ensure, action list/run, and proxy requests with a flag table, leaving only minor gaps like unresolved CONNECTION_ID placeholders, matching the 'mostly executable guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, with only minor checkpoint gaps, fitting the 'clear sequence with most checkpoints present' anchor.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives in SKILL.md under well-organized sections (Overview, Authentication, Connecting, Searching, Actions, Best practices); structure is good though some detailed reference material (clientAction fields, proxy flags) is inlined rather than split out, matching the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly identifies the JumpCloud niche and includes an explicit 'Use when' clause, satisfying both what and when. Its main weakness is generic action verbs and limited trigger-term variation rather than concrete JumpCloud-specific operations.

Suggestions

Replace generic verbs with concrete JumpCloud operations, e.g. 'Create and update users, manage user groups and devices, run commands, and query System Insights.'

Expand trigger terms to include natural user phrasings like 'JumpCloud users', 'JumpCloud devices', 'user groups', or 'system insights'.

Tighten the 'Use when' clause to enumerate specific intents such as onboarding users, applying policies, or running device commands.

Dimension	Reasoning	Score
Specificity	The description names the JumpCloud domain and lists actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete operations, so it sits at the anchor naming a domain with a few actions that are not comprehensive.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with JumpCloud data'), but the trigger clause is somewhat generic rather than concrete, fitting the anchor where both exist yet 'when' could be more specific.	4 / 5
Trigger Term Quality	'JumpCloud' and 'interact with JumpCloud data' provide the core natural keyword, but coverage lacks common variations or synonyms a user might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill explicitly to JumpCloud gives it a clear niche with minimal conflict risk, but the generic action verbs ('manage data, records') leave minor overlap with adjacent integration skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/jumpcloud/SKILL.md
Commit: f484c82

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