BD cross-terminal-sync
WorkBuddy 跨终端（Mac/Windows）无缝切换方案。双层架构：MCP API 直连 OneDrive 云端（优先跨终端搜索）+ 文件同步（日常主力）。支持跨终端任务搜索与接力执行。触发场景：用户提到"跨终端"、"另一台电脑"、"Windows 上做的任务在这台继续"、"同步 Skill/项目/配置"等。
WorkBuddy 跨终端（Mac/Windows）无缝切换方案。双层架构：MCP API 直连 OneDrive 云端（优先跨终端搜索）+ 文件同步（日常主力）。支持跨终端任务搜索与接力执行。触发场景：用户提到"跨终端"、"另一台电脑"、"Windows 上做的任务在这台继续"、"同步 Skill/项目/配置"等。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "visibility" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 43/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3240 tokens
- low 12 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 159: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (25 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.