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.
32
Quality
3%
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
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.
This description is essentially a placeholder with no substantive content. It merely restates the skill name without explaining what actions the skill performs, what technologies it works with, or when Claude should select it. The repeated trigger term adds no value and the description would fail to help Claude distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions like 'Creates background job processors, configures task queues, implements retry logic, and sets up scheduled workers for frameworks like Sidekiq, Celery, or Bull'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions background jobs, async tasks, job queues, worker processes, scheduled tasks, cron jobs, or task processing'
Remove the duplicate trigger term and expand to include technology-specific terms users might mention (e.g., 'Redis queue', 'message broker', 'job scheduler')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Background Worker Creator' without describing any concrete actions. There are no specific capabilities listed like 'creates job queues', 'schedules tasks', or 'manages async processes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'background worker creator' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'job queue', 'async task', 'scheduled job', 'worker process', 'cron job'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'background worker' is somewhat specific to a particular backend pattern, the lack of detail means it could overlap with general backend development skills, task scheduling skills, or queue management skills. | 2 / 3 |
Total | 5 / 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 template that provides no actual value. It contains only generic placeholder text describing what a skill should do rather than providing any concrete guidance on creating background workers. The content fails on all dimensions by being verbose yet content-free, completely non-actionable, and lacking any workflow or structural organization.
Suggestions
Add concrete, executable code examples for creating background workers in at least one language (Node.js, Python, or Go) with a specific framework like Celery, Bull, or Temporal
Define a clear workflow with steps: 1) Choose worker pattern, 2) Set up queue/broker, 3) Implement worker logic, 4) Add error handling/retries, 5) Deploy and monitor
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific patterns like job queues, scheduled tasks, or event-driven workers
Add references to detailed documentation for different worker types (e.g., CELERY.md, BULL.md) with clear navigation signals
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about background workers. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually create a background worker in any language or framework. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for creating background workers. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no references to detailed documentation, examples, or related files. It mentions 'Related Skills' but provides no actual links or navigation structure. | 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
994edc4
- 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.