CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A well-structured, actionable skill with executable examples and tight prose. Its weaknesses are a missing validation/feedback-loop for batch job operations and a referenced details file that is not actually bundled.

Suggestions

Add an explicit validate/retry checkpoint workflow for batch job processing (e.g., enqueue -> poll status -> on failure inspect DLQ and retry/backoff) to raise workflow clarity.

Either create references/details.md with the promised 'Advanced Patterns' content or remove the dangling reference so progressive disclosure points to a real file.

Consider folding the 'Best Practices Summary' into a concise verification checklist tied to the patterns above so it functions as a feedback loop rather than a loose list.

DimensionReasoningScore

Conciseness

Lean body with executable code and minimal preamble; it does not re-explain basic concepts Claude already knows. Brief inline comments earn their place.

3 / 3

Actionability

Provides complete, executable Python (Celery config, retry/backoff, idempotency, job repository) that is copy-paste ready with specific settings and strategies.

3 / 3

Workflow Clarity

Content is a patterns catalog rather than a sequenced fragile workflow, and for batch/queue operations there is no explicit validate-fix-retry checkpoint, capping it at 2.

2 / 3

Progressive Disclosure

It signals a one-level-deep reference ('references/details.md') for advanced patterns, but that file/bundle does not exist, so the referenced path is dangling.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that names concrete capabilities and provides explicit, natural trigger guidance for both what and when. Third-person voice is maintained throughout. No significant weaknesses.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'task queues, workers, and event-driven architecture' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does (background job patterns) and when to use it via a 'Use when ...' clause.

3 / 3

Trigger Term Quality

Natural user-facing triggers like 'async task processing, job queues, long-running operations, or decoupling work from request/response cycles' that a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

Clear niche (background jobs/task queues) with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
wshobson/agents
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.