CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

background-agent-pings

Background Agent Pings

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/background-agent-pings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, actionable pattern with concrete tool-call specifics, a clear DO/DON'T contrast, and appropriate structure for a small single-purpose skill. Its only real slack is the redundant 'Why This Matters' and 'Source' sections, and the absence of guidance for failure cases.

DimensionReasoningScore

Conciseness

The body is lean and imperative, but '## Why This Matters' partially restates the DON'T block and '## Source' (session provenance) adds tokens that earn nothing — minor over-explanation that could be trimmed, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete guidance with real tool parameters (run_in_background=true, the .claude/cache/agents/<type>/output.md path convention, the exact reminder format), though presented as stylized pseudocode rather than copy-paste ready calls — anchor 4, above anchor 3 because specific executable details are given.

4 / 5

Workflow Clarity

A clear 4-step sequence (launch, continue, check reminder, read output on completion) with an implicit checkpoint ('check if output file exists'), but no explicit handling of failure paths such as an agent dying silently — anchor 4; no destructive/batch cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into well-labeled sections (Pattern / DO / DON'T / Why / Source), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

28%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 effectively just a title: it names the topic but describes no actions, no use conditions, and few natural trigger phrases. It would rarely be selected over competing skills because nothing tells Claude what the skill does or when to reach for it.

Suggestions

Rewrite as a third-person action statement, e.g., 'Avoids polling for background agent output by trusting system reminder notifications; continue other work and read the output file only on completion.'

Add an explicit 'Use when...' clause with concrete triggers such as 'launching background agents', 'waiting on async tasks', or 'tempted to poll agent output'.

Include natural trigger terms users would say (polling, agent progress, background task, output file) to improve both trigger quality and distinctiveness.

DimensionReasoningScore

Specificity

The description 'Background Agent Pings' names a specific domain but is a verbless topic label with no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic' rather than anchor 1's purely abstract generic language.

2 / 5

Completeness

It provides only a vague 'what' (a topic hint, no described behavior) and no 'when' guidance at all; a vague what with no when matches anchor 2, and the missing 'Use when...' clause would cap it at 3 regardless.

2 / 5

Trigger Term Quality

Only one or two keywords ('background agent', 'pings') are present; the natural phrases a user would actually say ('polling', 'agent progress', 'async task', 'check output') are missing, fitting anchor 2.

2 / 5

Distinctiveness Conflict Risk

The niche of background agent notifications is somewhat specific, but a verbless label like this could overlap with any agent-orchestration or task-management skill, matching anchor 3 'somewhat specific but could still overlap'.

3 / 5

Total

9

/

20

Passed

Validation

100%

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

parcadei/Continuous-Claude-v3

Path

.claude/skills/background-agent-pings/SKILL.md

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.