CtrlK
BlogDocsLog inGet started
Tessl Logo

judopay

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

82%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, executable CLI commands and a clear workflow that includes validation and state-handling feedback loops. It is efficient and well-structured, with only minor conciseness and organization gaps.

DimensionReasoningScore

Conciseness

The body is mostly lean with concrete code blocks and command examples, with only minor over-explanation such as 'This is the fastest way to get a connection...', fitting the score-4 anchor of efficient with minor trimmable instances.

4 / 5

Actionability

The content provides fully executable, copy-paste-ready CLI commands with flags and JSON usage examples covering install, auth, connection, action discovery, and proxying, matching the score-5 anchor.

5 / 5

Workflow Clarity

There is a clear sequence (install → auth → connect → poll until READY → discover → run) with validation checkpoints and state-based feedback loops, but the dangling 'skip to Step 2' reference (no labeled Step 2) is a minor gap keeping it below score 5.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Overview, Working with Judopay, Best practices) with no unnecessary nesting, but the sparse 'Judopay Overview' bullet list and absence of any split-out reference files leave minor organization gaps versus the score-5 ideal.

4 / 5

Total

17

/

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 identifies a clear, branded niche (Judopay) and includes an explicit 'Use when' trigger, but the capability phrasing is generic and the trigger terms lack synonyms or concrete actions. It is solidly above average but not exemplary.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and capture payments, fetch transactions, and manage refunds via Judopay'.

Expand the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to process payments, look up transactions, or integrate Judopay checkout'.

Avoid the catch-all 'Manage data, records, and automate workflows', which overlaps with many skills and weakens distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('Judopay integration') but the stated actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities, matching the score-2 anchor better than score 3 which requires 1-2 concrete actions.

2 / 5

Completeness

Both 'what' (Judopay integration, manage data/records/workflows) and 'when' (use when the user wants to interact with Judopay data) are present, but the 'when' clause is generic and could be more specific, matching the score-4 anchor; it is not score 5 because the trigger phrases are not concrete.

4 / 5

Trigger Term Quality

The trigger clause 'Use when the user wants to interact with Judopay data' includes the natural term 'Judopay data' but lacks synonyms or common variations, fitting the score-3 anchor of 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The Judopay brand name gives the skill a clear niche with minimal conflict risk, but the generic action phrasing ('Manage data, records') keeps it from the fully-distinct score-5 anchor.

4 / 5

Total

13

/

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.