CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-tasks-catalog

api/tasks — 2 abstractions.

50

Quality

53%

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

Quality

Content

86%Weight 40%Scale 1-5

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 tight, well-structured catalog: a concise How to Use workflow followed by two abstractions with concrete imports and source paths. Its main weakness is actionability, since it deliberately offloads the actual interface to the source files rather than showing usage.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line (How to Use steps, Name/Import/Source/Description entries) earns its place, matching the 'Lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Each abstraction provides copy-paste-ready import statements and concrete source paths, but defers the exact interface/types to the source file ('You MUST read the source file'), leaving a minor gap; fits anchor 4 rather than 5 because no usage example beyond the import is shown.

4 / 5

Workflow Clarity

The How to Use section is a clear 4-step numbered sequence (find → read source → import → consult pattern skills) with unambiguous ordering; no validation checkpoints are present, but none are required for a non-destructive catalog, so it sits at anchor 4 rather than 5's explicit-validation anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files requiring navigation, and is organized into clear 'How to Use' and 'Abstractions' sections with external pointers (pattern skills, source files) clearly signaled at one level deep, satisfying the simple-skills exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

21%Weight 40%Scale 1-5

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 a terse, jargon-only label that names the api/tasks domain and abstraction count but provides no concrete actions, no natural trigger terms, and no use-when guidance. It is distinguishable by namespace yet weak on completeness and trigger quality.

Suggestions

Add concrete actions, e.g. 'Define and trigger long-running background tasks in the Webiny api/tasks namespace'.

Append an explicit 'Use when...' clause with natural triggers users would say, such as 'Use when building or invoking Webiny background tasks, cron jobs, or task lifecycle hooks'.

Replace the bare catalog label with a third-person capability statement that states both what the skill catalogs and when to reach for it.

DimensionReasoningScore

Specificity

The description names the domain ('api/tasks') and a count ('2 abstractions') but describes zero concrete actions, matching the 'Names the domain but actions are minimal or generic' anchor; it is not a 1 because the domain is explicitly named rather than being entirely vague.

2 / 5

Completeness

It offers a vague 'what' (a catalog of 2 abstractions under api/tasks) and no 'when'/trigger guidance, matching anchor 2; the missing 'Use when...' clause also caps completeness below 3 per the guidelines.

2 / 5

Trigger Term Quality

'api/tasks — 2 abstractions' is pure technical jargon with no natural keywords a user would actually say, matching the 'No natural keywords; only technical jargon' anchor exactly.

1 / 5

Distinctiveness Conflict Risk

The 'api/tasks' namespace pins a specific domain (low conflict with unrelated skills) but the terse phrasing could overlap with sibling webiny catalog skills, fitting 'Somewhat specific but could still overlap with similar skills'; not 4 because no distinct trigger phrases are given.

3 / 5

Total

8

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.