CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-aco-catalog

admin/aco — 2 abstractions.

44

Quality

46%

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

Quality

Content

85%

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-organized catalog of two ACO hooks with correct imports and source pointers, and a clear simple workflow. Its main weakness is actionability: it delegates the actual hook interfaces and usage to the source files rather than including them.

Suggestions

Include the signature/return type or a minimal usage snippet for each hook so Claude can use them without opening the source.

If interface details are intentionally deferred, add a one-line description of what each hook returns or does alongside the import line.

DimensionReasoningScore

Conciseness

The body is a lean catalog: a 3-step usage list plus name/import/source lines per abstraction, with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It provides concrete import statements and exact source paths, but it explicitly punts the actual interface/types to the source file ('You MUST read the source file') and shows no executable usage example of the hooks, so guidance is incomplete.

2 / 3

Workflow Clarity

The 'How to Use' section gives a clear, unambiguous 3-step sequence (find abstraction, read source, import); as a simple single-purpose skill this satisfies the simple-skills allowance for a score of 3, and no destructive/batch validation checkpoint is needed.

3 / 3

Progressive Disclosure

The skill is well under 50 lines with no external bundle files (references/scripts/assets absent), and content is organized into clearly labeled sections (How to Use, Abstractions), meeting the simple-skills allowance for a score of 3.

3 / 3

Total

11

/

12

Passed

Description

7%

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 far too terse: it names a domain and a count of abstractions but conveys no capabilities, no usage triggers, and no natural keywords. It fails to tell Claude what the skill does or when to invoke it.

Suggestions

State concrete capabilities, e.g. 'Navigate ACO folders and read ACO records via React hooks'.

Add a 'Use when...' trigger clause naming natural terms users would say (e.g. 'Use when working with Webiny admin access-control folder navigation or record fetching').

Avoid relying on a raw count ('2 abstractions') as the substance of the description; describe what those abstractions accomplish.

DimensionReasoningScore

Specificity

The description only states 'admin/aco — 2 abstractions' which names a domain and a count but lists no concrete actions or capabilities, matching the vague/abstract anchor rather than the score-2 anchor that names actions.

1 / 3

Completeness

It answers neither 'what does this do' (only counts abstractions) nor 'when should Claude use it'; there is no 'Use when...' trigger clause, so it falls below even the what-without-when anchor.

1 / 3

Trigger Term Quality

'admin/aco' is technical jargon and '2 abstractions' is not a phrase a user would naturally say when they need this skill; there are no natural user-facing keywords.

1 / 3

Distinctiveness Conflict Risk

The 'admin/aco' niche is reasonably specific within Webiny, so it is unlikely to broadly conflict, but the bare phrasing gives no distinct triggers and could overlap with sibling Webiny admin skills.

2 / 3

Total

5

/

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.