background-worker-creator
Background Worker Creator - Auto-activating skill for Backend Development. Triggers on: background worker creator, background worker creator Part of the Backend Development skill category.
29
0%
Does it follow best practices?
Impact
77%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/background-worker-creator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that essentially only restates the skill name without providing any concrete capabilities, trigger terms, or usage guidance. It reads like an auto-generated placeholder rather than a functional skill description. It would be nearly impossible for Claude to correctly select this skill from a pool of backend development skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates background workers and job processors using frameworks like Sidekiq, Celery, or Bull. Implements job queues, retry logic, scheduling, and error handling for asynchronous tasks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about background jobs, async workers, job queues, task scheduling, Sidekiq, Celery, Bull, delayed jobs, or cron-based processing.'
Remove the duplicate trigger term ('background worker creator' is listed twice) and replace with diverse, natural keywords users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions whatsoever. 'Background Worker Creator' is a label, not a description of capabilities. There are no specific actions like 'creates job queues', 'schedules tasks', or 'implements retry logic'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and there is no 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name and provides no meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'background worker creator' repeated twice. No natural user language like 'job queue', 'async task', 'Sidekiq', 'Celery', 'cron job', 'background job', or 'worker process' is included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any backend development skill. 'Backend Development skill category' is extremely broad, and without specific triggers or capabilities, it's indistinguishable from other backend-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actionable content. It consists entirely of boilerplate meta-descriptions that repeat the phrase 'background worker creator' without ever providing any technical guidance, code examples, or concrete instructions for creating background workers. It fails on every dimension of the rubric.
Suggestions
Replace the boilerplate with actual executable code examples for creating background workers in at least one language (e.g., a Celery worker in Python, a Bull queue worker in Node.js, or a Go goroutine-based worker).
Add a concrete multi-step workflow: define the task, set up the queue/broker, implement the worker, add retry/error handling, and validate with a health check or test job.
Include specific patterns and anti-patterns for background workers (e.g., idempotency, graceful shutdown, dead letter queues, concurrency limits) instead of vague claims about 'best practices'.
If the skill is meant to cover multiple languages/frameworks, create a concise overview with references to separate files (e.g., PYTHON_WORKERS.md, NODE_WORKERS.md) for detailed implementations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'background worker creator' excessively, and provides zero technical substance. Every token is wasted. | 1 / 3 |
Actionability | There is no concrete code, no commands, no specific examples, no executable guidance whatsoever. The skill describes what it could do in abstract terms but never actually instructs Claude how to create a background worker. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There is no sequence, no validation, no checkpoints—just vague claims like 'provides step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to detailed resources, no references to supporting files, and no meaningful organization of content across sections. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.