AD wps-macos-helper
Help macOS users work with WPS Office more reliably when WPS is explicitly part of the document workflow. Use for preparing, converting, reviewing, exporting, or troubleshooting files that will be opened or checked in WPS on macOS, especially for Word/docx, PDF, Markdown, PowerPoint, and Excel workflows. Useful for: (1) preparing content before opening in WPS, (2) reducing WPS/Word compatibility issues, (3) choosing safe conversion workflows, (4) export and formatting guidance on macOS, and (5) troubleshooting layout, fonts, tables, page breaks, headers/footers, and PDF output.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, 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: 10. 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: Help macOS users work with WPS Office more reliably when WPS is ex… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 48/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
- 30Running it twice. 1 mutating operations with no state check
- 85Steps. 15 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 332 tokens
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 584: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 15 items
- +4Reference files are cited in the instructions (6 of 6)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.