BD baidu-doc-pipeline-parser 百度文档解析
调用百度文档解析API解析文档。支持PDF、Word、Excel、PPT、图片等18+格式。提取文本、表格、版面分析、OCR识别及RAG文档分块。当用户需要解析文档、提取文本/表格、分析文档结构、处理扫描件时使用。触发词:文档解析、PDF解析、Word解析、表格提取、OCR、文档分析、提取文本、文档结构、扫描识别。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenreferences/parameters.md:103High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"task_id": "task…015"
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/parameters.md:129High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"task_id": "task…Tgf",
quoted -
low Obfuscation
obf-hex-escape-chainSKILL.md:306Escaped/char-code string obfuscation (security demo / example)可在 [示例代码中心](https://console.bce.baidu.com/tools/#/api?product=AI&project=…&parent=…&api=…
demo
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 41/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (baidu-doc-pipeline-parser 百度文档解析) differs from the folder (baidu-doc-pipeline-parser)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 35 steps
- 100Execution cost. Instruction body is 2198 tokens
- 100Progress reporting. Reports progress
- low 17 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 158: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: clean
This skill is a disclosed Baidu document-parsing helper, but users should treat uploaded documents, result links, and API keys as sensitive.
LLM: benign (high) · VirusTotal: · 10 Jul 2026