SKILLEMALL.ai

BC doc-parse-tool-pro

当需要doc parse tool相关能力的开发场景,提供结构化工作流程和配置说明. 该工具经过深度优化,基于用户反馈改进了实用性和可操作性。Use。请注意,以上功能在处理边界条件时,会根据实际情况进行相应的调整和优化,以确保工具的稳定性和可靠性。Use when 需要文件处理、文档转换、格式互转、内容提取时使用。不适用于加密文件破解。 ## 场景介绍

ClawHub Hermes author: 天轰穿 v1.0.1 MIT-0 2 files body ≈ 3 433 tokens Open the sourceclawhub.ai analyzed 3 d ago

当需要doc parse tool相关能力的开发场景,提供结构化工作流程和配置说明.

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationSoftware developmentAI and agentsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • 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-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Missing closing 'quote at line 6, column 87: …: '通用文档解析工具,支持PDF、图片、扫描件的结构化信息提取与OCR识别。。文档解析工具 - (专业版) 核心能力: 文档解析, OCR识别, 表格提取, ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 177 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "edition"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 58/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 57 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3433 tokens
  • 100Running it twice. No mutating operations
  • low 22 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 177: enough signal without eating the budget
  • +4Structure: 54 headings
  • +3Step-by-step instructions: 57 items
  • +4Has examples (4 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.

External checks

ClawHub: suspicious
This is a document-parsing skill with mostly expected capabilities, but its handling of sensitive document contents, callbacks, and saved outputs is not scoped clearly enough.
LLM: suspicious (medium) · 22 Aug 2026