AC sysu-anything-cli
Use when the user wants SYSU campus help through the SYSU Anything CLI, including natural-language requests such as 查课表、今天有什么课、教务系统、请假、雨课堂作业、ddl、签到、预约健身房、预约体育馆、订球场、查班车、查岐关、图书馆研讨室、宣讲会、招聘会、岗位投递、勤工助学、学工系统、USC课室预约、会议场所预约、学生活动预约、交叉探索、校园问答、校内资讯, or fuzzy requests to handle campus services, bookings, schedules, reminders, and CAS-based login recovery.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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: 21. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 47 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 981 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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 346: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 47 items
- +4Reference files are cited in the instructions (15 of 15)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.