Name: jibble
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jibble

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

Quality

72%

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

Quality

Content

87%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 is a strong, action-oriented CLI guide with executable commands, a clear validated connection workflow, and good sectioning. It is held back only by minor prose padding and a few inline sections that could be externalized.

Suggestions

Trim editorial padding like 'so you can focus on the integration logic rather than auth plumbing' to keep the guide lean.

Consider moving the clientAction object field breakdown and the proxy flags table into a separate reference file, leaving SKILL.md as a tighter overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal concept explanation, but has minor padding such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed, fitting 'Efficient; minor instances of over-explanation' rather than the fully lean level 5.	4 / 5
Actionability	It provides copy-paste ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a flags table covering common cases, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connect-and-poll sequence has explicit validation checkpoints — polling with '--wait', branching on state values (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), and re-polling after user action — matching the anchor with explicit validation steps and a feedback loop.	5 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references, but a sizable chunk of inline detail (the full clientAction object breakdown and proxy flags table) could be split out, fitting 'Good structure; most content appropriately placed; minor organization gaps' rather than the cleanly split level 5.	4 / 5
	Total	18 / 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 clearly names its niche (Jibble) and includes an explicit 'Use when' trigger, but the capability statement relies on generic verbs like 'Manage data, records, and automate workflows' rather than concrete Jibble-specific actions. Tightening the action list would lift specificity and distinctiveness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Jibble capabilities, e.g. 'Track time, manage clock entries, users, projects, leaves, and reports in Jibble.'

Add user-natural trigger terms and synonyms to the 'Use when' clause, e.g. 'Use when the user wants to track time, clock in/out, manage attendance, or query Jibble timesheets and reports.'

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Jibble domain but the actions are minimal and generic, matching the anchor 'Names the domain but actions are minimal or generic' rather than the more concrete level 3.	2 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Jibble data'), but the 'what' is generic so it does not reach the concrete level 5 anchor.	4 / 5
Trigger Term Quality	It surfaces 'Jibble' and 'interact with Jibble data' as relevant keywords but misses common variations or synonyms users might say, fitting 'Some relevant keywords but missing common variations or synonyms' rather than the fuller level 4 coverage.	3 / 5
Distinctiveness Conflict Risk	The 'Jibble' niche name and explicit trigger make it mostly distinct with only minor overlap risk, though the generic action verbs keep it short of the clear-niche level 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/jibble/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.