Name: backblaze
Rating: 58.4 (1 reviews)
Author: membranedev

backblaze

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

Quality

68%

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/backblaze/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 content is highly actionable with copy-paste commands and a well-sequenced connection workflow including polling feedback loops. Its main weaknesses are mild verbosity in the intro and a lack of validation checkpoints on the action-execution path.

Suggestions

Trim the opening 'Backblaze is a cloud storage and data backup service...' paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside to reduce concept-overexplaining.

Add a validation/check step before running write or destructive actions (e.g. confirm the action's inputSchema and expected effect before 'membrane action run'), especially for proxy DELETE/PUT requests.

Consider splitting the connection state-machine details and proxy flag reference into a reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but the opening paragraph ('Backblaze is a cloud storage and data backup service. It's used by individuals and businesses...') explains a concept Claude already knows and lines like 'so you can focus on the integration logic rather than auth plumbing' add padding, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste ready, fully executable commands throughout (install, login, connection ensure, action list/run, request) plus a flag options table, matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connect → poll → search → run sequence is clear with an explicit state-machine feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling, but the action-execution path lacks validation checkpoints, fitting anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than the fully-validated 5.	4 / 5
Progressive Disclosure	The single SKILL.md is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) with no nested references, fitting the 'good structure; most content appropriately placed; minor organization gaps' anchor; it is over 50 lines so it does not get the simple-skill 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 has a clear, distinctive Backblaze niche and an explicit 'Use when' clause, but its capability list is generic and its trigger terms lack synonyms like B2/buckets/backups. Tightening the actions to concrete Backblaze operations and broadening trigger terms would lift it.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Backblaze operations such as managing buckets, uploading/downloading files, and B2 account tasks.

Expand trigger terms to include natural synonyms users say — 'B2', 'buckets', 'backups', 'cloud storage' — alongside 'Backblaze'.

Make the 'when' clause more concrete, e.g. 'Use when the user wants to manage Backblaze B2 buckets, upload or download files, or interact with Backblaze data.'

Dimension	Reasoning	Score
Specificity	The actions 'Manage data, records, and automate workflows' name the Backblaze domain but are generic rather than concrete Backblaze-specific operations (no mention of buckets, files, or B2 accounts), matching the 'names domain but actions are minimal or generic' anchor and falling below the 1-2 concrete actions of score 3.	2 / 5
Completeness	It states both what ('Backblaze integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Backblaze data.'), but the 'when' trigger is generic rather than concrete trigger phrases, so it sits at anchor 4 rather than the explicit-trigger 5; the present 'Use when' clause keeps it above the 3 cap.	4 / 5
Trigger Term Quality	'Backblaze' and 'Backblaze data' are natural terms a user would say, but common synonyms and variations (B2, buckets, backups, file extensions) are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Backblaze is a specific named service giving a clear niche with distinct triggers ('interact with Backblaze data'), so it is unlikely to conflict with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	14 / 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/backblaze/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.