Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

processes

Background jobs, long-running processes, and task management

Quality

67%

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 ./src/skills/bundled/processes/SKILL.md

Quality

Content

72%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 content is highly actionable with clean executable examples and good token efficiency, but it lacks validation checkpoints for its destructive batch operations and keeps the entire API reference inline rather than splitting it across referenced files.

Suggestions

Add a verification step after stop/stopAll/restart (e.g. check status is 'stopped' and confirm exit code) to satisfy the destructive-operations workflow cap.

Move the bulk TypeScript API reference into a separate REFERENCE.md and keep only a quick-start excerpt in SKILL.md with a clearly signaled link.

Add an error-recovery sequence (e.g. on 'failed' status, inspect logs then decide whether to restart) with explicit feedback-loop checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean API reference with executable code and minimal over-explanation of concepts Claude already knows; it only has minor redundancy such as overlapping spawn and status/list examples that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready TypeScript and chat-command examples covering spawn, list, status, output streaming, stop, restart, and event handling, fully executable across the common cases.	5 / 5
Workflow Clarity	Despite managing batch/destructive operations (stop, stopAll, force kill), the content has no validation or verification checkpoints and is organized by API endpoint rather than as a sequenced workflow, so the rubric's destructive-operations cap limits this to 3.	3 / 5
Progressive Disclosure	With no bundle files, the full ~250-line API reference is inlined in SKILL.md with section headers but no one-level-deep references or signaled navigation, so structure is present yet content that belongs in a separate reference file is not split out.	3 / 5
	Total	15 / 20 Passed

Description

48%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 clearly identifies its domain but states no concrete capabilities and omits any explicit 'when to use' trigger guidance, capping its completeness. Adding concrete verbs and a Use-when clause would move it toward the top anchors.

Suggestions

Add concrete actions, e.g. 'Spawn, monitor, stop, and restart background jobs and long-running processes'.

Append an explicit trigger clause such as 'Use when the user wants to run commands in the background, manage long-running jobs, or schedule tasks'.

Include natural user phrasings and synonyms ('run in background', 'start a job', 'keep a process alive') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description 'Background jobs, long-running processes, and task management' names the domain but uses no concrete action verbs (e.g. spawn, monitor, stop), matching the anchor for minimal/generic actions rather than the pure-vagueness of score 1.	2 / 5
Completeness	It gives a clear 'what' but entirely lacks a 'Use when...' or equivalent trigger clause, so per the rubric guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like 'background jobs', 'long-running processes', and 'task management' are relevant but miss common user phrasings such as 'run a command in the background' or 'start a job', so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Process and background-job management is a fairly distinct niche with only minor overlap risk against generic execution skills, fitting 'mostly distinct' better than the broad-overlap lower anchors.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/processes/SKILL.md
Revision: c930628

Reviewed: 1 month ago

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.

processes

Table of Contents

Is this your skill?