BC emoji-toolkit-free
表情符号工具箱免费版解决在即时通讯中\"隐藏消息传递、代币安全传输、表情符号深度解析\"的核心需求。表情符号工具箱利用Unicode变体选择器（VS1-VS256）技术，将文本隐藏在表情符号内部，达成视觉上只显示表情但实际携带隐藏信息的效果。Use. 适用于需要emoji toolkit相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量.
表情符号工具箱免费版解决在即时通讯中\"隐藏消息传递、代币安全传输、表情符号深度解析\"的核心需求。表情符号工具箱利用Unicode变体选择器（VS1-VS256）技术，将文本隐藏在表情符号内部，达成视觉上只显示表情但实际携带隐藏信息的效果。Use.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 6, column 72: …ode变体选择器隐藏消息、代币编码与元数据解析.。表情符号工具箱免费版解决在即时通讯中"隐藏消息传递、代币安全传输、表情符号深度解析"的核心需求。表情符号工" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 190 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
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. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2151 tokens
- 100Running it twice. No mutating operations
- 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
- +2Single-language instructions
- +3Description length 190: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.