Name: filescom
Rating: 60.8 (1 reviews)
Author: membranedev

filescom

Files.com integration. Manage Files, Folders, Users, Groups, Permissions, Shares and more. Use when the user wants to interact with Files.com data.

Quality

71%

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

Quality

Content

65%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.

Highly actionable CLI guidance with concrete commands and tables, but it carries a padded intro and a large inline catalog, has incoherent workflow numbering, and omits validation guidance around destructive operations.

Suggestions

Add a confirmation/validation checkpoint before destructive runs, e.g. 'Before delete-file/delete-user/delete-group, verify the target with a get-* call and confirm with the user'.

Fix the broken step numbering: replace '1b' with a proper '1a/1b' pair or renumber the connect → search → run sections as explicit numbered steps including the missing 'Step 2'.

Move the 45-item entity list and/or the full action catalog into a reference file (e.g. references/actions.md) and keep SKILL.md as a lean overview that links to it.

Dimension	Reasoning	Score
Conciseness	The marketing intro ("Files.com is a secure file management and automation platform. It's used by businesses of all sizes...") and the ~45-item inline entity bullet list explain context Claude can infer and consume tokens that could be trimmed or offloaded.	3 / 5
Actionability	Copy-paste-ready commands throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action list/run`, `membrane request` — plus a flags table and a 20-row action catalog covering the common cases.	5 / 5
Workflow Clarity	A sequence exists (install → auth → connect → search → run) with polling checkpoints for connection state, but step numbering is incoherent (a referenced "Step 2" and a "1b" with no "1a"/"Step 2"), and destructive `delete-file`/`delete-user`/`delete-group` actions are listed with no confirmation/validation checkpoint, capping this at 3.	3 / 5
Progressive Disclosure	Sections are well-organized, but at ~200 lines with a 45-item entity list and a 20-row action table all inlined and zero external references (no references/scripts/assets bundle), content that could be split into a reference file is not, so it falls short of the well-split anchor 4.	3 / 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.

A clear, third-person description that names the product and several managed entities and includes an explicit 'Use when' trigger. It is distinctive but would benefit from more concrete action verbs and additional trigger phrasing to reach the top anchor.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, list, update, and delete Files, Folders, Users, Groups, Permissions, and Shares'.

Expand the 'Use when' clause with more specific triggers, e.g. 'Use when the user wants to list, share, or manage Files.com files, folders, users, or permissions'.

Drop 'and more' — it is vague filler that adds no trigger value.

Dimension	Reasoning	Score
Specificity	"Manage Files, Folders, Users, Groups, Permissions, Shares and more" lists several specific managed entities, but the single generic verb "Manage" leaves the concrete actions (create/list/update/delete) un-enumerated, so it sits just below the comprehensive-anchor 5.	4 / 5
Completeness	Both halves are present — a clear "what" ("Manage Files, Folders, Users, Groups, Permissions, Shares") and an explicit "Use when the user wants to interact with Files.com data" — but the single, somewhat generic when-clause is less concrete than anchor 5's multiple trigger phrases.	4 / 5
Trigger Term Quality	The product name "Files.com" plus entity keywords (Files, Folders, Users, Groups, Permissions, Shares) give good natural-term coverage a user would say, though a few synonyms/variations are missing relative to the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Files.com" is a specific named product with entity-specific triggers, giving a clear niche and minimal conflict risk with other skills.	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/filescom/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.