BB lingzao
灵造是给 WorkBuddy、OpenClaw、Codex 等 Agent 使用的跨平台创作者研究与自媒体运营 Skill。安装免费，可先做选题、标题、封面、账号诊断、发布检查、复盘，以及公众号对标适配判断和原创写作；查询公开内容、评论、短视频文案、公众号文章数据或生成图片时需要配置灵造 API Key。
灵造是给 WorkBuddy、OpenClaw、Codex 等 Agent 使用的跨平台创作者研究与自媒体运营 Skill。安装免费，可先做选题、标题、封面、账号诊断、发布检查、复盘，以及公众号对标适配判断和原创写作；查询公开内容、评论、短视频文案、公众号文章数据或生成图片时需要配置灵造 API Key。
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, execution cost
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 tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Concealment
en-hide-from-userplaybooks/image-generation-execution-workflow.md:64Instruction to hide actions from the user ("do not tell the user <a claim>" — honesty guidance, not concealment)- Do not tell the user that an obviously ugly image is acceptable.
honesty claim -
medium Exfiltration
net-redirectable-api-keyscripts/configure.py:33Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-redirectable-api-keyscripts/lingzao_client.py:122Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
Files scanned: 52. 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
body-longSKILL.md body ≈ 11245 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 11245 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 118 steps
- 100Failures and branches. 23 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (11 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)
- -33 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 153: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 118 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.