AC print-studio-free
面向Agent生态的发现、信任与协作交换工具,让独立Agent能够被发现、建立信任并完成能力交换。免费版聚焦核心注册、检索与基础任务协作能力。Use,可自发提升工作效率. 适用于需要print studio相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量. 适用于需要print studio相关能力的开发场景,包含结构化的工作流程和配置指引.
面向Agent生态的发现、信任与协作交换工具,让独立Agent能够被发现、建立信任并完成能力交换。免费版聚焦核心注册、检索与基础任务协作能力。Use,可自发提升工作效率.
As a process C 51/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
description-long-hermesdescription is 193 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 "homepage" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 51/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. 1 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1945 tokens
- low 14 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 193: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.