CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task-diagnosis

Diagnose missing replies, runtime errors and slow execution using authorized task traces; as Manager, inspect component and Agent CPU, memory and container logs.

Quality

79%

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 ./plugins/teamharness/skills/agent/task-diagnosis/SKILL.md

The canonical home for this skill is task-diagnosis in agentscope-ai/AgentTeams

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strongly actionable, well-sequenced diagnostic workflow with executable commands, explicit validation checkpoints and error-recovery loops throughout. Its main weakness is token efficiency: several safety and evidence rules are stated multiple times across sections, and the reply-template section could be split into a reference file to shorten the always-loaded body.

Suggestions

Deduplicate the repeated guidance — consolidate "report failures/denials explicitly, never present an empty successful diagnosis", the current-sample caveat, and the untrusted-data rule into one stated place each.

Move the evidence-block markdown templates and Dashboard link-construction rules (percent-encoding, RFC3339 window resolution) into a references/ file, keeping only a short pointer and one example inline.

Trim hedging sentences that restate the same limitation (e.g. multiple variants of "a running container does not prove replies work") to a single canonical line.

DimensionReasoningScore

Conciseness

The body is dense with platform-specific, non-obvious knowledge (flag semantics, pagination, truncation, error-code meanings), but guidance is repeated across sections — "report failures explicitly / don't fake a successful diagnosis" appears in three places, and the current-sample and untrusted-data caveats each appear twice. It could be tightened to reclaim tokens without losing clarity.

3 / 5

Actionability

Every workflow gives copy-paste-ready commands with concrete flags (e.g. "agt logs component controller --since 15m --tail 300 -o json", "agt tracing --agent <worker-name> --since 1h --limit 20 -o table") plus a filled-in output template with instructions to replace placeholders with actually-read evidence. This matches the fully-executable anchor.

5 / 5

Workflow Clarity

Both main workflows are numbered 1–5 with explicit validation checkpoints ("Read `totalPages`", "Inspect `truncated` and the returned timestamps", "Read `retrieval_complete` and `gaps`") and error-recovery feedback loops (narrow the window when truncated; check `agt version` on 404; ask the administrator on 503). This matches the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

No bundle files exist, and the single file is well-organized into clear H2 sections (runtime health, evidence presentation, query scope, formal task) with everything at one level. It falls short of anchor 5 because at ~195 lines some self-contained material (the evidence-block templates and link-construction rules) is inlined where a references file could offload it.

4 / 5

Total

17

/

20

Passed

Description

66%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 names concrete, domain-specific capabilities with mostly natural trigger keywords, but it completely lacks an explicit 'Use when...' clause, capping its completeness. Adding trigger phrasing (e.g., when an Agent does not reply, a task fails/stalls/retries, or a user asks about CPU, memory or container logs) would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when an Agent does not reply, a session/task fails, stalls or retries, or when asked about runtime errors, slow execution, CPU, memory or container logs."

Include natural user phrasings like "not responding", "stalled" or "timeout" as trigger synonyms alongside "missing replies" and "slow execution".

Mention the trace/session query capability (not just Manager monitoring) so the 'what' covers the Leader-side diagnosis workflow.

DimensionReasoningScore

Specificity

"Diagnose missing replies, runtime errors and slow execution" and "inspect component and Agent CPU, memory and container logs" list several concrete, distinct actions. It stops short of anchor 5 because coverage has gaps — trace/session queries, formal-task diagnosis and evidence presentation are not mentioned.

4 / 5

Completeness

The 'what' is clear (diagnose failures/slowness via traces; inspect CPU/memory/logs as Manager), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "as Manager" is a role qualifier, not a usage trigger. Per the rubric guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"missing replies", "runtime errors", "slow execution", "CPU", "memory", "container logs" are terms a user would plausibly say when needing this skill. Not 5 because common natural synonyms like "not responding", "stalled", "failed" or "timeout" are absent; not 3 because the keywords are relevant and natural rather than technical jargon.

4 / 5

Distinctiveness Conflict Risk

"authorized task traces" and the Manager/Agent component-log framing carve a fairly distinct niche in agent-execution diagnostics. Minor overlap risk remains with generic debugging or observability skills via terms like "runtime errors" and "container logs", keeping it below anchor 5.

4 / 5

Total

15

/

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

agentscope-ai/AgentTeams

Path

plugins/teamharness/skills/agent/task-diagnosis/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.