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 provides the skill's name and category without any substantive content. It lacks concrete actions, natural trigger terms, explicit usage guidance, and distinguishing details. The trigger terms are a duplicate of the skill name, providing no additional matching value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates background worker classes, configures job queues, sets up retry logic, and implements scheduled tasks for asynchronous processing.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create background jobs, async workers, job queues, task scheduling, Sidekiq workers, Celery tasks, or delayed job processing.'
Remove the duplicate trigger term and replace with varied natural language terms users would actually say, such as 'async task', 'job queue', 'worker process', 'background processing', 'scheduled job'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Background Worker Creator') without describing any concrete actions. There are no specific capabilities listed such as creating job queues, scheduling tasks, or configuring worker processes. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of what the skill actually does beyond its name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('background worker creator, background worker creator'). It lacks natural user terms like 'job queue', 'async task', 'worker process', 'Sidekiq', 'Celery', 'cron job', or 'background job'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other backend development skills. 'Background Worker Creator' could overlap with task scheduling, queue management, or general backend development skills without clear boundaries. | 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—a template placeholder that contains no actual technical content about creating background workers. It repeatedly references 'background worker creator' without ever defining what a background worker is in this context, how to create one, or providing any code, commands, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Replace the abstract meta-descriptions with concrete, 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 goroutine-based worker in Go).
Add a clear multi-step workflow: e.g., 1) Define the job/task, 2) Set up the queue/broker, 3) Implement the worker, 4) Add error handling/retries, 5) Validate with a test job—with specific commands and validation checkpoints.
Remove all the 'When to Use' and 'Example Triggers' sections that just repeat the skill name, and use that space for actual technical patterns like retry strategies, dead letter queues, graceful shutdown, and idempotency.
Add references to supporting files for language-specific implementations (e.g., 'See [PYTHON_WORKERS.md](PYTHON_WORKERS.md) for Celery/RQ patterns') to provide progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'background worker creator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of actual background worker implementations. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. Sections exist but contain no real content differentiation. There are no references to detailed materials, examples, or supporting files. | 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
c8a915c
- 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.