Name: salla
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

salla

Salla integration. Manage Recordses. Use when the user wants to interact with Salla data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

81%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 is a well-structured, executable guide to the Membrane/Salla CLI with strong workflow clarity and explicit feedback loops; its main gap is minor over-explanation and placeholder-dependent commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, with only minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing".	4 / 5
Actionability	Concrete copy-paste bash commands with a clear flag table cover common cases, though placeholders like CONNECTION_ID, QUERY, and actionId require substitution.	4 / 5
Workflow Clarity	The connection workflow is a clear sequence with explicit polling and state branches (READY/BUILDING/CLIENT_ACTION_REQUIRED) plus feedback loops ("After the user completes the action... poll again").	5 / 5
Progressive Disclosure	A single self-contained file is organized into clear sections (Overview, Install, Auth, Connecting, Actions, Proxy, Best practices) with no external references needed.	4 / 5
	Total	17 / 20 Passed

Description

57%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 answers both what and when with an explicit trigger tied to a distinct platform, but its capability list is minimal and the term "Recordses" is vague and oddly pluralized.

Suggestions

Replace "Manage Recordses" with concrete CRUD actions, e.g. "create, read, update, delete, and list Records in Salla".

Add natural trigger synonyms a user might say, such as "Salla orders", "Salla store data", or "Salla API", to broaden trigger coverage.

Fix the term "Recordses" to "Records" to avoid a confusing, non-standard plural that users are unlikely to say.

Dimension	Reasoning	Score
Specificity	"Manage Recordses" names the Salla domain but offers only one minimal, generic action verb, matching the anchor where the domain is named but actions are minimal.	2 / 5
Completeness	Both a "what" ("Salla integration. Manage Recordses.") and an explicit "when" ("Use when the user wants to interact with Salla data") are present, though the what is thin.	4 / 5
Trigger Term Quality	"Salla", "Salla data", and "interact with Salla" provide the key natural term a user would say, but common variations or synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	"Salla" is a specific named platform giving a clear niche, but the generic verb "interact with Salla data" leaves minor overlap risk.	4 / 5
	Total	13 / 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/salla/SKILL.md
Commit: f484c82

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