CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-tasks-catalog

api/tasks — 2 abstractions.

40

Quality

40%

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

72%

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 clean, well-organized catalog that is appropriately concise and uses one-level-deep pointers effectively. Its main weakness is actionability: it hands off the actual interface and usage details to external source files rather than showing an executable example.

Suggestions

Add a minimal executable usage example for TaskDefinition and TaskService so the skill is copy-paste ready without reading external source.

Include the key interface surface (e.g. primary methods or lifecycle hook signatures) inline rather than requiring a source-file read.

Add a brief validation/sanity step (e.g. confirm the imported name resolves) to lift workflow clarity above 2.

DimensionReasoningScore

Conciseness

The body is lean and free of padding: each line (import, source path, one-line description) earns its place and assumes Claude's competence with no restated concepts.

3 / 3

Actionability

Concrete import statements and source paths are provided, but the skill explicitly defers interface/types/usage to the source file ('You MUST read the source file') and offers no executable usage example, so guidance is incomplete.

2 / 3

Workflow Clarity

The 'How to Use' steps are clearly sequenced (find -> read source -> import -> see pattern skills), but there are no validation checkpoints; for this multi-step lookup it sits at the 'steps listed, checkpoints implicit' anchor.

2 / 3

Progressive Disclosure

Content is well-organized into 'How to Use' and 'Abstractions' sections with one-level-deep, clearly signaled pointers (source files and pattern skills) and no nested references.

3 / 3

Total

10

/

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 to function as an effective trigger: it names a domain and abstraction count but provides no actions, no natural user-facing keywords, and no use-when guidance. It reads as an internal label rather than a discoverable skill description.

Suggestions

Add concrete actions the skill enables, e.g. 'Define and trigger long-running background tasks via TaskDefinition and TaskService'.

Include a 'Use when...' clause with natural trigger terms such as 'background tasks', 'long-running tasks', or 'task lifecycle hooks'.

Spell out the domain in user-facing language instead of the bare path 'api/tasks' so it is distinguishable from other webiny-api skills.

DimensionReasoningScore

Specificity

The phrase "api/tasks — 2 abstractions" names a domain and a count but describes no concrete actions; it does not meet the 'names domain and some actions' bar for a 2.

1 / 3

Completeness

The 'what' is only vaguely hinted and the 'when' (Use when...) is entirely absent, so both halves are weak as required for a 1.

1 / 3

Trigger Term Quality

Terms like "api/tasks" and "abstractions" are technical jargon a user would not naturally say; there are no natural-language trigger keywords.

1 / 3

Distinctiveness Conflict Risk

The api/tasks scope gives it a somewhat specific niche, but the terse description with no distinct triggers could overlap with sibling webiny-api 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.