AB feishu-workflow-cli
Orchestrate complex Feishu/Lark workflows using the official lark CLI (v1.0.40+, 200+ commands, 17 domains). Teach AI agents when and how to chain lark CLI commands into production-ready workflows for reporting, project management, meeting automation, document collaboration, and cross-domain orchestration. Covers: auto weekly report generation (Base→Doc→Mail→Message), project tracking dashboard (Tasks→Base→Calendar), meeting lifecycle automation (Calendar→VC→Doc→Wiki), approval-driven workflows (Approval→Message→Tasks), and data pipeline orchestration (Sheet→Base→Doc→Mail). Triggers on: 飞书CLI工作流, feishu workflow, lark CLI automation, 飞书自动化, feishu report automation, lark agent workflow, 飞书周报自动化, feishu meeting automation, lark task management, 飞书审批流程, feishu doc collaboration, lark base workflow, 飞书多维表格工作流, feishu calendar automation, lark mail automation, 飞书邮件自动化, agent feishu orchestration, AI飞书工作流
Orchestrate complex Feishu/Lark workflows using the official lark CLI (v1.0.40+, 200+ commands, 17 domains). Teach AI agents when and how to chain lark CLI…
As a process B 78/100 · Nearly there — weak spots: running it twice
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: 2. 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 78/100
- 30Running it twice. 21 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 37 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3056 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 913: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 25 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.