CtrlK
BlogDocsLog inGet started
Tessl Logo

findmy

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

53

Quality

61%

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/apple/findmy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The body is well-structured and highly actionable with concrete, executable AppleScript/screenshot/vision commands, but the batch AirTag-tracking loop lacks validation checkpoints, which caps workflow clarity, and a few minor placeholders and padding keep conciseness and actionability just below maximum.

Suggestions

Add validation/feedback checkpoints to the AirTag tracking loop (e.g., verify the screenshot was captured and non-empty, confirm FindMy is still in the foreground, and handle failures with a retry before continuing) to lift workflow clarity above the batch-operation cap of 3.

Replace the non-executable placeholder '# 2. Click on the AirTag item' with a concrete peekaboo/osascript click command so every step is copy-paste ready.

Trim the opening rationale sentence and obvious in-code comments (e.g., '# Open Find My app') to push conciseness toward a lean 5.

DimensionReasoningScore

Conciseness

The body is efficient with tight, executable code blocks and clear sections, but carries minor over-explanation (the opening rationale restatement and a few obvious in-code comments) that keeps it just short of a lean 5.

4 / 5

Actionability

Provides mostly executable, copy-paste-ready commands (osascript, screencapture, peekaboo, vision_analyze) covering common cases, but the AirTag workflow's step 2 is a non-executable placeholder comment rather than a concrete command, leaving a minor gap.

4 / 5

Workflow Clarity

Steps are sequenced across the methods and the AirTag workflow, but the 'while true' capture loop is a batch operation with no validation or error-recovery checkpoints, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Prerequisites, When to Use, Method 1/2, Workflow, Limitations, Rules) with no nested references and nothing that clearly needs splitting, though the flat single-file structure lacks the reference-based split that the 5 anchor implies.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 distinct, specific niche, but it omits any explicit 'when to use' trigger guidance and offers limited keyword variations, capping both completeness and trigger term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks where their iPhone, iPad, AirPods, or AirTag is, or wants to track an item's location over time.'

Expand trigger terms with common synonyms users say ('Find My', 'iPhone', 'iPad', 'where is my', 'locate my device') to improve keyword coverage.

List a couple more concrete actions (e.g., 'view device locations, switch Devices/Items tabs, monitor AirTag movement over time') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ("Apple devices/AirTags") and one concrete action ("Track ... via FindMy.app on macOS"), but offers only a single verb and no broader coverage of capabilities, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Has a clear 'what' ("Track Apple devices/AirTags via FindMy.app on macOS") but no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong natural terms like "AirTags" and "Apple devices" that users would actually say, but misses common variations and synonyms (e.g., "Find My", "iPhone", "iPad", "where is my"), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Carves a clear, specific niche (FindMy.app tracking on macOS) with low overlap risk, but the bare description lacks explicit trigger phrases, leaving it just short of the minimal-conflict 5 anchor.

4 / 5

Total

13

/

20

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.