BF workbuddy-multi-device-sync
Set up automatic configuration sync across multiple Macs using WorkBuddy. Use when the user wants to use WorkBuddy on two or more computers and keep identity, memory, skills, and settings synchronized. Triggers: 多台电脑同步, 双机同步, 两台 Mac 同步 WorkBuddy, sync WorkBuddy across devices, multi-device sync, 换电脑配置同步. Covers Git-based sync via GitHub, auto-sync daemon, and one-click setup for additional machines.
Set up automatic configuration sync across multiple Macs using WorkBuddy.
As a process F 46/100 · Will not run — References files that are not bundled: references/gitignore-template, scripts/setup-mac-b.sh.template
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-persistencereferences/sync-architecture.md:49Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)On macOS 12+, `launchctl load` frequently fails with "Input/output error" under
quoted -
medium Dangerous commands
cmd-persistenceSKILL.md:217Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- **LaunchAgent** (`launchctl load`) often fails with "Input/output error" on macOS 12+
detector
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/gitignore-template - warning
missing-refreference to a missing file: scripts/setup-mac-b.sh.template - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: references/gitignore-template, scripts/setup-mac-b.sh.template
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 14 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 57 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1989 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
- +1No license
- +2Single-language instructions
- +3Description length 402: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (11 code blocks)
- +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: 81.