SKILLEMALL.ai
GitHub ↗ RU Sign in

AF nvflare-diagnose-job

Use when the user asks why a reported NVFLARE job failure signal occurred: the job failed, stalled, timed out, lost clients, ended with EXECUTION_EXCEPTION, or produced suspicious errors. Diagnose in simulation, POC, or production by collecting bounded evidence and mapping failure patterns to recovery actions.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 1 055 tokens Open the sourceclawhub.ai↗ analyzed 8 h ago

Use when the user asks why a reported NVFLARE job failure signal occurred: the job failed, stalled, timed out, lost clients, ended with EXECUTIONEXCEPTION, or…

As a process F 65/100 · Will not run — References files that are not bundled: references/evidence-collection.md, references/failure-patterns.md

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
F
65/100
Will not run
References files that are not bundled: references/evidence-collection.md, references/failure-patterns.md
Tools and files w 18
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/evidence-collection.md
  • warning missing-ref reference to a missing file: references/failure-patterns.md

Process rating: all ten parameters 65/100

Will not run. References files that are not bundled: references/evidence-collection.md, references/failure-patterns.md
  • 0Tools and files. 2 referenced file(s) missing: references/evidence-collection.md, references/failure-patterns.md
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 23 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1055 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 311: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 23 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.