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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill background-worker-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill actually does or when Claude should select it. The description fails to meet basic requirements for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates background job processors, configures job queues, implements retry logic, and sets up scheduled tasks'
Include a 'Use when...' clause with natural trigger terms like 'async jobs', 'background tasks', 'job queue', 'worker process', 'scheduled jobs', 'Sidekiq', 'Celery', or 'cron jobs'
Specify the technologies or frameworks supported (e.g., Redis, RabbitMQ, specific language workers) to distinguish from other backend skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('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, and provides no 'when to use' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('background worker creator, background worker creator'). Missing natural user terms like 'async jobs', 'queue', 'scheduled tasks', 'cron', 'job processing', or 'background tasks'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'background worker' is somewhat specific to a domain, the lack of detail means it could overlap with general backend skills, job scheduling skills, or async processing skills without clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance on creating background workers. There is no code, no specific patterns, no technology-specific instructions, and no actionable content whatsoever.
Suggestions
Add concrete, executable code examples for creating background workers in at least one language (Node.js, Python, or Go) with a specific queue/job system like Bull, Celery, or similar
Define a clear workflow with steps: 1) Choose job queue, 2) Define worker function, 3) Configure retry/error handling, 4) Set up monitoring - with validation checkpoints
Include specific patterns for common background worker scenarios: email sending, image processing, data sync, with copy-paste ready implementations
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content about worker patterns, concurrency, idempotency, and failure handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about background workers. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code examples, no commands, and no specific instructions. The entire content describes what the skill supposedly does rather than instructing how to create background workers. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no links to related documentation. It mentions 'Related Skills' but provides no actual navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.