BF lobster-haoyun
从你的对话和记忆中观察行为模式，用5个维度为你画像（工作方式/沟通模式/关注焦点/能量来源/情感倾向）， 生成每日运势和修炼提醒。在本地 ~/.lucky-lobster/ 存储 OB 身份凭据、行为画像、运势历史和偏好设置。 通过 OceanBus 加密通道向 L1 服务发送 5维行为代码、城市级位置、日期和匿名 OpenID， 用于获取节气黄历、匹配经典故事和推荐社区 Skill/公开课。对话内容、项目名、人名永不离开设备。 首次使用自动创建 OceanBus 匿名身份（密码学随机生成，删除 ~/.lucky-lobster/ 即可永久清除）。
从你的对话和记忆中观察行为模式，用5个维度为你画像（工作方式/沟通模式/关注焦点/能量来源/情感倾向）， 生成每日运势和修炼提醒。在本地 ~/.lucky-lobster/ 存储 OB 身份凭据、行为画像、运势历史和偏好设置。 通过 OceanBus 加密通道向 L1 服务发送 5维行为代码、城市级位置、日期和匿名…
As a process F 63/100 · Will not run — References files that are not bundled: {url}
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 18. 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") - warning
missing-refreference to a missing file: {url} - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "files" - note
frontmatter-keyunknown frontmatter key "required_capabilities"
Process rating: all ten parameters 63/100
- 0Tools and files. 1 referenced file(s) missing: {url}
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 100Steps. 45 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3180 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (4 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)
- -223 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 277: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.