Name: filestack
Rating: 61.6 (1 reviews)
Author: membranedev

filestack

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

Quality

73%

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

Quality

Content

88%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 strong, actionable CLI integration guide with concrete commands, explicit state-validation feedback loops, and clear sequencing. Its only real weaknesses are minor over-explanation in the intro and a monolithic single-file structure with a thin 'Popular actions' section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and operational detail, but the opening paragraph explaining what FileStack is and some explanatory prose around clientAction states could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, poll, action list/run, proxy) with complete flag syntax and a parameter table.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear, with explicit validation checkpoints (state checks for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (poll with --wait, re-poll after user action).	5 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no nested references, but everything is inlined in a single ~156-line file with no external reference files, and the 'Popular actions' section is largely a pointer rather than substantive content.	4 / 5
	Total	18 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when' trigger and names the target service, making it reasonably complete and distinct. Its main weakness is generic action language ('Manage data, records, and automate workflows') that fails to convey FileStack's concrete file-handling capabilities.

Suggestions

Replace generic verbs with concrete FileStack capabilities, e.g. 'Upload, transform, and deliver files via FileStack; manage file content, metadata, folders, and shared links.'

Add natural file-handling trigger terms users would say, such as 'files', 'uploads', 'image transformations', or 'shared links'.

Tighten the 'what' so it mirrors the body's actual capabilities rather than the abstract 'manage data, records, and automate workflows'.

Dimension	Reasoning	Score
Specificity	The description names the FileStack domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete file-handling operations like uploading, transforming, or delivering files.	2 / 5
Completeness	Both 'what' (FileStack integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with FileStack data') are present, though the 'what' could be more concrete.	4 / 5
Trigger Term Quality	'FileStack' and 'FileStack data' are natural trigger terms, but common file-handling synonyms users would say (upload, transform, files, images) are missing.	3 / 5
Distinctiveness Conflict Risk	The FileStack-specific trigger gives it a clear niche with minimal conflict risk, though the generic 'data, records, workflows' phrasing creates minor overlap with broad data-management skills.	4 / 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/filestack/SKILL.md
Commit: f484c82

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