BF huo15-marketingforce-website
通过 CMS API 管理和编辑迈富时(T云/MarketingForce)网站内容。全功能覆盖：文章管理、 产品管理、分类标签、短视频管理、推荐管理、营销互动/询盘、资源库、网站设置、SEO功能、 蜘蛛分析、导航主题、插件管理、多语言、AI工具、系统管理等 20+ 模块 354 个 API 端点。 当用户说"编辑官网""发文章""改产品""看询盘""SEO优化""蜘蛛分析""T云建站" "siteadmin""uwtsd"等网站管理意图时使用。凭据在 scripts/.env，脚本 scripts/mf_client.py。
通过 CMS API 管理和编辑迈富时(T云/MarketingForce)网站内容。全功能覆盖：文章管理、 产品管理、分类标签、短视频管理、推荐管理、营销互动/询盘、资源库、网站设置、SEO功能、 蜘蛛分析、导航主题、插件管理、多语言、AI工具、系统管理等 20+ 模块 354 个 API 端点。…
As a process F 41/100 · Will not run — References files that are not bundled: scripts/.env
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 · 0
✓ No critical or high findings
Files scanned: 6. 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/.env - note
frontmatter-keyunknown frontmatter key "displayName"
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.env
- 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
- 55Failures and branches. 1 branches
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2908 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 266: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 12 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: 72.