Name: webiny-infra-catalog
Rating: 47.2 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-infra-catalog

Infrastructure — 30 abstractions. Infrastructure extensions.

Quality

50%

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/infra/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 an efficient, well-structured abstraction catalog with copy-paste imports, source paths, and a clear usage workflow including a verification checkpoint. It assumes Claude's competence and adds only novel, actionable information.

Dimension	Reasoning	Score
Conciseness	The body is a lean catalog of Name/Import/Source triples with no concept over-explanation, so every token earns its place.	3 / 3
Actionability	Each entry provides an exact copy-paste import statement and a concrete source path, giving fully executable guidance.	3 / 3
Workflow Clarity	The 'How to Use' section gives an unambiguous 3-step sequence with an explicit verification checkpoint ('You MUST read the source file to get the exact interface and types').	3 / 3
Progressive Disclosure	No bundle files exist; content is organized into a flat, single-level catalog under clear sections, which is appropriate for this self-contained reference skill.	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 minimal and abstract, conveying little beyond an abstraction count and the word 'extensions' with no concrete actions, trigger terms, or use-when guidance. It fails to tell Claude what the skill does or when to invoke it.

Suggestions

Name concrete actions the skill supports, e.g. 'Extends Webiny infrastructure build/deploy hooks and stack-output services'.

Add a 'Use when...' trigger clause, e.g. 'Use when wiring custom build/deploy hooks or stack-output services for Webiny's admin/api/core stacks'.

Replace the generic 'Infrastructure' framing with distinct keywords (Webiny infra hooks, Admin/API/Core build & deploy, stack output services) to reduce conflict with other skills.

Dimension	Reasoning	Score
Specificity	The description only states 'Infrastructure — 30 abstractions.' and 'Infrastructure extensions.' — it names no concrete actions, only an item count and the abstract noun 'extensions'.	1 / 3
Completeness	It gives only a vague 'what' and entirely omits any 'when'/'Use when...' trigger guidance, so both halves are weak or missing.	1 / 3
Trigger Term Quality	No natural trigger terms a user would say appear; 'Infrastructure' is generic technical framing rather than user-facing keywords like 'build', 'deploy', or 'webiny infra'.	1 / 3
Distinctiveness Conflict Risk	'Infrastructure' is so generic it would overlap with many other skills and lacks any distinct trigger that would route the user to this catalog.	1 / 3
	Total	4 / 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/infra/SKILL.md
Commit: 484553b

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