Name: jetbrains-marketplace
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

jetbrains-marketplace

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/jetbrains-marketplace/SKILL.md

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 highly actionable with executable commands and a clear, checkpointed connection workflow, but it opens with concept padding Claude does not need and leaves a couple of minor workflow/organization gaps (an undefined 'Step 2', inlined advanced reference material). Overall it is a strong, well-structured integration skill.

Suggestions

Remove or condense the opening paragraph explaining what the JetBrains Marketplace is, since Claude already knows this; start directly with what the skill does and how to use it.

Define or fix the 'Step 2' reference (e.g., add an explicit '## Step 2: Searching and running actions' heading) so the cross-reference resolves.

Add a brief verification note after running actions (e.g., check the response `output` field or `error` for non-zero status) to close the action-execution loop.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient, but the opening paragraph explaining what the JetBrains Marketplace is ('a platform for developers to discover and purchase plugins...') and mildly promotional lines ('so you can focus on the integration logic rather than auth plumbing') explain concepts Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation' rather than the lean 4-5 anchors.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure with --wait, action list/run with --input, request with a complete flag table) covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install -> authenticate -> connect -> wait for ready -> search -> run) with explicit state checkpoints and a poll/re-poll feedback loop for connection readiness, but a dangling undefined 'Step 2' reference and the absence of success verification after running actions leave minor validation gaps, capping it below 5.	4 / 5
Progressive Disclosure	With no bundle files present, the ~140-line body is organized into clearly headed sections (Overview, Working with IntelliJ IDEA, Install, Authentication, Connecting, Searching, Popular actions, Best practices) that are easy to navigate; the inline proxy-flag table and clientAction details represent minor organization gaps rather than monolithic or buried structure, matching the 'good structure; most content appropriately placed' anchor.	4 / 5
	Total	16 / 20 Passed

Description

57%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 answers both what and when with an explicit trigger clause, but its capability wording is generic rather than concrete and its keyword coverage lacks synonyms. Distinctiveness is reasonably strong thanks to the IntelliJ IDEA niche.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions specific to IntelliJ IDEA (e.g., 'Search plugins, fetch plugin versions, read reviews, and pull download statistics').

Expand trigger terms to include natural synonyms users say, such as 'JetBrains', 'IDE plugin', 'plugin marketplace', or 'plugin downloads'.

Tighten the 'when' clause to name concrete triggers, e.g. 'Use when the user wants to search JetBrains plugins, check plugin versions, or review marketplace statistics.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('IntelliJ IDEA integration') but the actions ('Manage data, records, and automate workflows') are generic and not concrete, fitting the 'names the domain but actions are minimal or generic' anchor rather than the concrete-action anchors at 3+.	2 / 5
Completeness	Both 'what' ('IntelliJ IDEA integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with IntelliJ IDEA data') are present, fitting the 'has both what and when; when could be more explicit' anchor; it falls short of 5 because the 'what' is vague and the trigger phrases are not concrete.	4 / 5
Trigger Term Quality	'IntelliJ IDEA' and the trigger phrase 'interact with IntelliJ IDEA data' are natural terms a user might say, but coverage is thin with no synonyms or variants (e.g., 'IDE', 'plugin', 'JetBrains'), matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'IntelliJ IDEA' niche is mostly distinct with clear triggers and minor overlap risk, but the generic 'Manage data, records, and automate workflows' phrasing keeps it from the minimal-conflict 5 anchor.	4 / 5
	Total	13 / 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/jetbrains-marketplace/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.