CD powpow-integration
向 PowPow 泡泡(global.powpow.online)发布帖子/游记,以及创建数字人并钉到公开地图。当用户想把「旅行」「照片」「游记」发布到 PowPow 时触发,例如"发一篇 PowPow 帖子""在泡泡发一条""把这次旅行的照片发到泡泡""发篇游记到 powpow""publish a PowPow post""post to PowPow feed";当用户想创建/发布数字人到地图时触发,例如"创建一个数字人""把某某做成数字人放到地图上""发布数字人"。需要 PowPow 账号(尚无账号时先注册)。包含的辅助能力(均为上述发布/创建流程的组成部分):账号登录与会话管理、运行环境自检、地点名称解析为坐标、数字人搜索与主题匹配、图片搜索与上传、帖子组装与发布、发布后验证、删除自己发布的帖子(仅清理测试帖,JWT 限定本人帖子);以及面向平台维护者本人的万神殿(theotopia)神明批量发布与只读巡检(维护者提供自己的 Supabase 服务密钥,见正文专节)。不含其他社交平台发布,不含订阅/营销推广。
向 PowPow 泡泡(global.powpow.online)发布帖子/游记,以及创建数字人并钉到公开地图。当用户想把「旅行」「照片」「游记」发布到 PowPow 时触发,例如"发一篇 PowPow 帖子""在泡泡发一条""把这次旅行的照片发到泡泡""发篇游记到 powpow""publish a PowPow…
As a process D 44/100 · Unfinished process — References files that are not bundled: scripts/*.js, scripts/create-theotopia-gods.js
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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
-
medium Exfiltration
net-credential-usescripts/check-theotopia-gods.js:75Credential used in a network call (verify the destination is the intended service)const res = await fetch(`${creds.url}/rest/v1/user_digital_humans?${query}`, {
Files scanned: 26. 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") - warning
missing-refreference to a missing file: scripts/*.js - warning
missing-refreference to a missing file: scripts/create-theotopia-gods.js
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: scripts/*.js, scripts/create-theotopia-gods.js
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4089 tokens
- 100Steps. 121 steps
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 13 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 466: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 121 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.