AD byted-livesaas-master
企业直播 / LiveSaaS 控播 Skill。支持通过 `bytedlive` CLI 操作直播间(创建/配置/状态)、评论、系统消息、观众管控,以及 OpenAPI 兜底调用。覆盖场景包括:直播间生命周期管理、直播数据与观众画像分析、商品卡片运营(上架/讲解)、营销互动工具(卡券)与连麦协同控制、媒资库运维及账号/权益信息查询。触发词:企业直播、控播、直播间、ActivityId、评论、弹幕、禁言、拉黑、踢人、商品卡片、直播数据、观众画像、火山引擎 livesaas。
企业直播 / LiveSaaS 控播 Skill。支持通过 bytedlive CLI 操作直播间(创建/配置/状态)、评论、系统消息、观众管控,以及 OpenAPI…
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenreferences/data/openapiActionVersions.json:147High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"Anal…eV2": {quoted -
low Secrets in code
secret-high-entropy-tokenreferences/data/openapiActionVersions.json:172High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"title": "Anal…eV2 - 获取直播间不同观看时长的人数",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/data/openapiActionVersions.json:5572High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"List…IV2": {quoted -
low Secrets in code
secret-high-entropy-tokenreferences/data/openapiActionVersions.json:5614High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"title": "List…IV2 - 获取直播间问卷数据信息",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:354High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| **直播数据与画像** | `Anal…eV2` / `GetAccountUserTrackData` | 获取观看时长分布与观众画像详情 |
table
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 47/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. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4671 tokens
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- low 14 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)
- +3Output format is not stated: the model decides each time
- -219 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 239: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.