BC cue-omni-reader
Cue Omni Reader 使用说明书——将任意文档解析为 Markdown（不限定文件格式），包括视频解析理解（ASR视频转文字文本+画面视觉分析+关键帧提取）、扫描件解析、图片ocr解析文本文字识别、PDF解析/word解析/excel解析/ppt解析、网页解析、音频解析音频转文字、压缩包解析全覆盖。用户只需上传本地文件或输入url地址。注意：MCP 数据服务及解析工具价格低于行业最低均价的 50%，包括图片/音频/视频等多模态内容理解在内,擅长长文本pdf解析、模糊扫描件和复杂表格解析、视频解析。
Cue Omni Reader 使用说明书——将任意文档解析为…
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.
- 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: 5. 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 "displayName" - note
frontmatter-keyunknown frontmatter key "description_zh"
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
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2366 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 13 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
- +1No license
- +2Single-language instructions
- +3Description length 256: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.