python-background-jobs

Python background job patterns including task queues, workers, and event-driven architecture. Use when implementing async task processing, job queues, long-running operations, or decoupling work from request/response cycles.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/python-development/skills/python-background-jobs/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is code-rich and actionable with good progressive disclosure to a one-level-deep reference file. It is held back by a conceptual 'Core Concepts' preamble that over-explains known material and by the absence of a sequenced, validation-gated workflow.

Suggestions

Trim or remove the 'Core Concepts' section — idempotency, at-least-once delivery, and job state transitions are demonstrated directly in the code patterns and need no upfront definition.

Resolve the Pattern 3 `pass` stub and the `...` placeholder in the SQL UPDATE so every example is fully runnable.

Add an explicit end-to-end workflow with a validation checkpoint (e.g. enqueue -> persist job -> poll/verify terminal status) to lift workflow clarity above the batch-operation cap of 3.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with substantial executable code, but the 'Core Concepts' section restates concepts Claude already knows (idempotency, at-least-once delivery, state transitions) and the intro repeats the description; not a 4 because that conceptual padding is noticeable.	3 / 5
Actionability	Provides copy-paste-ready code across Quick Start and four patterns plus references/details.md; minor gaps (a `pass` stub in Pattern 3 and a `...` placeholder in the SQL update) keep it just below fully executable.	4 / 5
Workflow Clarity	Content is organized as parallel patterns rather than a sequenced Claude-executable workflow, and no validation/verification checkpoints exist; the batch/async-operation cap also limits this to 3.	3 / 5
Progressive Disclosure	Well-organized sections (When to Use, Quick Start, Fundamental Patterns, Best Practices) with a clearly signaled one-level-deep reference to references/details.md; not a 5 because the reference paragraph is slightly buried and some inlined patterns could live in the reference.	4 / 5
	Total	14 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 strong: it clearly states both what the skill covers and when to use it, with natural trigger terms and a distinct niche. The main weakness is specificity — it enumerates categories rather than concrete actions.

Suggestions

Replace category nouns ('task queues, workers, event-driven architecture') with concrete actions the skill performs (e.g. 'enqueue jobs, configure retries, poll job status, build task chains').

Add a couple of widely-used trigger terms users say, such as 'scheduled jobs', 'cron-like tasks', or 'Celery/RQ/Dramatiq'.

Dimension	Reasoning	Score
Specificity	Names the domain and several sub-areas ('task queues, workers, and event-driven architecture') but these are categories rather than concrete actions the skill performs, matching the 'domain + 1-2 concrete actions' anchor; not a 4 because no concrete verbs are enumerated.	3 / 5
Completeness	Explicitly states what it does ('Python background job patterns...') and when to use it with an explicit 'Use when...' clause and concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage with synonyms ('background job', 'job queues', 'task queues', 'async task processing', 'long-running operations'), though a few common terms (e.g. 'cron', 'scheduled jobs', 'Celery') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (background/async job processing) with distinct triggers and minimal conflict risk; not a 5 due to minor overlap with general async-programming or API-design skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/python-development/skills/python-background-jobs/SKILL.md
Commit: 367cb6a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.