AC xhs-title-pro
使用场景： - 用户说"帮我起标题"、"标题怎么写" - 用户说"小红书标题"、"爆款标题" - 用户粘贴笔记内容说"帮我起个好标题" - 用户说"笔记没人看"、"怎么涨粉" - 用户说"这个内容怎么取标题" 不适用： - 公众号文章标题（用公众号标题生成器） - 抖音视频标题（用抖音标题生成器） - 简历优化（用resume-pro） - 纯闲聊
As a process C 53/100 · Has gaps — 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.
For the model run — optional
- 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: 3. 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 "tools"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 62 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 814 tokens
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 175: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 62 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: suspicious
This title-writing skill is mostly coherent, but it asks for broad local file read/write access and describes ongoing memory without clear limits.
LLM: suspicious (high) · VirusTotal: · 29 May 2026