Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, directive skill body: it sequences prototyping → task-based verification → service verification with explicit checkpoints and error-recovery loops, and provides concrete commands and source URLs. The main gaps are minor — placeholder arguments in the nohup example and advanced Router/PD content inlined rather than split into reference files.
Suggestions
Move the Router and PD-disaggregation sections into a reference file (e.g. references/advanced.md) and link to them from SKILL.md, keeping the main body focused on the core task→service prototyping loop.
Replace the `nohup vllm serve ...` placeholder with one complete concrete serving command (real flags, model name, port) so the pattern is copy-paste ready.
Consolidate the repeated verification checklist (image, command, port, resources, env vars, cache) into a single named checklist section that later steps reference, trimming duplicated enumerations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive throughout: no concept explanations Claude already knows (no "what is dstack/vLLM" padding), terse section headers, and purposeful restatement of the config checklist as validation checkpoints rather than filler. Quotes like "Submit the task detached, attach or SSH into it... and run commands inside the live environment" show every token carrying instruction. Not 4 because there is no over-explanation to trim. | 5 / 5 |
Actionability | Mostly executable guidance: a literal task command block (`commands: - sleep infinity`), a full nohup pattern with stdin/stdout redirects, concrete CLI (`dstack fleet get <fleet name> --json`), specific URLs to fetch with named sections to look for ("Look for 'Prototyping services' in https://dstack.ai/docs/concepts/tasks.md"). Not 5 because the nohup example is a placeholder (`nohup vllm serve ...`) and no concrete dstack task/service YAML is shown inline (syntax is delegated to the /dstack skill, which is justified but leaves minor gaps). | 4 / 5 |
Workflow Clarity | Clear sequence with explicit validation checkpoints and a feedback loop: choose backend → check serving sources → task on real hardware → "Do not move to a service after checking only GPU visibility, imports, logs, or a health endpoint" → submit service → verify through service URL → on failure "go back to a task" or "fix the configuration and submit the service again". This matches the top anchor including error-recovery loops. | 5 / 5 |
Progressive Disclosure | Well-organized sections with clearly signaled, one-level-deep references (dstack docs URLs, vLLM/SGLang recipe sources, the /dstack skill for syntax). Not 5 because the body is ~133 lines with advanced Router and PD-disaggregation sections inlined that could live in separate reference files (no references/ bundle exists to absorb them), leaving minor organization gaps. | 4 / 5 |
Total | 18 / 20 Passed |