Name: webiny-api-file-manager-catalog
Rating: 52 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-file-manager-catalog

API — File Manager — 48 abstractions. File event handlers and use cases.

Quality

56%

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/user-skills/generated/api/file-manager/SKILL.md

Quality

Content

71%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 well-structured, lean index of 48 abstractions with copy-paste import lines and a clear usage sequence, deferring interface details to source files. Its main weakness is progressive disclosure: no bundle files exist and the entire catalog is inlined rather than externalized.

Suggestions

Move the 48-entry abstraction catalog into a references file (e.g. references/abstractions.md) and keep SKILL.md as a concise overview with a single clearly-signaled pointer, improving progressive disclosure.

Add a brief per-category grouping (e.g. Asset Delivery, File CRUD, Settings, Lifecycle Events) so users can locate abstractions without scanning all 48 entries.

Optionally add a one-line usage snippet for the most common abstractions (e.g. a CreateFileUseCase example) so actionability does not depend solely on reading the source file.

Dimension	Reasoning	Score
Conciseness	Each entry is lean metadata (Name/Import/Source, occasionally Description) with no padding, and the body explicitly defers interfaces to source files ('You MUST read the source file'), assuming Claude's competence; only the sheer volume of 48 inline entries keeps it from a 5.	4 / 5
Actionability	Every abstraction ships a concrete, copy-paste-ready import statement and an exact source path, and the 'How to Use' steps are specific; the minor gap is that actual usage/types still require reading the source file.	4 / 5
Workflow Clarity	A clear 4-step numbered sequence (find → read source → import → consult pattern skills) is present and unambiguous; this is a non-destructive lookup skill so the batch/destruction cap does not apply, but there are no validation checkpoints to justify a 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets are empty) and the full 48-entry catalog is inlined in SKILL.md rather than split into a reference file, fitting the score-3 anchor of structure present but content that could be separate is inline; source-file pointers are one level deep but not via bundle references.	3 / 5
	Total	15 / 20 Passed

Description

41%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 identifies the domain and scope clearly but lacks concrete action verbs and any explicit 'Use when' trigger guidance, relying on technical jargon rather than natural user phrasing. It is reasonably distinct but under-specified for triggering.

Suggestions

Add an explicit 'Use when ...' clause naming concrete triggers, e.g. 'Use when implementing Webiny file-manager features such as uploads, file CRUD, asset delivery, or file/settings lifecycle hooks.'

Replace jargon ('abstractions', 'use cases') with concrete user-facing actions like 'upload, list, update, and delete files; deliver assets; hook into file/settings lifecycle events'.

Include natural synonyms and file/extension terms users might say (e.g. 'file upload', 'asset delivery', 'file lifecycle events') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('API — File Manager') and tallies '48 abstractions' but the only actions offered ('File event handlers and use cases') are generic categories rather than concrete actions, matching the score-2 anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	It states a clear 'what' (a catalog of 48 file-manager abstractions) but provides no 'Use when...' trigger guidance, so per the cap it cannot exceed 3; this matches the score-3 anchor of a clear 'what' with 'when' missing.	3 / 5
Trigger Term Quality	'File Manager' is a plausible keyword, but 'abstractions', 'use cases', and 'event handlers' are technical jargon users would not naturally say; missing the natural trigger phrases, fitting the score-2 anchor of one or two generic keywords.	2 / 5
Distinctiveness Conflict Risk	Scoped to the Webiny file-manager API with a concrete niche (asset delivery, file CRUD, settings), giving it mostly distinct triggers with only minor overlap risk against other webiny-api skills.	4 / 5
	Total	11 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/file-manager/SKILL.md
Commit: d98a4e8

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