AC feishu-bitable-import
🚀 企业级飞书多维表格（Bitable）数据导入工具，从 CSV/Excel/JSON 批量导入数据到飞书多维表格，自动智能推断字段类型，增量更新/全量覆盖/仅新增三种同步模式，支持从本地数据一键创建新表格。适合企业数据中台导出、业务报表同步、定时数据更新、团队数据协作场景。使用当需要将本地CSV/Excel数据批量导入飞书多维表格、从外部系统导出数据到飞书、批量创建多维表格业务记录时触发。Triggers: "导入CSV到飞书", "批量导入飞书表格", "飞书数据导入", "feishu bitable import", "创建飞书表格", "数据导入飞书"。
As a process C 53/100 · Has gaps — 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: 🚀 企业级飞书多维表格（Bitable）数据导入工具，从 CSV/Excel/JSON 批量导入数据到飞书多维表格，自动智能推断字… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 773 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 286: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.