AD shortcuts-automator
Run and manage macOS Shortcuts directly from OpenClaw. Use when user wants to: (1) Run a specific shortcut by name, (2) List all available shortcuts, (3) View details of a shortcut, (4) Sign/unsign shortcuts for automation, (5) Execute any macOS Shortcut workflow. Triggers include "run shortcut", "execute shortcut", "list shortcuts", "run automation", "show shortcuts", "what shortcuts do I have".
As a process D 46/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: 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: Run and manage macOS Shortcuts directly from OpenClaw. Use when us… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 46/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (shortcuts-automator) differs from the folder (openclaw-skill-shortcuts-automator)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 19 steps
- 100Execution cost. Instruction body is 1061 tokens
- 100Running it twice. Mutating operations check current state
- 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 (4 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 399: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.