CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-file-manager-catalog

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

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized, token-efficient abstraction catalog with clear import and source guidance and an unambiguous usage sequence. Its main gaps are missing usage examples (types deferred to source) and a large inline catalog that could be split into reference files.

Suggestions

Add a brief executable example showing how to invoke one use case or register one event handler so actionability reaches fully executable guidance.

Consider moving the 28-entry catalog (or per-feature groups) into a separate reference file and linking from the body to improve progressive disclosure for this over-50-line skill.

Keep the concise index style but ensure the "How to Use" steps explicitly mention verifying types against the read source as a lightweight validation checkpoint.

DimensionReasoningScore

Conciseness

The body is a token-efficient lookup index where every entry carries unique reference data (Name, Import, Source, Description) with no padding, no concept explanations, and no tutorials, matching "Lean and efficient; every token earns its place".

3 / 3

Actionability

Each abstraction provides a concrete, copy-paste import statement and a source path, but usage/invocation examples and type details are deferred to source, matching "Some concrete guidance but incomplete; missing key details".

2 / 3

Workflow Clarity

The 4-step "How to Use" sequence (find abstraction, read source for types, import, consult pattern skills) is clear and the single lookup action is unambiguous; per the simple-skill guideline an unambiguous single action warrants 3, and no destructive/batch feedback loop is required here.

3 / 3

Progressive Disclosure

The body has clear sections and signals two external pattern skills, but the large 28-entry catalog is inline with no split into reference files, matching "Some structure but content that should be separate is inline" rather than a 3.

2 / 3

Total

10

/

12

Passed

Description

57%

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 scopes the skill to the Webiny File Manager API and identifies its two abstraction categories, but it lacks explicit trigger guidance and the concrete actions a user would recognize. It is distinctive but not fully actionable as a discovery description.

Suggestions

Add a "Use when..." clause naming concrete user requests (e.g. implementing file uploads, file lifecycle hooks, or file manager settings in the Webiny API) to lift completeness.

Replace abstract phrasing with concrete verbs from the catalog (create, delete, update, list files/tags, manage settings) so the description lists multiple specific actions.

Include natural trigger terms such as "file upload", "file lifecycle events", "file manager settings", or "Webiny file storage" to improve trigger term quality.

DimensionReasoningScore

Specificity

The description names the domain and two abstraction categories ("File event handlers and use cases") but lists no concrete actions such as persist, retrieve, or delete, so it matches "Names domain and some actions, but not comprehensive" rather than a 3.

2 / 3

Completeness

It states a partial "what" (a catalog of file event handlers and use cases) but provides no "Use when..." trigger guidance for the "when", which the guidelines cap at 2; it is not a 1 because the "what" is present rather than very weak.

2 / 3

Trigger Term Quality

It carries the relevant keywords "API — File Manager" and "event handlers", but lacks the natural phrasings a user would say (e.g. "file upload", "file lifecycle", "Webiny file storage"), so it has some relevant keywords but misses common variations.

2 / 3

Distinctiveness Conflict Risk

Scoping to "API — File Manager" within the webiny-api context gives it a clear niche unlikely to trigger for unrelated skills, matching "Clear niche with distinct triggers" rather than merely "somewhat specific".

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
webiny/webiny-js
Reviewed

Table of Contents

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.