Name: baselinker
Rating: 60 (1 reviews)
Author: membranedev

baselinker

BaseLinker integration. Manage Products, Orders, Shops, Users. Use when the user wants to interact with BaseLinker data.

Quality

70%

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/baselinker/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 content delivers highly executable Membrane CLI commands and a solid connection workflow with state-based validation. Weaknesses are the padded introductory concept paragraph, an incomplete Popular actions table, and missing validation guidance around destructive action execution.

Suggestions

Trim or remove the opening explanatory paragraph about what BaseLinker is; Claude can infer the platform's purpose.

Add a verification/check step after running destructive actions (e.g., re-query the order or stock to confirm the change applied).

Fill the empty Description column in the Popular actions table so the agent can pick the right action without extra lookups.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening paragraph ("BaseLinker is an e-commerce platform that helps online sellers manage and automate...") explains a concept that could be trimmed, matching the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the full workflow (install, login, connection ensure/get, action list/run, request), but the Popular actions table has an empty Description column and several placeholders, leaving minor gaps below fully executable.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state polling and a CLIENT_ACTION_REQUIRED feedback loop, but running potentially destructive/batch actions (set order status, update stock, add order) has no validation checkpoint before or after, which caps clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The single file is organized into clear, well-labeled sections covering overview through best practices with no nested references; minor gaps (empty action descriptions, a "1b" heading with no matching "1a") keep it just below a 5.	4 / 5
	Total	14 / 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.

The description cleanly answers both what and when and is well-differentiated by naming the BaseLinker platform and its core entities. Its main weakness is the generic "Manage" verb and a broad "interact with BaseLinker data" trigger that could name more concrete use cases.

Suggestions

Replace the generic "Manage" with varied concrete verbs (e.g., "create, update, and query Products, Orders, Shops, Users").

Expand the "Use when" clause with concrete triggers like "when the user wants to sync inventory, track orders, or manage listings in BaseLinker".

Add a synonym or common phrasing (e.g., "BaseLinker API") to broaden natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage Products, Orders, Shops, Users" lists several concrete entities the skill acts on, though the single generic verb "Manage" is less varied than the anchor's distinct actions, so it stops below 5.	4 / 5
Completeness	It states a clear "what" ("BaseLinker integration. Manage Products, Orders, Shops, Users.") and an explicit "when" ("Use when the user wants to interact with BaseLinker data"), but the trigger clause is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	"BaseLinker", "Products", "Orders", "Shops", "Users" are natural terms users would say, but the description lacks synonyms or platform variations that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	The named platform "BaseLinker" plus its specific data entities carve a clear niche with minimal overlap against 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/baselinker/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.