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

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong operational skill: concrete executable commands, explicit parameter semantics, well-sequenced workflows with genuine validation checkpoints and failure-mode handling. Its only weaknesses are mild repetition of safety cautions and a single-file structure that inlines some presentation/link-format detail that could be split into a reference.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational semantics ("CPU 100% means one core; memory excludes inactive file cache. Null usage is unknown, not zero"; "The interval includes since and excludes until") rather than concepts Claude already knows. A few cautions repeat (untrusted-data handling appears in three places, permission/403 warnings recur) and the evidence-formatting rules are somewhat over-specified, so it is efficient with minor trimming possible — anchor 4, not the fully lean anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: "agt monitoring --search <component-or-agent-name> --page 1 --limit 12 -o json", "agt logs component controller --since 15m --tail 300 -o json", "agt tracing --agent <worker-name> --since 1h --limit 20 -o table", "agt tracing task <project-id> <task-id> --team <team-name> --related". Concrete parameter ranges ("--tail is 1–1000", "--limit (1–100, default 20)"), output field names, and a filled-in reply template leave no gaps.

5 / 5

Workflow Clarity

Both workflows are explicitly numbered with validation checkpoints and feedback loops: "Inspect truncated and the returned timestamps before claiming completeness. Narrow the window when truncated", "Read retrieval_complete and gaps before drawing conclusions", "A 404 may mean a missing resource... check agt version and resource discovery before deciding", and error-recovery guidance (503 handling, pagination via totalPages). Observed-facts-vs-explanation separation and explicit uncertainty reporting complete the checkpoint discipline.

5 / 5

Progressive Disclosure

No bundle files exist, so the skill is scored as a single-file skill with well-organized sections and clear headers ("Inspect Runtime Health as Manager", "Present Evidence in Conversation", "Choose Your Query Scope", "Diagnose a Formal Task") — good structure with easy navigation. At ~195 lines, the reply-template and link-formatting details (percent-encoding rules, RFC3339 window resolution) are ancillary material that could live in a one-level-deep reference file, keeping it below the ideal-split anchor 5.

4 / 5

Total

18

/

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 is concise and specific, naming concrete diagnostic capabilities with natural user-facing terms and a distinct niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which both caps completeness and slightly raises conflict risk.

Suggestions

Add an explicit trigger clause, e.g. "Use when an Agent fails to reply, errors, stalls, retries, or a task produces an unexpected result."

Include natural trigger synonyms users would actually say: "not responding", "task failed", "stalled", "troubleshoot".

Round out capability coverage by mentioning session/task trace queries (e.g. "query traces by Agent, session, or task") so the description reflects the body's full scope.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "Diagnose missing replies, runtime errors and slow execution", "inspect component and Agent CPU, memory and container logs" — which name the domain and multiple specific operations. Minor gaps remain (tracing/session queries, formal task diagnosis, evidence presentation are covered in the body but not the description), so it falls just below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear (diagnose task failures via authorized traces; inspect CPU/memory/logs as Manager), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the "as Manager" phrase states a role condition, not when the skill applies. Per the judging guidelines, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases users would say include "missing replies", "runtime errors", "slow execution", "CPU", "memory", "container logs". A few common variations are missing ("failed", "stalled", "not responding", "troubleshoot", "task failure"), matching the 'good coverage, a few natural terms missing' anchor rather than the fully comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — authorized task-trace diagnosis plus Manager-scoped container monitoring — with little overlap risk against generic skills. Minor overlap remains with any general monitoring/logging skill, matching the 'mostly distinct; minor overlap risk' anchor; it is not a 5 because the trigger boundary is not fully explicit.

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/agentteams-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.