AB fcalendar-skill
fcalendar-skill is a Chinese date/time expression recognition and holiday query tool. **Trigger this skill whenever users mention any time-related terms**, including but not limited to: 明天, 后天, 下周, 春节, 国庆节, Christmas, Monday, etc. It can identify and annotate time expressions in natural language text (Chinese and English), resolve them to exact calendar dates, and query Chinese public holidays and normal weekends within a specified time range. Use this skill when users ask about dates, time expressions, schedules, holidays, or when you need to resolve relative time references to concrete dates.
As a process B 75/100 · Nearly there — weak spots: result and completion, inputs and preconditions
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: 4. 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: fcalendar-skill is a Chinese date/time expression recognition and … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 75/100
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 20 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1812 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +2Single-language instructions
- +3Description length 601: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.