BF trans-doc-to-md
Convert PDFs, Lexiang document links, or prepared Markdown packages into faithful bilingual Markdown work packages. Preserves source paragraphs, local image paths and order, and rich document structure; uses a generic article profile or strict PDF-rich profile as appropriate. Outputs source.md, optional images/, meta.json, and a final Markdown file named from the original title. Publishing is delegated to upload-markdown-to-lexiang; this skill contains no upload implementation. 将 PDF、乐享文档链接或已准备好的 Markdown 工作包转换为保真的双语 Markdown 工作包。
Convert PDFs, Lexiang document links, or prepared Markdown packages into faithful bilingual Markdown work packages.
As a process F 35/100 · Will not run — References files that are not bundled: /assets/..., images/...
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 12. 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") - warning
missing-refreference to a missing file: /assets/... - warning
missing-refreference to a missing file: images/... - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: /assets/..., images/...
- 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
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1697 tokens
- 100Running it twice. No mutating operations
- 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
- -31 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 536: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.