AB feishu-candy
Convert ICS (iCalendar) files to JSON for Feishu calendar integration. Use when user needs to import calendar events from ICS format, export Feishu calendar to JSON, or process calendar files for Feishu calendar apps. Triggers on: ICS to JSON conversion, calendar file parsing, Feishu calendar data transformation.
As a process B 76/100 · Nearly there — weak spots: 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: 3. 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: Convert ICS (iCalendar) files to JSON for Feishu calendar integrat… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 76/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 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
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 242 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)
- +1No license
- +2Single-language instructions
- +3Description length 314: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.