BF nvflare-convert-lightning
Convert existing PyTorch Lightning training code into an NVFLARE federated job using the Lightning Client API patch, local validation, and job export; use only when the request names federated/NVFLARE conversion or asks multiple sites to train collaboratively while keeping each site's data local, and either names PyTorch Lightning or preliminary source inspection identifies one Lightning owner; do not use for non-federated Lightning work such as DDP, profiling, inference serving, or training-loop changes, nor for plain PyTorch, TensorFlow/Keras, other frameworks, deployment, POC/production lifecycle, or experiment workflows.
Convert existing PyTorch Lightning training code into an NVFLARE federated job using the Lightning Client API patch, local validation, and job export; use…
As a process F 57/100 · Will not run — References files that are not bundled: references/lightning-detection.md, references/lightning-conversion.md, references/lightning-validation.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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-refreference to a missing file: references/lightning-detection.md - warning
missing-refreference to a missing file: references/lightning-conversion.md - warning
missing-refreference to a missing file: references/lightning-validation.md - warning
missing-refreference to a missing file: references/lightning-ddp-and-tracking.md
Process rating: all ten parameters 57/100
- 0Tools and files. 4 referenced file(s) missing: references/lightning-detection.md, references/lightning-conversion.md, references/lightning-validation.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 6 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 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 3039 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 632: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 31 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.