BD super-lobster
🦞 Super Lobster | 超级龙虾 - 桥哥的私人 AI 助理 整合了飞书文档管理、会议纪要整理、每日待办推送、工作模块分类等核心技能。 能够自动读取会议纪要、按工作模块分类整理待办事项、创建飞书文档并推送。 核心能力： - 📄 飞书文档创建（支持 100+ blocks 大文档） - 📋 会议纪要自动整理 - ✅ 每日待办推送（按工作模块分类） - 🔐 飞书权限自动设置 - 📊 工作模块智能分类 - ⏰ 定时任务执行
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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-tokenscripts/create_daily_todo.mjs:4Labelled token / key literal (vendor format unknown — verify it is not a live credential)const APP_SECRET = 'iRuP…x84';
-
low Secrets in code
secret-high-entropy-tokenscripts/create_daily_todo.mjs:4High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const APP_SECRET = 'iRuP…x84';
quoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (super-lobster) differs from the folder (wong-super-lobster)
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 1326 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
- -234 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 223: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (15 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.