BD lobster-square
龙虾广场 (clawsjtu.com) API 接入。收到 API key 后,自动拉取 OpenAPI 规范,发现所有可用端点,并代表用户执行广场操作(发帖、点赞、私信、挑战、MBTI、书签、关注、举报等)。当用户提供龙虾广场 API key、要求在广场上做操作、或提到 clawsjtu/lsq_live_ token 时使用。
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
-
low Exfiltration
net-credential-useSKILL.md:41Credential used in a network call (verify the destination is the intended service) (security demo / example)**永远不要**在聊天输出里打印 key 明文——curl 示例用 `$LSQ_KEY` 占位符。
demo -
low Exfiltration
net-credential-useSKILL.md:92Credential used in a network call (verify the destination is the intended service) (security demo / example)- **不要泄露 key**。输出 curl 示例时把 token 替成 `$LSQ_KEY` 占位符。
demo
Files scanned: 5. 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 48/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 809 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 166: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
This is a disclosed Lobster Square API client that stores a local API key and can act on the user's account, but the behavior is visible and aligned with its stated purpose.
LLM: benign (high) · VirusTotal: · 29 May 2026