SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Storage Manager

Feishu Bitable Storage Manager - Integrated tool for item storage, retrieval, and location updates

ClawHub Agent Skills author: ruoruochen v1.0.0 MIT-0 10 files · 1 script body ≈ 107 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationInfrastructuretype 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
83/100
safety, quality, tests
Safety 60%
99
Quality 40%
59
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token test_basic.py:33
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    os.environ["FEISHU_APP_SECRET"] = "HHEZ…B71"
    fixturequoted

Files scanned: 9. 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-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "read_when"

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 40Consistency. Frontmatter name (Storage Manager) differs from the folder (release-package)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 9 steps
  • 100Execution cost. Instruction body is 107 tokens
  • 100Running it twice. No mutating operations

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 98: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 9 items

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

External checks

ClawHub: suspicious
The skill mostly matches its Feishu storage-manager purpose, but it includes real-looking Feishu credentials in test code and needs review before installation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026