BC infinite-memory-vault-pro
面向需要超越 Agent 内置记忆的长期结构化存储场景的无限记忆库专业版。与 Agent 内置记忆并行工作，互不冲突，提供无限分类、语义搜索、自动同步、大规模索引能力。专业版解锁全部高级功能，适合团队/企业级知识管理与长期记忆需求。Use when 需要SEO优化、关键词分析、排名提升、搜索流量优化时使用。不适用于黑帽SEO手段。 功能涵盖: infinite, vault。
面向需要超越 Agent 内置记忆的长期结构化存储场景的无限记忆库专业版。与 Agent 内置记忆并行工作，互不冲突，提供无限分类、语义搜索、自动同步、大规模索引能力。专业版解锁全部高级功能，适合团队/企业级知识管理与长期记忆需求。Use when…
As a process C 52/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: All mapping items must start at the same column at line 10, column 1: description: "面向需要超越 Agent 内置记忆的长期结构化存储场景的无限记忆库专业版。与 Agent 内置记忆并行工作，互不冲突，提供无限分类… 核心能力包括无限分类存储（用户自定义目录结构）、INDEX.md 索引导航（每类别独立索引）、即写即存协议、与内置记忆并行工作、语义搜索（基于本地 emb… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 189 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"
Process rating: all ten parameters 52/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
- 70Execution cost. Instruction body is 4144 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 20 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
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (23 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.