Tessl • The management layer for AI agent skills

SkillPublic

backblaze

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

Quality

63%

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

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 delivers executable Membrane CLI commands for the full connect-run workflow and handles connection states well, but it is padded with a Backblaze concept intro, contains a broken "Step 2" reference, and has redundant or empty sections (Overview, Popular actions) that hurt navigation. Tightening the structure into an explicit numbered workflow would lift most dimensions.

Suggestions

Delete the introductory paragraph explaining what Backblaze is and the "Backblaze Overview" bullet list, or replace them with a short mapping of Backblaze concepts to Membrane actions.

Fix the dangling "skip to **Step 2**" reference by numbering the workflow steps explicitly (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run actions) and merging the duplicated action-list guidance in "Searching for actions" and "Popular actions".

Either populate "Popular actions" with real frequently-used actions (e.g. list buckets, upload file) or remove the section, and move the flags table for proxy requests under it only if that section survives.

Dimension	Reasoning	Score
Conciseness	The body opens with an unneeded concept explainer ("Backblaze is a cloud storage and data backup service. It's used by individuals and businesses to securely store and access their files online...") and padded sentences like "This is the fastest way to get a connection. The URL is normalized to a domain...". It is mostly command-focused but includes unnecessary explanation, matching anchor 3 rather than 4's "minor instances of over-explanation".	3 / 5
Actionability	Commands are concrete and copy-paste ready throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://www.backblaze.com/" --json`, `membrane action run <actionId> --input '{"key": "value"}'`, plus a flags table for proxy requests. Minor gaps keep it below 5: the "Popular actions" section lists no actual actions, and "Use action names and parameters as needed" is vague.	4 / 5
Workflow Clarity	A rough sequence exists (install → login → connection ensure → poll until READY → search actions → run actions) with state-based polling checkpoints (CLIENT_ACTION_REQUIRED handling), but the text says "skip to Step 2" when no Step 2 is labeled anywhere, and the overall flow is never presented as an ordered workflow. This matches anchor 3 (sequence present, checkpoints implicit/incoherent in places) rather than 4.	3 / 5
Progressive Disclosure	There are clear section headers and no nested references, but organization gaps remain: "Backblaze Overview" is a contentless bullet list (Bucket / File / B2 Account), "Searching for actions" and "Popular actions" duplicate the same `action list` command, and "Running actions" is oddly nested under "Popular actions". This matches anchor 3 (some structure, could be better organized) rather than 4.	3 / 5
	Total	13 / 20 Passed

Description

52%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 distinct and trigger-safe thanks to the Backblaze brand name, but it undersells the skill with vague capability language ("Manage data, records, and automate workflows") and omits domain-specific vocabulary like B2, buckets, or backups. Both a sharper "what" and richer trigger terms would raise it substantially.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities, e.g. "Manage B2 buckets, upload and download files, list bucket contents, and retrieve account records".

Expand trigger terms to include natural synonyms users would say: "B2", "backup", "bucket", "cloud storage" — e.g. "Use when the user mentions Backblaze, B2, buckets, or backup storage".

Make the "when" clause more specific about the interaction types (reading vs. writing data, running operations on records) so it discriminates among use cases.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Backblaze integration") but its actions are generic — "Manage data, records, and automate workflows" conveys no concrete capability. It matches anchor 2 ("Names the domain but actions are minimal or generic") rather than 3, which requires 1-2 concrete actions like buckets, backups, or B2 file operations.	2 / 5
Completeness	An explicit trigger clause is present ("Use when the user wants to interact with Backblaze data"), but the "what" is too vague to clearly describe the skill's capabilities. It sits above anchor 3's missing-when example yet below anchor 4, whose example pairs a concrete what with a when; the vague what keeps it at 3.	3 / 5
Trigger Term Quality	"Backblaze" is the natural keyword and appears twice, but common variations and synonyms users would say — "B2", "backup", "bucket", "cloud storage" — are absent, and "data"/"records" are generic filler. This matches anchor 3 (some relevant keywords, missing common variations) rather than 4's broader coverage.	3 / 5
Distinctiveness Conflict Risk	Every clause is anchored on the specific brand "Backblaze", giving a clear niche with a distinct trigger term and minimal conflict risk with other skills. It matches anchor 5; anchor 4 would require some plausible overlap with a closely related skill, which is not the case.	5 / 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/backblaze/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

backblaze

Table of Contents

Is this your skill?