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

Blog Docs Log inGet started

webiny-api-file-manager-catalog

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

Quality

66%

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-formatted, actionable lookup catalog: every abstraction has a copy-paste import and exact source path, and the usage sequence is clear. Its main weakness is structural — the entire 48-entry catalog lives inline in SKILL.md with no reference files, and import boilerplate is repeated verbatim across entries.

Suggestions

Split the catalog into per-module reference files (e.g., references/assetDelivery.md, references/file.md, references/settings.md) and keep SKILL.md as a short index with one-level-deep, clearly signaled links.

Compress repeated import boilerplate by stating each module's import path once (e.g., 'All abstractions below: import from "webiny/api/file-manager/assetDelivery"') instead of repeating it in all ~45 entries.

Add one short executable example showing how an abstraction is actually used (e.g., implementing a FileBeforeCreateEventHandler), since the pattern skills are referenced but no inline usage is demonstrated.

Dimension	Reasoning	Score
Conciseness	The body contains zero over-explanation and every catalog entry is terse, load-bearing metadata (Name/Import/Source). It is not a 5 because ~45 entries repeat only two distinct import paths verbatim ('webiny/api/file-manager/assetDelivery' and 'webiny/api/file-manager/file'), which could be compressed by stating the import path once per module.	4 / 5
Actionability	Each entry provides a copy-paste-ready import statement, an exact source file path, and the 'How to Use' section mandates reading the source and points to two pattern skills. Not a 5 because there is no usage example (e.g., how to register an event handler or invoke a use case) covering the common cases.	4 / 5
Workflow Clarity	'How to Use' lays out a clear 4-step sequence (find abstraction → read source → import → consult pattern skills) that is unambiguous for this lookup task. Not a 5 because the skill exceeds the simple-skill line and minor gaps remain (e.g., no guidance when multiple abstractions match or a source path is not found); no validation steps are needed since nothing destructive or batch-oriented is performed.	4 / 5
Progressive Disclosure	There are no bundle files at all, and ~310 lines of API catalog are inlined in SKILL.md under only two section headers. The consistent entry format provides some structure (above anchor 2's 'no section headers' example), but content that clearly belongs in per-module reference files (assetDelivery, file, settings, permissions) is inlined with no split, capping it at 3.	3 / 5
	Total	15 / 20 Passed

Description

45%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 terse and names its domain, but it reads as a table-of-contents label rather than a capability statement. It lacks any 'when to use' trigger guidance and omits the project name, limiting both completeness and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when working with the Webiny File Manager API, implementing file upload/delete/update flows, or hooking into file lifecycle events.'

Replace the category labels with concrete capability phrases: 'Find and import file event handlers and use cases (create, update, delete, batch upload) with exact import paths and source locations.'

Include the project name 'Webiny' and natural user phrases (file lifecycle, file upload hooks, batch file creation) to improve trigger term coverage and reduce conflict risk with generic file-management skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("API — File Manager — 48 abstractions") but offers only category labels ("File event handlers and use cases") rather than concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete action verb phrases (e.g., 'hook into file lifecycle events' or 'import use cases') are stated.	2 / 5
Completeness	The 'what' is stated reasonably clearly (a catalog of 48 abstractions covering file event handlers and use cases), but there is no 'Use when...' clause or any equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline. Not a 2 because the 'what' is more specific than 'vague'.	3 / 5
Trigger Term Quality	It includes some relevant keywords ("file manager", "event handlers", "use cases") but misses the natural phrases users would actually say, such as 'upload a file', 'hook into file creation', or any project name like 'Webiny'. Better than anchor 2 ('Works with files') but lacks synonym and variation coverage for a 4.	3 / 5
Distinctiveness Conflict Risk	"API — File Manager" scopes the skill to a specific API area, but the description omits the project/brand name (Webiny), so it could still overlap with generic file-management or other API catalog skills. Somewhat specific, but not 'mostly distinct' enough for a 4.	3 / 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: f0d3d3e

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