CtrlK
BlogDocsLog inGet started
Tessl Logo

judgeme

Judge.me integration. Manage Reviews, Products. Use when the user wants to interact with Judge.me data.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/judgeme/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 concrete CLI commands and a clear connection workflow, and it is reasonably well structured. Weaker spots are marketing-fluff padding and the absence of validation guidance before destructive operations.

Suggestions

Remove marketing prose (e.g. "builds trust and increases sales") and tighten explanatory sentences to assume Claude's competence.

Add a validation/verification step before destructive actions, e.g. fetch and confirm the target review/webhook before running delete-webhook or update-review-status.

Fix the dangling "skip to Step 2" reference by adding an explicit Step 2 heading so the connection-to-action transition is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI commands and tables, but includes unnecessary padding such as the marketing intro ("This in turn builds trust and increases sales") and explanatory prose that could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for install, auth, connection, action search/run, and proxying, plus a concrete popular-actions table and a complete proxy-flag table covering common cases.

5 / 5

Workflow Clarity

The connection workflow is well sequenced with state-based checkpoints and a poll-after-action feedback loop, but destructive actions (delete-webhook, update-review-status) are presented without validation/verification steps, capping the score at 3.

3 / 5

Progressive Disclosure

Content is well organized into clearly headed sections with no nested references and a single inline actions table that aids discovery; minor gap is the 16-row actions table that could optionally live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

66%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 is concise and correctly pairs a "what" with an explicit "Use when" trigger, anchored to a distinct branded platform. Its main weakness is generic action wording and limited keyword synonyms, which keep specificity and trigger quality at mid-range.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Fetch, reply to, and moderate reviews; update products and shop settings."

Expand the trigger phrase with natural synonyms users say, e.g. "Use when the user mentions reviews, ratings, testimonials, or wants to manage Judge.me data."

Add file/extension-style concrete cues such as review IDs or webhook events to broaden trigger coverage.

DimensionReasoningScore

Specificity

It names the domain (Judge.me) and concrete entities ("Manage Reviews, Products"), but the single verb "Manage" is generic, so it lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Both a clear "what" ("Judge.me integration. Manage Reviews, Products.") and an explicit "when" ("Use when the user wants to interact with Judge.me data.") are present, though the trigger could enumerate more specific cases.

4 / 5

Trigger Term Quality

It includes relevant keywords ("Judge.me", "Reviews", "Products") but misses common variations and synonyms like "ratings", "testimonials", or "e-commerce reviews".

3 / 5

Distinctiveness Conflict Risk

"Judge.me" is a specific named platform giving a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.