AF turix-mac
Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.
Computer Use Agent (CUA) for macOS automation using TuriX.
As a process F 35/100 · Will not run — References files that are not bundled: examples/config.json
ProcedureWordGitHubSoftware developmentInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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
missing-refreference to a missing file: examples/config.json
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: examples/config.json
- 0Tools and files. 1 referenced file(s) missing: examples/config.json
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (turix-mac) differs from the folder (turix-cua)
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 59 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3232 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 204: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (21 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.