SKILLEMALL.ai
GitHub ↗ RU Sign in

CC fleet-maintenance

Mac fleet inventory and upkeep with full/worker profiles: collect installed apps and packages, compare desired versus observed state, audit local-account escrow references, update Homebrew/global packages, safely sync repos and Xcode, and report disk, service, backup, update, and security health.

steipete/agent-scripts Agent Skills author: steipete MIT 18 files · 15 scripts body ≈ 4 733 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Mac fleet inventory and upkeep with full/worker profiles: collect installed apps and packages, compare desired versus observed state, audit local-account…

As a process C 51/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
92
Quality 40%
73
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Inputs and preconditions w 11
30
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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Dangerous commands cmd-persistence SKILL.md:210
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)
    - failed Brew services and role-specific LaunchAgents/daemons
    security skill
  • low Dangerous commands cmd-shell-rc scripts/op-profile-audit.sh:316
    Writes to a shell startup file (documentation of a security skill)
    printf 'op-profile: refusing zprofile without a secure .profile token loader: %s\n' "$zprofile" >&2
    security skill
  • low Dangerous commands cmd-shell-rc scripts/test-octopool-audit.sh:149
    Writes to a shell startup file (test fixture / example file; documentation of a security skill)
    printf '# unrelated startup content\nexport FLEET_TEST=1\n' >"$case_root/home/.zprofile"
    fixturesecurity skill
  • low Dangerous commands cmd-shell-rc scripts/test-octopool-audit.sh:162
    Writes to a shell startup file (test fixture / example file; documentation of a security skill)
    cat >"$case_root/home/.zprofile" <<'PROFILE'
    fixturesecurity skill

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 13 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4733 tokens
  • 100Steps. 49 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 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
  • -35 of 15 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 297: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 49 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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