SKILLEMALL.ai
GitHub ↗ RU Sign in

CD macOS

macOS system administration, command-line differences from Linux, and automation best practices.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 404 tokens Open the sourcegithub.com↗ analyzed 3 d ago

macOS system administration, command-line differences from Linux, and automation best practices.

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentsSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
71/100
safety, quality, tests
Safety 60%
79
Quality 40%
60
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5

✓ No critical or high findings

Medium and low: 5
  • medium Dangerous commands cmd-persistence SKILL.md:36
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - User agents: `~/Library/LaunchAgents/` — runs as user when logged in
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:37
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - System daemons: `/Library/LaunchDaemons/` — runs at boot as root
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:38
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - Load: `launchctl load -w ~/Library/LaunchAgents/com.example.plist`
    quoted
  • medium Dangerous commands cmd-disable-security SKILL.md:104
    Disables a security control (Defender, Gatekeeper, SIP, firewall, execution policy) (quoted — discussed, not commanded)
    - Disable (Recovery Mode only): `csrutil disable` — not recommended for production
    quoted
  • low Dangerous commands cmd-quarantine-file SKILL.md:67
    Removes the macOS quarantine flag from one file (usual for a downloaded CLI; make sure the file is the intended binary) (quoted — discussed, not commanded)
    - Quarantine removal: `xattr -d com.apple.quarantine app.app`
    quoted

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 45/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 72 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1404 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 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)
  • +3Description length 96: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 72 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.