CtrlK
BlogDocsLog inGet started
Tessl Logo

findmy

Track Apple devices/AirTags via FindMy.app on macOS.

60

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/apple/findmy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is concise and highly actionable with copy-paste-ready commands and well-organized sections, but the AirTag-over-time tracking loop lacks validation/verification checkpoints, capping workflow clarity at 2.

Suggestions

Add a validation step inside the capture loop, e.g. verify the screenshot file is non-empty and FindMy is still foregrounded before sleeping, with a re-activate-and-retry path on failure.

Make the AirTag workflow's click step concrete with a peekaboo/osascript command instead of the prose instruction 'Click on the AirTag item (stay on page)'.

Consider documenting how to detect and recover from the 'AirTag only updates while page is open' failure mode as an explicit checkpoint in the tracking workflow.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude's competence, avoids explaining what AirTags or FindMy are, and presents only prerequisites, executable commands, and short workflows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides copy-paste-ready, executable commands (osascript, screencapture, peekaboo, vision_analyze) with real flags and concrete example invocations, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The AirTag-over-time workflow is numbered and sequenced, but the recurring 'while true' capture loop has no validation/verification checkpoint (e.g., confirming the screenshot succeeded or FindMy stayed foregrounded); per the guidelines missing validation in a batch/recurring operation caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Content is well-organized into clear single-level sections (Prerequisites, When to Use, Method 1/2, Workflow, Limitations, Rules) with no nested or broken references; the monolithic single-file scope is acceptable and navigation is easy.

3 / 3

Total

11

/

12

Passed

Description

57%

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 distinctive and names a clear niche, but it is terse: it states a single action without multiple concrete capabilities and omits any explicit 'Use when' trigger guidance, capping specificity and completeness at 2.

Suggestions

Add a 'Use when...' clause listing natural triggers, e.g. 'Use when the user asks where their AirTag, iPhone, iPad, or Mac is, or wants to track a lost device over time.'

Expand the action list beyond 'Track' to concrete capabilities like 'view current locations, switch between Devices and Items tabs, and log AirTag position over time'.

Include common trigger-term variations such as 'Find My', 'lost device', and specific device names (iPhone, iPad, Mac, AirPods) for better trigger coverage.

DimensionReasoningScore

Specificity

"Track Apple devices/AirTags via FindMy.app on macOS" names the domain and a concrete action (track) with specific targets (devices, AirTags), but does not list multiple distinct actions, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does (track devices/AirTags via FindMy.app) but provides no 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('Apple devices', 'AirTags', 'FindMy.app'), but misses common variations users would say such as 'Find My', 'iPhone/iPad/Mac location', or 'lost', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The FindMy.app/macOS/AirTag niche is highly specific with distinct triggers and is unlikely to conflict with other skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.

3 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.