AC eplan-drawing-parser
EN: Extract structured data from EPLAN/CAD vector PDF electrical drawings — component list (位号/型号/数量), wire/pin topology (导线连接、串并联、电能流向), terminal table, and title-block metadata. Uses PDF vector geometry (100% accurate, no OCR) instead of visual models. Use when the user provides an EPLAN or vector PDF electrical schematic and asks "解析EPLAN图 / 抽元件清单 / 看导线怎么连 / 提取位号型号 / parse EPLAN drawing / extract components / wire topology". 中文：从 EPLAN / CAD 矢量 PDF 电气图纸中抽取结构化数据 —— 元件清单（位号/型号/数量）、导线连接拓扑（串并联、电能流向）、端子表、标题栏。基于 PDF 矢量几何直接提取（100%准确，无OCR误差），不依赖视觉模型。当用户提供 EPLAN 或矢量 PDF 电气原理图并要求"解析EPLAN图/抽元件清单/看导线怎么连/提取位号型号"时触发。
EN: Extract structured data from EPLAN/CAD vector PDF electrical drawings — component list (位号/型号/数量), wire/pin topology (导线连接、串并联、电能流向), terminal table, and…
As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, progress reporting
How to improve
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 841 tokens
- 100Running it twice. No mutating operations
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)
- -219 emoji in the instructions: noise for the model
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 613: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.