BD feishu-image-send
Send inline images via Feishu Bot messages. Use when the `message` tool's `filePath`/`file_path` parameters fail to render images (shows JSON text instead). Works by generating a temporary Node.js script that calls the Feishu Open API directly (upload image → get image_key → send image message). Trigger: sending images to Feishu chat, image rendering fails, or user asks to send a picture via Feishu bot.
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:140High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `appSecret`: `Q3c7…cZH`
quoted
Files scanned: 2. 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: Send inline images via Feishu Bot messages. Use when the `message`… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 39/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. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (feishu-image-send) differs from the folder (send-feishu-image)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 15 steps
- 100Execution cost. Instruction body is 1684 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 406: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.