BC iris-formatter-tool-pro
面向企业级 IRIS 开发团队的 ObjectScript 代码审查与治理工具。核心能力: - 批量代码审查与格式化（多文件/多类） - 自定义规范规则与团队级配置 - 结构化审查报告导出（Markdown/HTML） - SQL 格式规范与性能检查 - 陷阱（Trap）深度分析与合规检查 - 代码复杂度与重复度分析 适用场景: - 企业级 IRIS 项目的代码质量管控 - 团队协作中的代码审查标准化 - 遗留系统的代码重构与规范化 - 上线前的合规检查与合规检查 差异化: 专业版兼容免费版所有规...
面向企业级 IRIS 开发团队的 ObjectScript 代码审查与治理工具。核心能力: - 批量代码审查与格式化（多文件/多类） - 自定义规范规则与团队级配置 - 结构化审查报告导出（Markdown/HTML） - SQL 格式规范与性能检查 - 陷阱（Trap）深度分析与合规检查 -…
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 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 256 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - 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"
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. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2743 tokens
- 100Running it twice. No mutating operations
- low 12 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 256: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.