BD feishu-calendar
飞书日历管理技能。用于查询日程、创建事件、查询忙闲状态。当用户询问日程、会议、日历相关问题时使用此技能。触发条件:(1) 用户询问今天的日程/明天的日程/某天的日程 (2) 用户要求创建日程/添加会议/新建事件 (3) 用户询问日历/日程安排 (4) 用户提到飞书日历相关需求。
As a process D 45/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 · 9
✓ No critical or high findings
Medium and low: 9
-
medium Secrets in code
secret-labelled-tokenreferences/oauth-setup.md:47Labelled token / key literal (vendor format unknown — verify it is not a live credential)$appSecret = "9QGw…8eF"
-
medium Secrets in code
secret-labelled-tokenSKILL.md:82Labelled token / key literal (vendor format unknown — verify it is not a live credential)$appBody = @{ app_id = "cli_…cc2"; app_secret = "9QGw…8eF" } | ConvertTo-Json -
low Secrets in code
secret-high-entropy-tokenreferences/oauth-setup.md:47High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)$appSecret = "9QGw…8eF"
quoted -
low Exfiltration
net-credential-usereferences/oauth-setup.md:52Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)$appToken = (Invoke-RestMethod -Uri "https://open.feishu.cn/open-apis/auth/v3/app_access_token/internal" -Method Post -Body $body1 -ContentType "application/json").app_access_token
vendor-host -
low Exfiltration
net-credential-usereferences/oauth-setup.md:56Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)$userToken = Invoke-RestMethod -Uri "https://open.feishu.cn/open-apis/authen/v1/oidc/access_token" -Method Post -Body $body2 -ContentType "application/json" -Headers @{ Authorization = "Bearer $appTokvendor-host -
low Exfiltration
net-credential-usereferences/oauth-setup.md:59Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)$calendar = Invoke-RestMethod -Uri "https://open.feishu.cn/open-apis/calendar/v4/calendars/primary" -Method Post -Headers @{ Authorization = "Bearer $($userToken.data.access_token)" }vendor-host -
low Secrets in code
secret-high-entropy-tokenSKILL.md:82High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)$appBody = @{ app_id = "cli_…cc2"; app_secret = "9QGw…8eF" } | ConvertTo-Jsonquoted -
low Exfiltration
net-credential-useSKILL.md:83Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)$appToken = (Invoke-RestMethod -Uri "https://open.feishu.cn/open-apis/auth/v3/app_access_token/internal" -Method Post -Body $appBody -ContentType "application/json").app_access_token
vendor-host -
low Exfiltration
net-credential-useSKILL.md:87Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)$newToken = Invoke-RestMethod -Uri "https://open.feishu.cn/open-apis/authen/v1/oidc/refresh_access_token" -Method Post -Body $refreshBody -ContentType "application/json" -Headers @{ Authorization = "Bvendor-host
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 45/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
- 40Consistency. Frontmatter name (feishu-calendar) differs from the folder (feishu-calendar-cn)
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 847 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)
- +3Output format is not stated: the model decides each time
- -34 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 139: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.