AD huo15-claw-butler-file-delivery
Deliver a file to the user's 龙虾管家 (Claw Butler) desktop/mobile client. Use whenever you produced a file (report, PDF, image, spreadsheet, export, archive, code bundle) and the user wants to receive, open, download, or save it — and especially the moment a normal send fails with "Message failed" or the file shows up only as a clickable link that 404s. Delivers via the client's `file.push` node capability (works), never via WebChat outbound (which cannot carry files). Triggers: 发我文件 / 把文件发过来 / 下载 / 导出给我 / send me the file / why is it just a link.
Deliver a file to the user's 龙虾管家 (Claw Butler) desktop/mobile client.
As a process D 49/100 · Unfinished process — 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: 0. 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: Deliver a file to the user's 龙虾管家 (Claw Butler) desktop/mobile cli… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 49/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
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 441 tokens
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 550: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.