BD bimwing-convert
把本地 BIM / 三维模型或图纸（.rvt/.nwd/.ifc/.dwg/.skp/.obj/.fbx 等）上传到 BIMWing（垒知翼）做在线轻量化转换，生成可在浏览器直接在线浏览三维模型的分享链接。除上传外，还支持列出账号下全部模型、查看转码状态、为已有模型生成链接。需要 BIMWing 账号，会将账号密码以明文保存在本机 config.local.json（仅本机、gitignore）以便复用，且仅在你主动提供时保存。支持 API 直连（主）与 Playwright 浏览器自动化（兜底）。
把本地 BIM / 三维模型或图纸（.rvt/.nwd/.ifc/.dwg/.skp/.obj/.fbx 等）上传到 BIMWing（垒知翼）做在线轻量化转换，生成可在浏览器直接在线浏览三维模型的分享链接。除上传外，还支持列出账号下全部模型、查看转码状态、为已有模型生成链接。需要 BIMWing…
As a process D 43/100 · Unfinished process — 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: 0. 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 "agent_created"
Process rating: all ten parameters 43/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1658 tokens
- low The response is described with custom markup (7 tags): a typed call is more reliable
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 252: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 49 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.