Name: webiny-api-build-params-catalog
Rating: 49.6 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-build-params-catalog

api/build-params — 2 abstractions.

Quality

53%

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

Quality

Content

100%

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, token-efficient abstraction catalog that gives concrete import paths and source locations plus a clear usage sequence. It is an exemplary simple catalog skill with nothing padded or misplaced.

Dimension	Reasoning	Score
Conciseness	The body is a lean catalog with four compact fields per abstraction and a short numbered how-to; it explains no concepts Claude already knows and every line earns its place.	3 / 3
Actionability	Each abstraction ships a concrete copy-paste import ('import { BuildParam } from "webiny/api/build-params"'), an exact source path, and a one-line description; deferring interface/types to the source file is a deliberate, clearly signaled choice.	3 / 3
Workflow Clarity	The 4-step 'How to Use' sequence (find → read source → import → consult pattern skills) is unambiguous for a simple lookup skill, and no destructive or batch operation requires a validation checkpoint.	3 / 3
Progressive Disclosure	Under 50 lines with no bundle files, it is organized into clear 'How to Use' and 'Abstractions' sections and signals one-level-deep references (source files, sibling pattern skills) without nesting.	3 / 3
	Total	12 / 12 Passed

Description

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 essentially a path label plus an abstraction count, with no concrete actions, natural trigger terms, or use-when guidance. It is specific enough to a niche but fails to tell a user or Claude what it does or when to reach for it.

Suggestions

Add a verb-led capability statement, e.g. 'Catalogs the BuildParam and BuildParams abstractions from the Webiny api/build-params module and shows their import paths and source locations.'

Append an explicit trigger clause, e.g. 'Use when working with Webiny api/build-params build-time configuration or when you need the BuildParam/BuildParams import paths.'

Replace the bare path identifier with natural terms users would say (e.g. 'build-time configuration parameters', 'Webiny build params') to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	The phrase 'api/build-params — 2 abstractions' names a domain and a count but describes no concrete actions; '2 abstractions' is a tally, not a verb, so it falls at the 'no actions' anchor rather than the 'some actions' level 2.	1 / 3
Completeness	It gives only a bare category label with no statement of what the skill does and no 'Use when…' trigger, so both 'what' and 'when' are weak or missing.	1 / 3
Trigger Term Quality	Terms like 'api/build-params' and 'abstractions' are internal path/jargon identifiers a user would not naturally say, matching the 'technical jargon, no natural keywords' anchor.	1 / 3
Distinctiveness Conflict Risk	The module path names a specific niche, but '2 abstractions' is generic and sibling webiny-api catalog skills could overlap; without distinct natural triggers it is only 'somewhat specific'.	2 / 3
	Total	5 / 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/build-params/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.