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

simplebackups

SimpleBackups integration. Manage Backups, Restores, Alerts, Users. Use when the user wants to interact with SimpleBackups 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/simplebackups/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 is a solid, actionable integration guide built around concrete Membrane CLI commands and a well-sequenced connection workflow with polling checkpoints. It is weakened by some redundant/verbose prose, inconsistent step numbering, and the absence of validation guidance for destructive backup/restore operations.

Suggestions

Add an explicit validation/confirmation step before destructive actions (e.g. restores or backup deletions) — a "confirm with the user before running destructive actions" checkpoint — to satisfy the destructive-operations workflow requirement.

Fix the step numbering: either label the "Searching for actions" section as "Step 2" or remove the dangling "skip to Step 2" reference so the sequence is unambiguous.

Trim redundant prose — collapse the "Popular actions" section into "Searching for actions" and remove the marketing-style intro clause ("ensuring data is safe and recoverable") to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation (the marketing-style intro "ensuring data is safe and recoverable", "so you can focus on the integration logic rather than auth plumbing") and redundancy where "Popular actions" repeats the `action list` command already shown in "Searching for actions", so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready bash commands for every common case (install, login, connection ensure, action list/run, request proxy) plus a concrete flags table, but examples use unresolved placeholders (CONNECTION_ID, actionId) with no real SimpleBackups-specific action or input example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection workflow has a clear state-based sequence with polling checkpoints and a feedback loop (poll after CLIENT_ACTION_REQUIRED), but step numbering is inconsistent (references "Step 2" with no labeled Step 2 heading, uses "1b"), and because the skill drives destructive operations (restores, backup deletion) with no validation/confirmation guidance before running actions, the destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	The single-file skill is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching/Running actions, Proxy, Best practices) with no nested references and no bundle files to navigate; minor redundancy between "Popular actions" and "Searching for actions" keeps it just below a perfect structure score.	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 is well-constructed: it names the product, lists four concrete capability areas, uses third-person voice, and includes an explicit "Use when" trigger clause. Its main weakness is that the trigger guidance is a single generic phrase rather than enumerated concrete triggers.

Suggestions

Expand the "Use when" clause with concrete trigger phrases, e.g. "Use when the user wants to schedule backups, run restores, review alerts, or manage SimpleBackups users and teams."

Replace the single generic verb "Manage" with more specific verbs per area (e.g. "Schedule backups, run restores, review alerts, manage users") to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("SimpleBackups integration") and lists several concrete action areas ("Manage Backups, Restores, Alerts, Users"), giving good coverage, though the single generic verb "Manage" subsumes the actions rather than enumerating them, leaving minor gaps versus a fully comprehensive list.	4 / 5
Completeness	Clearly answers "what" ("Manage Backups, Restores, Alerts, Users") and includes an explicit "when" trigger ("Use when the user wants to interact with SimpleBackups data"), but the when clause is a single generic trigger rather than multiple concrete trigger phrases, matching the anchor where "when could be more explicit or specific."	4 / 5
Trigger Term Quality	Includes natural terms users would say ("Backups", "Restores", "Alerts", "Users", "SimpleBackups") with an explicit "Use when the user wants to interact with SimpleBackups data" clause, but omits common synonyms/variations and has no equivalent of file-extension triggers, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The named product "SimpleBackups" establishes a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor for a clear niche with distinct triggers.	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/simplebackups/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.