Name: bringg
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bringg

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bringg/SKILL.md

Quality

Content

61%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 skill body is a well-structured, actionable CLI guide with strong concrete commands and a stateful connection workflow. Weaknesses are minor verbosity, a missing Step 2 anchor, and a dense ungrouped entity list.

Suggestions

Add an explicit "Step 2" heading (or reword the cross-references) so the "skip to Step 2" pointers resolve to a real section.

Group the flat entity list into categories (e.g. Dispatch, People, Billing, Configuration) so it scans as navigation rather than a wall.

Trim the opening "Bringg is a delivery management platform..." paragraph and the verbose clientAction field list, since Claude can infer the action semantics from the field names.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro paragraph explaining what Bringg is and the lengthy inlined clientAction schema are mild over-explanation that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands with explicit flags cover the common flows (auth, connection ensure, action list/run, proxy), with only minor placeholder gaps around CONNECTION_ID and actionId discovery.	4 / 5
Workflow Clarity	The connection flow is sequenced with polling states and a feedback loop (re-poll after client action), but the "skip to Step 2" reference has no corresponding Step 2 heading and there is no explicit validation checkpoint for confirming action success.	3 / 5
Progressive Disclosure	As a single-file skill with no bundle files, the content is well-sectioned into navigable headings; the main gap is the flat 40-item entity list that reads as a wall rather than grouped navigation.	4 / 5
	Total	14 / 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 cleanly answers what the skill does and when to use it, anchored by a distinctive brand name. Its main weakness is generic action phrasing ("manage data, records") rather than concrete Bringg capabilities.

Suggestions

Replace generic verbs with concrete Bringg operations, e.g. "create and dispatch tasks, manage drivers and teams, track deliveries in real time, configure webhooks".

Tighten the "when" clause with concrete triggers such as "Use when the user wants to create delivery tasks, assign drivers, track orders, or query Bringg records".

Dimension	Reasoning	Score
Specificity	Names the Bringg domain and three actions ("Manage data, records, and automate workflows"), but the actions are generic rather than Bringg-specific concrete operations, sitting below the anchor-3 midpoint.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and a "when" ("Use when the user wants to interact with Bringg data") are present, though the "when" trigger is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	The natural keyword "Bringg" and phrase "interact with Bringg data" are present, but coverage is limited to a single term family with no synonyms or variations, matching the anchor-3 example.	3 / 5
Distinctiveness Conflict Risk	The "Bringg" proper-noun brand name carves out a clear niche with minimal overlap risk against other skills.	5 / 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/bringg/SKILL.md
Commit: f484c82

Reviewed: 3 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.