BF qdrant-vertical-scaling
Guides Qdrant vertical scaling decisions. Use when someone asks 'how to scale up a node', 'need more RAM', 'upgrade node size', 'vertical scaling', 'resize cluster', 'scale up vs scale out', or when memory/CPU is insufficient on current nodes. Also use when someone wants to avoid the complexity of horizontal scaling.
Guides Qdrant vertical scaling decisions.
As a process F 30/100 · Will not run — References files that are not bundled: ../../../qdrant-monitoring/SKILL.md, ../horizontal-scaling/SKILL.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: ../../../qdrant-monitoring/SKILL.md - warning
missing-refreference to a missing file: ../horizontal-scaling/SKILL.md
Process rating: all ten parameters 30/100
- 0Tools and files. 2 referenced file(s) missing: ../../../qdrant-monitoring/SKILL.md, ../horizontal-scaling/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (qdrant-vertical-scaling) differs from the folder (vertical-scaling)
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 1002 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 318: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 29 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.