AD github-pages-publish
把「已有的」静态网页文件（单个 HTML 或整个网站目录）安全发布到 GitHub Pages，生成可公开访问、能分享的网址链接。当用户已有现成网页，想「发到网上」「部署上线」「发布网页」「生成分享链接」时使用；本技能只做「发布已有文件」，不负责从零生成网站。提供可执行的 deploy.py 脚本（整站增量上传 / 单文件上传 / 仅启用 Pages 三种模式），纯标准库无额外依赖，逐文件增量上传、绝不覆盖远程已有内容，并已回写真实踩坑（token 写权限、连接器只读、force 覆盖风险）。仅适用于纯静态内容；涉及后端、数据库、登录或敏感数据时不要用。
把「已有的」静态网页文件（单个 HTML 或整个网站目录）安全发布到 GitHub Pages，生成可公开访问、能分享的网址链接。当用户已有现成网页，想「发到网上」「部署上线」「发布网页」「生成分享链接」时使用；本技能只做「发布已有文件」，不负责从零生成网站。提供可执行的 deploy.py 脚本（整站增量上传 /…
As a process D 43/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.
- 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 · 0
✓ No critical or high findings
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") - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 43/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. 11 mutating operations with no state check
- 60Tools and files. Uses tools (git, python) that frontmatter does not declare
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 967 tokens
- low The response is described with custom markup (12 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 280: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.