Name: jfrog
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jfrog

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

Quality

68%

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/jfrog/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 body delivers executable, well-structured guidance for connecting to JFrog and running actions via the Membrane CLI, with clear state-based checkpoints during connection setup. It is slightly weakened by a preamble explaining what JFrog is and by placeholders the user must substitute.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tight tables, though the opening paragraph explaining what JFrog is and the 'streamline their software delivery process' framing adds mild over-explanation Claude does not need.	4 / 5
Actionability	It provides copy-paste-ready membrane commands with flags and a clear options table for proxy requests, with only minor gaps such as the occasional placeholder (CONNECTION_ID, QUERY) that the user must fill in.	4 / 5
Workflow Clarity	The connection setup is sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a polling loop with --wait, providing clear checkpoints; it falls short of 5 only because there is no explicit error-recovery feedback loop for CONFIGURATION_ERROR beyond 'check the error field'.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested references, which is appropriate for its length; it stops short of 5 because the action catalog and proxy options could arguably be externalized, though staying inline is reasonable here.	4 / 5
	Total	16 / 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 identifies the JFrog niche and includes an explicit 'Use when' clause, satisfying the basic what-and-when requirement. It is let down by generic action verbs and missing the concrete JFrog entity terms (artifacts, builds, repositories) that users would naturally mention.

Suggestions

Replace generic verbs with concrete JFrog operations, e.g. 'Manage artifacts, builds, release bundles, and repositories, and automate release workflows.'

Broaden the trigger clause to reflect natural user phrasing: 'Use when the user wants to manage JFrog artifacts, builds, repositories, or automate release pipelines.'

Drop or sharpen 'records' which is vague and not clearly tied to a JFrog concept.

Dimension	Reasoning	Score
Specificity	The description names the domain (JFrog) and the concrete actions 'Manage data, records, and automate workflows' plus 'interact with JFrog data', but the actions are generic rather than listing specific operations like artifacts, builds, or release bundles found in the body.	3 / 5
Completeness	It states both the 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with JFrog data'), but the trigger could be more specific to particular JFrog tasks.	4 / 5
Trigger Term Quality	'JFrog' is a relevant keyword and 'data, records, and automate workflows' are useful, but common natural user phrases like 'artifacts', 'builds', 'release bundles', or 'repositories' are missing from the description.	3 / 5
Distinctiveness Conflict Risk	'JFrog' anchors it to a clear niche with minimal overlap risk, though 'manage data, records, and automate workflows' is broad enough that it could be slightly more tightly scoped to JFrog-specific entities.	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/jfrog/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.