Name: backendless
Rating: 62.4 (1 reviews)
Author: membranedev

backendless

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

Quality

74%

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

Quality

Content

75%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 strongly actionable, copy-paste-ready CLI guide with a clear multi-step connection workflow and explicit state-handling feedback loops. Its main weakness is conciseness: an opening paragraph explaining what Backendless is and who uses it, plus minor redundancy between the action-search sections.

Suggestions

Trim or remove the opening paragraph describing Backendless's platform and target audience ('citizen developers, startups, and enterprises') — Claude does not need this to run the integration.

Remove the editorial phrase 'so you can focus on the integration logic rather than auth plumbing' and other commentary that does not change what Claude should do.

Consolidate the duplicate 'Searching for actions' and 'Popular actions' sections, which both instruct running 'action list --intent=QUERY', and explicitly label the 'Step 2' referenced in the connection flow.

Dimension	Reasoning	Score
Conciseness	Quotes 'Backendless is a visual app development platform that provides a no-code/low-code environment... used by citizen developers, startups, and enterprises' and 'so you can focus on the integration logic rather than auth plumbing' — mostly efficient command reference, but the opening paragraph explains what Backendless is and who uses it, plus editorial fluff Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor and falling below the lean 4.	3 / 5
Actionability	Quotes copy-paste-ready commands like 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://backendless.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ...' plus a full proxy flags table — fully executable commands covering install, login (interactive + headless), connection, polling, action search/run, and proxy; matches the 5 anchor for copy-paste-ready guidance over common cases.	5 / 5
Workflow Clarity	Quotes a clear sequence (Install CLI → Authentication → Connecting → 'poll until state is no longer BUILDING' with explicit READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling → search → run) with feedback loops during connection setup; held below 5 because action execution has no validation/verification step and 'Step 2' is referenced but never explicitly labeled as a section.	4 / 5
Progressive Disclosure	Quotes well-organized sections ('## Backendless Overview', '## Working with Backendless', '### Searching for actions', '## Best practices') with no nested or multi-level references in a single self-contained file; held below 5 because the file exceeds 50 lines and the 'Popular actions' section duplicates the 'Searching for actions' command, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clearly names a distinct product and provides both a 'what' and a 'when' clause in third-person voice, with a reasonable natural-language trigger. Weaknesses are generic action verbs and a 'when' clause narrower than the stated capabilities.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create and query data tables, manage users and roles, run Cloud Code functions, and automate workflows.'

Broaden the 'when' trigger to match the stated capabilities, e.g. 'Use when the user wants to manage Backendless data, records, users, or automate Backendless workflows.'

Consider adding natural synonyms/terms users say (e.g. 'Backendless database', 'data tables', 'Cloud Code') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — names the Backendless domain plus a couple of actions, but the verbs ('manage', 'automate') are generic rather than concrete like 'extract' or 'fill'; this matches the 'names domain and 1-2 concrete actions, not comprehensive' anchor and falls below score 4 which requires several specific actions.	3 / 5
Completeness	Quotes 'Backendless integration. Manage data, records, and automate workflows' (what) and 'Use when the user wants to interact with Backendless data' (when); both are present, but the 'when' clause only references data and omits records/workflows, so it could be more explicit — matching the 4 anchor rather than the fully explicit 5.	4 / 5
Trigger Term Quality	Quotes 'Backendless', 'data', 'records', 'workflows' and 'Use when the user wants to interact with Backendless data' — good keyword coverage with the distinctive product name as a natural trigger, though common synonyms/variations are missing, so it sits above 3 but below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Quotes 'Backendless integration' and 'Use when the user wants to interact with Backendless data' — Backendless is a specific named product forming a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/backendless/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.