CtrlK
BlogDocsLog inGet started
Tessl Logo

remote-mac

Remote Macs: MacBook, Mac Studio, clawmac, megaclaw, Tailscale, SSH, OpenClaw.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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, high-density operational reference with executable commands, explicit validation and approval checkpoints for risky operations, and clean sectioning, so it scores at the top of every content dimension.

DimensionReasoningScore

Conciseness

The body is dense with concrete facts (hostnames, Tailscale IPs, ports, paths, users) and assumes Claude already knows what SSH, tmux, and Tailscale are, with no padding or concept explanations — every token earns its place.

3 / 3

Actionability

It provides copy-paste-ready executable commands (e.g. 'ssh -o RequestTTY=no -o RemoteCommand=none HOST', 'dns-sd -B _ssh._tcp local', 'lsof -nP -iTCP:18789 -sTCP:LISTEN', 'launchctl list') with specific hosts, users, and ports, matching the 'fully executable' anchor.

3 / 3

Workflow Clarity

Discovery is a numbered sequence with an explicit stop checkpoint, OpenClaw sections give verifiable 'healthy shape' checklists, and the Live Testing Policy supplies explicit per-task approval checkpoints for destructive/production operations, satisfying the validation requirement.

3 / 3

Progressive Disclosure

No bundle files exist and the content is appropriately inline unique operational facts; external references (computers.yaml, agents.yaml, repo docs/AGENTS) are clearly signaled and one level deep, and the skill is well-organized into clear sections, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

62%

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 frontmatter is a terse inventory of host names and tooling keywords with excellent trigger-term and distinctiveness coverage, but it omits concrete capability verbs and lacks an explicit 'Use when' trigger clause, capping specificity and completeness.

Suggestions

Add concrete action verbs to the description so it states what the skill does (e.g. 'SSH into, diagnose, configure, and run checks on Peter's remote Macs').

Append an explicit trigger clause such as 'Use when the user mentions MacBook, Mac Studio, clawmac, megaclaw, Tailscale, or asks to run or check something on one of Peter's Macs.'

Keep the distinctive proper nouns but pair them with the purpose so the description answers both what and when within the frontmatter.

DimensionReasoningScore

Specificity

The description is a noun list ("MacBook, Mac Studio, clawmac, megaclaw, Tailscale, SSH, OpenClaw") naming the domain and items but no concrete actions, matching the 'vague or no actions' anchor rather than the 'names domain and some actions' level which requires verbs.

1 / 3

Completeness

It states the 'what' (which remote Macs) but the description field lacks an explicit 'Use when...' trigger clause, so per the judging guideline a missing trigger clause caps completeness at 2 even though the body later supplies the trigger.

2 / 3

Trigger Term Quality

It surfaces natural terms a user would actually say — "MacBook", "Mac Studio", "Tailscale", "SSH" — giving strong coverage of the keywords that would surface this skill, matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Distinctive proper nouns like "clawmac", "megaclaw", and "OpenClaw" carve a clear niche with triggers unlikely to fire for any other skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

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.