BD miniprogram-mall-ushopun-official
基于 Ushopun（优社云AI）官方 miniProgramV2 真实项目构建的微信小程序商城前端，覆盖首页、分类、商品详情、购物车、结算、订单、个人中心等 50+ 页面与完整交易链路。内置 dev.ushopun.com OpenAPI（接口前缀 /api/v2，返回体 code/content/data，guid/token/shopId 鉴权）完整接口对接规范与每个方法的调用示例。当用户需要开发对接 Ushopun 后端（优社云）的微信小程序商城时调用此 Skill。后端接口文档参考同目录 openapi.json（#File ./openapi.json，servers 为 {tenant}.ushopun.com 泛域名模板，开发填 dev，正式替换租户子域名）。
基于 Ushopun（优社云AI）官方 miniProgramV2 真实项目构建的微信小程序商城前端，覆盖首页、分类、商品详情、购物车、结算、订单、个人中心等 50+ 页面与完整交易链路。内置 dev.ushopun.com OpenAPI（接口前缀 /api/v2，返回体…
As a process D 42/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.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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") - warning
body-longSKILL.md body ≈ 11928 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 42/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. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (miniprogram-mall-ushopun-official) differs from the folder (miniprogram-mall-ushopun-skill)
- 40Execution cost. Instruction body is 11928 tokens: crowds the task out of the window
- 100Tools and files. No external tools needed
- 100Steps. 57 steps
- low 11 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
- -2localhost URLs: will not work for another user
- -237 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 342: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.