CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

backendless

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/backendless/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a genuinely actionable CLI guide: real install, auth, connection, action, and proxy commands with a useful flags table and a well-handled connection-state loop. Its weaknesses are moderate verbosity (platform background, duplicated action-list section), broken step cross-references, and no verification step before running data-mutating actions.

Suggestions

Add a validation checkpoint before running state-changing actions, e.g. 'Run with a read-only/list action first to confirm the connection targets the right app before creating, updating, or deleting records', and note how to inspect output errors and retry — this lifts workflow clarity past the destructive/batch cap.

Fix the step numbering: replace the dangling 'Step 2' references and the orphaned '#### 1b' header with a consistent numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run actions), and remove the duplicated `action list` instructions from either 'Searching for actions' or 'Popular actions'.

Trim the opening platform-marketing paragraph and the 'Use action names and parameters as needed.' filler, and move the proxy flag table (and optionally the entity catalog) into a references/ file to tighten the main body.

DimensionReasoningScore

Conciseness

The body is mostly commands, but it opens with platform background Claude does not need ("Backendless is a visual app development platform... It's used by citizen developers, startups, and enterprises"), contains filler ("Use action names and parameters as needed."), and documents `action list` twice in 'Searching for actions' and 'Popular actions'. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; not 2 because the padding is limited to a few spots.

3 / 5

Actionability

Concrete executable commands cover the full path — install (`npm install -g @membranehq/cli@latest`), login (including headless completion), `connection ensure` with state polling, `action list`/`action run` with `--input` JSON, and proxy requests with a complete flag table. Matches 'mostly executable guidance with minor gaps'; not 5 because there is no worked example with a real intent, actionId, and sample input/output pair.

4 / 5

Workflow Clarity

The sequence (install → login → connect → poll state → search → run → proxy) and the connection-state feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll) are clear, but step numbering is incoherent (a '#### 1b' header with no step 1, and 'skip to **Step 2**' pointing at a nonexistent Step 2) and there is no validation before running actions that can mutate or delete Backendless data. The missing-validation cap for data/batch operations applies, so it cannot exceed 3.

3 / 5

Progressive Disclosure

The skill is a single ~150-line file with no bundle files and no references at all. Header-based structure is decent, but the proxy flag table and the 17-item entity catalog could live in a reference, the `action list` documentation is duplicated across sections, and the dangling 'Step 2' cross-reference hurts navigation — matching 'some structure but could be better organized; content that should be separate is inline'. The under-50-line exception does not apply.

3 / 5

Total

13

/

20

Passed

Description

62%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 is short, honest, and has an explicit 'Use when' clause anchored to a named platform, giving it good distinctiveness and completeness. Its main weakness is thin capability coverage — generic verbs like 'manage' and 'automate' instead of the concrete Backendless features the body enumerates — which limits specificity and natural trigger-term coverage.

Suggestions

Enumerate 3-4 concrete capabilities in the description (e.g., 'Query and modify data tables, manage files and users, send push notifications, run Cloud Functions/API services') so specificity reaches the comprehensive anchor.

Add natural trigger variations users would actually say, such as 'Backendless API, data tables, geopoints, roles and permissions, push notifications', to broaden trigger-term coverage beyond the bare platform name.

Tighten the 'Use when' clause to cover more request shapes, e.g. 'Use when the user wants to read, create, update, or delete Backendless data or manage Backendless resources'.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Backendless domain with only 1-2 generic actions (manage, automate) and no concrete coverage of tables, files, users, push, or geo features, matching the 'domain plus 1-2 concrete actions, not comprehensive' anchor. It falls short of 4 because it does not list several specific actions.

3 / 5

Completeness

Both parts are explicit: what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Backendless data"). The 'when' clause is present but could be more specific with concrete trigger phrases, matching anchor 4; not 5 because the trigger guidance is single-phrase and narrow.

4 / 5

Trigger Term Quality

"Backendless" and "data"/"records" are relevant keywords, but common natural variations are missing (e.g., Backendless API, data tables, file storage, push notifications, geopoints). Fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Backendless integration" carves a clear named-platform niche with minimal conflict risk, but the generic phrases "manage data" and "automate workflows" could overlap with other data/automation skills (Airtable, Zapier) when the platform is not named. Mostly distinct with minor overlap risk, matching anchor 4 rather than the fully-distinct anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.