CD dreamverse-deploy
Use when redeploying the migrated Dreamverse app backend and frontend on a chosen local GPU; tears down existing ports, launches services, and waits for readiness checks.
tears down existing ports, launches services, and waits for readiness checks.
As a process D 49/100 · Unfinished process — References files that are not bundled: ../../../apps/dreamverse/web/e2e/long-running-segments.spec.ts
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Dangerous commands
cmd-background-processscripts/dreamverse-deploy.sh:293Starts a background / autostarted processsetsid bash -c "
-
low Dangerous commands
cmd-background-processscripts/dreamverse-deploy.sh:316Starts a background / autostarted processdisown
-
low Dangerous commands
cmd-background-processscripts/dreamverse-deploy.sh:386Starts a background / autostarted processsetsid bash -c "
-
low Dangerous commands
cmd-background-processscripts/dreamverse-deploy.sh:394Starts a background / autostarted processdisown
-
low Dangerous commands
cmd-background-processSKILL.md:109Starts a background / autostarted process (quoted — discussed, not commanded)`setsid` session and captures its PID.
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../apps/dreamverse/web/e2e/long-running-segments.spec.ts - note
edit-residuethe text marks something as outdated (lines 36): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: ../../../apps/dreamverse/web/e2e/long-running-segments.spec.ts
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 55Failures and branches. 1 branches
- 85Steps. 29 steps, 1 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2254 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 170: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (4 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.