AC workbuddy-data-migration
Migrate the WorkBuddy data directory (C:\Users\USER\.workbuddy) off the system drive to a fixed non-system disk using a Windows directory junction, so conversation history, sessions, skills, logs, the python/node runtimes (binaries), and all caches stop consuming C: space — and stay off it permanently, including any runtimes installed later. Use this skill when C: is low on space and WorkBuddy-related files are a major contributor, when the user asks to move WorkBuddy data / cache / environment / 运行时 off the system disk, or to reproduce a clean data-directory relocation (e.g. after a WorkBuddy reinstall recreates the C: dir and overwrites the junction).
Migrate the WorkBuddy data directory (C:\Users\USER\.workbuddy) off the system drive to a fixed non-system disk using a Windows directory junction, so…
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Migrate the WorkBuddy data directory (C:\Users\USER\.workbuddy) of… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 53/100
- 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
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 85Steps. 17 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1078 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 661: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.