processes
Background jobs, long-running processes, and task management
65
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/processes/SKILL.mdQuality
Discovery
22%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 too vague and incomplete to effectively guide skill selection. It names a general domain but fails to specify concrete actions Claude can perform or provide explicit trigger conditions. Without a 'Use when...' clause and specific capabilities, Claude would struggle to distinguish this skill from related ones.
Suggestions
Add specific concrete actions like 'Queue background jobs, monitor task status, schedule recurring processes, manage worker pools'
Include a 'Use when...' clause with explicit triggers such as 'Use when the user mentions background jobs, async tasks, job queues, workers, cron jobs, or scheduled processes'
Add common user-facing terms and file/technology references like 'Celery', 'Sidekiq', 'cron', 'async', 'queue' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('background jobs', 'long-running processes', 'task management') without listing any concrete actions like 'start', 'monitor', 'queue', or 'schedule'. | 1 / 3 |
Completeness | Only partially addresses 'what' with vague domain terms, and completely lacks any 'when' guidance or 'Use when...' clause to indicate when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('background jobs', 'long-running processes', 'task management') that users might say, but misses common variations like 'async', 'queue', 'worker', 'cron', 'scheduled tasks', or 'job scheduler'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Task management' is generic and could overlap with project management or todo list skills; 'long-running processes' could conflict with deployment or monitoring skills. The domain is somewhat specific but boundaries are unclear. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-written API reference with excellent actionability and conciseness - code examples are complete and immediately usable. However, it functions more as documentation than a skill, lacking workflow guidance for common scenarios like debugging failed jobs or validating process health. The monolithic structure would benefit from progressive disclosure to separate quick-start content from detailed API reference.
Suggestions
Add a workflow section showing the typical job lifecycle: spawn -> monitor -> handle failure/success, with explicit validation steps
Split into overview SKILL.md with quick-start examples, linking to separate API_REFERENCE.md and USE_CASES.md files
Add error handling patterns showing how to detect and recover from common failures (OOM, timeout, crash loops)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting API reference material without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, with complete function signatures, options objects, and realistic use cases. Chat commands are also concrete and immediately usable. | 3 / 3 |
Workflow Clarity | While individual API methods are clear, the skill lacks explicit validation checkpoints for process management operations. No guidance on verifying job success, handling failures mid-workflow, or feedback loops for debugging failed jobs. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a lengthy API reference (200+ lines) that could benefit from splitting into separate files (e.g., CHAT_COMMANDS.md, API_REFERENCE.md, USE_CASES.md) with a concise overview in the main skill. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.