Name: filebase
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

filebase

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

Quality

61%

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/filebase/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.

This is a solid, command-rich CLI integration skill with good structure and actionable guidance. It loses points for some unnecessary conceptual preamble, placeholder-only examples, and missing validation steps around destructive proxy/action operations.

Suggestions

Add at least one fully worked example (real connectionId, a concrete QUERY intent, an actionId, and sample JSON output) so commands are copy-paste runnable end-to-end.

Insert a validation/confirm checkpoint before destructive or batch operations, e.g. dry-run or confirm before `membrane action run` and before proxy `-X DELETE/PUT` requests.

Trim the blockchain platform preamble and the skeletal Overview bullet list, and fold the redundant "Popular actions" section into "Searching for actions" to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, command-driven prose, but includes unnecessary explanation Claude already knows ("Filebase is a decentralized storage platform built on top of multiple blockchain storage networks...") and a thin, oddly-skimpy Overview bullet list that could be trimmed.	3 / 5
Actionability	It provides many concrete, executable commands (install, login, connection ensure, action list/run, request) plus a proxy-flags table, but commands rely on placeholders (CONNECTION_ID, actionId, QUERY) with no worked example showing real values and sample output.	4 / 5
Workflow Clarity	The connect→poll→handle-state→search→run sequence is clear and state-aware, but action runs and proxy requests (POST/PUT/DELETE) are potentially destructive or batch with no validation checkpoints, capping clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no bundle files, though the redundant "Popular actions" section partly restates "Searching for actions".	4 / 5
	Total	14 / 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 third-person and covers both what and when, with a clear Filebase niche. Its main weakness is generic, abstract action language and a thin trigger clause lacking natural synonyms.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Filebase capabilities such as creating buckets, uploading objects, listing storage, and automating workflows via actions.

Expand the trigger clause with natural user phrases, e.g. "Use when the user wants to manage Filebase buckets, upload or retrieve objects, or automate Filebase storage workflows."

Add file-type or platform qualifiers (e.g. S3-compatible buckets, decentralized storage) to sharpen distinctiveness from general data skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Filebase domain and a few actions, but the actions are generic abstractions rather than concrete capabilities like bucket or object operations.	3 / 5
Completeness	It states both what ("Filebase integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Filebase data"), but the when-clause is generic rather than a concrete trigger phrase.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Filebase data" includes the core keyword "Filebase" and "data", but lacks natural synonyms or common variations a user might say (e.g. buckets, objects, storage).	3 / 5
Distinctiveness Conflict Risk	Naming the specific Filebase platform gives it a clear niche with low conflict risk, but the generic "manage data/records/automate workflows" phrasing could still overlap with broad data-management skills.	4 / 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/filebase/SKILL.md
Commit: f484c82

Reviewed: 5 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.