SKILLEMALL.ai
GitHub ↗ RU Sign in

BD Feishu Upload Skill

飞书文件上传技能 - 直接上传文件到飞书并发送到聊天

modbender/skill-library-mcp Agent Skills author: modbender MIT 10 files · 4 scripts body ≈ 684 tokens Open the sourcegithub.com↗ analyzed 2 d ago

飞书文件上传技能 - 直接上传文件到飞书并发送到聊天

As a process D 36/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
79/100
safety, quality, tests
Safety 60%
94
Quality 40%
56
Run on models
none yet
Process rating
D
36/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Secrets in code secret-labelled-token get_feishu_token.sh:5
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    APP_SECRET="yAqF…HAK"
  • low Secrets in code secret-high-entropy-token get_feishu_token.sh:5
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    APP_SECRET="yAqF…HAK"
    quoted

Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 36/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (Feishu Upload Skill) differs from the folder (feishu-upload-skill)
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 100Steps. 34 steps
  • 100Execution cost. Instruction body is 684 tokens
  • low 10 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 26: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 34 items
  • +4Has examples (9 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.