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

Blog Docs Log in Get started

webiny-api-aco-catalog

API — ACO — 30 abstractions. Folder event handlers and use cases.

Quality

57%

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

Quality

Content

65%

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, highly actionable catalog that nails its core job of giving exact imports and source paths, but it pays for that breadth in verbosity and keeps everything inline rather than splitting or compacting the 30-entry reference.

Suggestions

Collapse the 30 entries into a compact table (Name | Import | Source | Description) to roughly halve the token count while preserving every fact.

Add a one-line validation cue in 'How to Use' (e.g. confirm the imported symbol exists at the listed Source path before relying on it) so the workflow has an explicit checkpoint.

Move the full 30-entry catalog into a reference file (e.g. references/abstractions.md) and keep SKILL.md as a short overview with a one-level-deep pointer, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Each entry is lean (Name/Import/Source/one-line Description) with no concept padding, but the 30-entry vertical layout with blank-line-separated blocks and '---' dividers is markedly more verbose than a compact table would be, so it is mostly efficient but could be tightened.	2 / 3
Actionability	Every entry provides a fully executable, copy-paste-ready import statement (e.g. 'import { CreateFlpUseCase } from "webiny/api/aco/flp"') plus an exact source path, which matches the 'fully executable; copy-paste ready' anchor for the catalog's core deliverable.	3 / 3
Workflow Clarity	The 'How to Use' section gives a clear 4-step sequence, but two steps defer work out of the skill ('You MUST read the source file', 'See ... skills for implementation patterns') and there are no checkpoints, matching the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Sections are consistently organized, but the skill is a 230-line monolithic inline catalog with no bundle files; the 30-entry reference that 'should be separate is inline' fits the score-2 anchor rather than a well-split, one-level-deep structure at 3.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 identifies a niche domain and the kind of artifacts it catalogs, but it reads as a label rather than a functional description: it has no concrete actions and no explicit use-when trigger guidance.

Suggestions

Add a 'Use when...' clause stating when Claude should reach for this skill, e.g. 'Use when implementing or extending ACO folder features and you need the exact use case or event handler abstraction to import.'

Replace the abstract noun list with concrete verbs, e.g. 'Locate, import, and extend ACO folder use cases and lifecycle event handlers.'

Soften the jargon by pairing 'ACO' with a plain-language gloss (e.g. 'access-controlled folders') so users without the internal term can still trigger it.

Dimension	Reasoning	Score
Specificity	Quotes "Folder event handlers and use cases" name the domain (ACO) and action-adjacent categories, but no concrete verbs are listed, so it stops short of the multi-action anchor at 3 and clears the vague-only anchor at 1.	2 / 3
Completeness	It states what the skill is ("30 abstractions. Folder event handlers and use cases") but has no "Use when..." clause or equivalent trigger, so per the guidelines completeness is capped at 2 rather than reaching the explicit-trigger 3.	2 / 3
Trigger Term Quality	Terms like "folder" and "event handlers" are somewhat natural, but "ACO" is internal jargon and common user variations are absent, matching the 'some relevant keywords but missing common variations' anchor rather than the full-coverage 3.	2 / 3
Distinctiveness Conflict Risk	The webiny-api-aco niche is somewhat specific, but without explicit triggers the description could overlap with sibling webiny-api-* skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 12 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: webiny/webiny-js
Path: skills/user-skills/generated/api/aco/SKILL.md
Commit: 484553b

Reviewed: about 13 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.