Name: repairshopr
Rating: 58.4 (1 reviews)
Author: membranedev

repairshopr

RepairShopr integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with RepairShopr data.

Quality

67%

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

Quality

Content

56%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 actionable Membrane CLI guidance is strong and executable, but it is undermined by a large padded keyword-stuffed overview list that wastes tokens and adds no navigational value. Trimming that list would materially raise both conciseness and progressive disclosure.

Suggestions

Delete the padded overview bullet list (lines 23–199) or replace it with the handful of actual RepairShopr resources the skill supports; most listed items (Podcast, Hack, Font, Infographic) are irrelevant.

Replace the vague "Use action names and parameters as needed" with a short worked example showing one action run with real parameters.

Tighten the connection workflow by labeling the post-connection steps explicitly (e.g. a numbered "Step 2: discover actions" / "Step 3: run action") so the "skip to Step 2" reference resolves clearly.

Dimension	Reasoning	Score
Conciseness	The "RepairShopr Overview" section is a ~177-item bullet list (lines 23–199) padded with irrelevant entries like Podcast, White Paper, Hack, Secret, Font and Icon, which is heavy stuffing even though the CLI sections are efficient.	2 / 5
Actionability	Concrete, copy-paste-ready commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) with flag tables and JSON examples, leaving only minor gaps around placeholder IDs.	4 / 5
Workflow Clarity	The connection flow is sequenced with state checks (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, though "Step 2" is referenced loosely and "Use action names and parameters as needed" is vague.	4 / 5
Progressive Disclosure	Headers provide some structure and there are no nested references, but the monolithic inlined 177-item list is content that should not be in SKILL.md at all, leaving organization only partially effective.	3 / 5
	Total	13 / 20 Passed

Description

78%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.

A focused, third-person description that names a distinct product and covers both capability and trigger context. It is solid but stops short of comprehensive action enumeration and concrete trigger phrasing.

Suggestions

Replace the generic "Manage ... and more" with a fuller list of the actual RepairShopr resources (Tickets, Invoices, Customers, Assets) to lift specificity toward 5.

Expand the "Use when" clause with concrete trigger phrases (e.g. "when the user mentions tickets, invoices, or repair jobs in RepairShopr") to make the when explicit.

Dimension	Reasoning	Score
Specificity	"Manage Deals, Persons, Organizations, Leads, Projects, Activities and more" lists several specific entities under a single concrete verb, with the trailing "and more" leaving minor coverage gaps rather than being comprehensive.	4 / 5
Completeness	It states both what ("Manage Deals, Persons... ") and when ("Use when the user wants to interact with RepairShopr data"), but the when clause is somewhat generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	"RepairShopr" is the dominant natural keyword and "interact with RepairShopr data" gives a usable trigger phrase, but few synonyms or variations are offered beyond the product name.	4 / 5
Distinctiveness Conflict Risk	"RepairShopr integration" names a specific SaaS product, creating a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 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/repairshopr/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.