AC feishu-file-send
Reliable Feishu file sending workflow. Strongly prefer this skill whenever a Feishu user asks for a file, asks you to send or return a document, or whenever you are about to deliver any attachment in a Feishu DM or group. Use for generated or edited docx, xlsx, pdf, txt, pptx, images, archives, and other local files. Also use when diagnosing Feishu attachment delivery failures, missing attachments, mediaLocalRoots path issues, or cases where text plus attachment was combined and the recipient did not receive the file. In any Feishu conversation involving outbound files or attachment troubleshooting, this skill should usually be selected.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 19 mutating operations with no state check
- 40Consistency. Frontmatter name (feishu-file-send) differs from the folder (feishu-attachment-send)
- 70When it triggers. States when to use, but not when not to
- 85Steps. 26 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 760 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 645: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.