Name: bidsketch
Rating: 55.2 (1 reviews)
Author: membranedev

bidsketch

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

Quality

63%

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

Quality

Content

65%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 highly actionable with copy-paste Membrane commands and a strong connection workflow, but it is weakened by a padded 'No description' actions table, missing validation for destructive create/update operations, and no progressive disclosure into reference files.

Suggestions

Remove or trim the 'Popular actions' table — 20 rows of 'No description' add noise with no information; either populate real descriptions or move it to a reference file.

Add a verification step after create/update/delete actions (e.g. re-list or get the resource to confirm the change applied) so the data-operation workflow has a validation checkpoint.

Externalize the entity overview and full action catalog into a references/ file, leaving SKILL.md as a concise overview that links one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands, but the 20-row "Popular actions" table where every row says "No description" is pure padding, and some clientAction explanation could be trimmed. Not a 4 because the noisy table and a few padded sections are noticeable rather than minor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (membrane login, connection ensure with --wait, action list/run, request proxy) with flags and JSON input examples covering the common cases. Not a concern below 5 — examples are concrete and run-ready.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state-check feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the core create/update data operations lack verification steps. Per the rubric cap, a batch/destructive-capable skill without validation of its data operations cannot score above 3; not a 2 because the connection sequence is genuinely clear.	3 / 5
Progressive Disclosure	Well-organized into clear sections, but everything is inlined into one file with no bundle files or one-level-deep references — the bulk actions table and entity list are content that could live in separate reference files. Not a 4 because there is no progressive disclosure structure pointing to detail materials; the skill is over the 50-line simple-skill threshold.	3 / 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 has an explicit Use-when trigger and a clear niche via the Bidsketch brand name, but its action language is generic ("manage data, records, automate workflows") and it omits the concrete proposal/client terms users would naturally say.

Suggestions

Replace generic verbs with concrete Bidsketch actions, e.g. "Create and send proposals, manage clients and fees, automate proposal workflows."

Add natural trigger terms users actually say: "proposals," "clients," "fees," "proposal templates."

Tighten the Use-when clause to reference proposals/clients specifically, e.g. "Use when the user wants to create, send, or track Bidsketch proposals or manage clients."

Dimension	Reasoning	Score
Specificity	Names the domain ("Bidsketch integration") but the actions are generic — "Manage data, records, and automate workflows" — with no concrete operations like creating proposals or managing clients. Not a 3 because the actions listed are abstract rather than the 1-2 concrete operations the anchor requires.	2 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Bidsketch data"). Not a 5 because the trigger phrase is generic rather than concrete (no mention of proposals/clients); not a 3 because the "when" clause is explicit, not merely implied.	4 / 5
Trigger Term Quality	Includes the natural proper noun "Bidsketch" and "interact with Bidsketch data," but misses the common terms users would actually say (proposals, clients, fees, templates). Not a 4 because keyword coverage is thin and lacks synonyms; not a 2 because "Bidsketch" itself is a specific, natural trigger rather than generic jargon.	3 / 5
Distinctiveness Conflict Risk	The branded name "Bidsketch" gives it a clear niche with minimal conflict risk against other skills. Not a concern at 4 because the proper-noun trigger is highly specific and unlikely to fire for the wrong skill.	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/bidsketch/SKILL.md
Commit: f484c82

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