CtrlK
BlogDocsLog inGet started
Tessl Logo

fleet-maintenance

Mac fleet upkeep: global packages, safe repo sync, Xcode, disk, Trash, and health.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fleet-maintenance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable, well-sequenced operational skill with strong validation checkpoints for destructive and batch operations; its main weakness is that substantial policy detail is inlined rather than progressively disclosed into reference files.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and command-heavy with no concept explanations Claude would already know; nearly every token carries an operational constraint or executable instruction, fitting the 'lean and efficient' anchor.

3 / 3

Actionability

It provides fully executable, copy-paste-ready commands (audit/update scripts, git fetch/merge invocations, brew/npm commands, the Trash path-verification block) with specific flags and concrete examples.

3 / 3

Workflow Clarity

A numbered Run order sequences the multi-step pass, and risky/batch operations have explicit validation checkpoints and feedback loops (recheck before mutation, post-merge requirements, fetch-timeout -> mark pending -> continue).

3 / 3

Progressive Disclosure

Executable logic is well offloaded to one-level-deep, real scripts (host-health-audit.sh, repo-sync-audit.sh, repo-sync-update.sh) and sections are clearly organized, but dense policy prose (repo-sync merge semantics, package-ownership investigation) is inlined in SKILL.md rather than split into reference docs.

2 / 3

Total

11

/

12

Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a clear fleet-maintenance domain with several concrete areas, but it omits any explicit 'when to use' trigger guidance and uses topic nouns rather than specific verb-based actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when maintaining a fleet of Macs: updating global packages, syncing repos, or auditing disk and health.'

Reframe the capability list as concrete actions (e.g. 'update Homebrew and global npm packages, fast-forward safe repos, sync Xcode') to raise specificity.

Include natural trigger variations a user might say ('update my Macs', 'sync my repos', 'free up disk') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names a concrete domain and several capability areas ('global packages, safe repo sync, Xcode, disk, Trash, and health') but lists topics as nouns rather than multiple specific concrete actions, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It clearly answers 'what' (Mac fleet upkeep across the listed areas) but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Terms like 'Mac fleet', 'repo sync', 'Xcode', 'Trash', and 'packages' are natural things a user would say, but coverage lacks common variations and there is no explicit trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

'Mac fleet upkeep' is a fairly specific niche, but without an explicit trigger it could still overlap with adjacent Mac or Xcode-maintenance skills.

2 / 3

Total

8

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.