CtrlK
BlogDocsLog inGet started
Tessl Logo

gleap

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

63

Quality

75%

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/gleap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 an efficient, highly actionable CLI guide with a clearly sequenced, validated connection workflow and good section organization; its only gaps are minor prose that could be tighter and the lack of any external reference split for a skill that is somewhat long.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands with tight surrounding prose; it has only minor over-explanation ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It provides copy-paste-ready, executable bash commands for install, login, connection ensure/get, action list/run, and proxy requests with a full flag table, covering the common cases completely.

5 / 5

Workflow Clarity

The connection flow is a clearly sequenced state machine (ensure -> poll with --wait -> branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with explicit validation via state checks and feedback loops (re-poll after the user completes an action), matching the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections in a single self-contained file with no nested or broken references, but at ~150 lines with no split into reference files it sits at 'good structure; most content appropriately placed' rather than the one-level-deep reference split that earns a 5.

4 / 5

Total

18

/

20

Passed

Description

61%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 correctly pairs a 'what' with an explicit 'Use when' clause and is highly distinct thanks to the named Gleap product, but its capability phrasing is generic and it misses the natural trigger terms (feedback, bug reports) users would say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Gleap capabilities such as 'collect user feedback, track bug reports, and triage tickets'.

Add natural trigger terms users actually say, e.g. 'Use when the user wants to collect feedback, log or track bug reports, or manage Gleap tickets and tasks'.

Mention the data objects users work with (Projects, Reports, Boards, Tasks) to make the 'when' clause more specific and reduce overlap with generic data-management skills.

DimensionReasoningScore

Specificity

The description names the Gleap domain but its actions ('Manage data, records, and automate workflows') are generic and do not describe Gleap's concrete capabilities (feedback/bug reporting), matching the 'names the domain but actions are minimal or generic' anchor rather than the concrete-action anchors at 3+.

2 / 5

Completeness

Both 'what' ('Gleap integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Gleap data') are present and explicit, matching the anchor where both exist but the 'when' could be more specific; it is not a 5 because the trigger phrase lacks concrete Gleap-specific triggers.

4 / 5

Trigger Term Quality

'interact with Gleap data' surfaces the 'Gleap' keyword, but it omits the natural terms users actually say (feedback, bug reports, tickets), fitting 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product Gleap with a trigger scoped to 'Gleap data' gives a clear niche and distinct triggers with minimal conflict risk against other skills.

5 / 5

Total

14

/

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.