Official recipe · Computer tasks

Locate an owned item and review its position history

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Owners trying to recover an item need readable location evidence and may need to compare its positions over time.

Agent job

Read the selected owner-registered item's Find My location and optionally compile timestamped UI observations into a position history.

Expected output

A current location observation or approved position-history summary for the owner's property.

Where this framing comes from

Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing

Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

An owner looking for a misplaced item may see a map marker without noticing that the observation is old or approximate. Repeated captures can suggest movement even when the evidence is too sparse to reconstruct a reliable route.
This job could summarize the selected property's location observations with timestamps and uncertainty intact. Keeping the scope tied to recovering the owner's item prevents a useful retrieval aid from expanding into surveillance of people.

Why an agent / simpler alternative

Useful judgment: Interpret UI timestamps and uncertainty, distinguish last-seen from current observations and avoid inventing paths between points.
Simpler alternative: Use the device service's own item view when one observation answers the question.
Unsuitable when: The request tracks another person without consent, ownership is unclear or location access would exceed the owner's authorization.

Proposed inputs

Name
Owned-item scope
Owner
Verified owner
Minimum scope
Specific registered item and recovery purpose
Quality check
Confirm ownership and exclude person-tracking intent
Name
Location observations
Owner
Owner-authorized source
Minimum scope
Minimum necessary screenshots with displayed time and accuracy
Quality check
Distinguish capture time from reported location time

Access and setup — proposed or unknown

Proposed minimum: Use fictional location displays first; no account access, screen recording or collection of real positions.
Compatibility unknowns: Current device-service permissions, observation freshness, UI behavior and runtime compatibility are unknown.
External actions requiring approval: Account/screen access, position-history collection and sharing location evidence require explicit scope; tracking people without consent is excluded.

Expected deliverable and review checks

Proposed artifact: Property-location summary with observation time, freshness/accuracy caveats and any approved history clearly bounded.
Critical checks: Verify selected item; preserve last-seen wording; omit unnecessary addresses; never connect sparse points into a claimed route.
Missing output evidence: This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

Signal
An old marker is called the current location
Why it matters
The owner may search the wrong place
Proposed response
Show the displayed age prominently and qualify the observation.
Signal
Two noisy points imply movement
Why it matters
Location uncertainty becomes an invented journey
Proposed response
Report separate observations without a route conclusion.

Effort and cost — unknown

Setup work: Confirm ownership, purpose and minimum history scope.
Ongoing review: Owner reviews stale/uncertain observations and controls any sharing.
Unknowns: Location accuracy, update frequency, device availability and review effort are unknown.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Invent three item displays with different observation/capture times and overlapping uncertainty areas; summarize without real coordinates.
Acceptance checks: Distinguish stale from fresh; infer no route or person's movement; collect no real location.
Stop conditions: Stop if ownership, consent or the property-only purpose is unclear.

Limits

Location observations cannot establish an exact position, possession by a person or a safe retrieval action.

Tasks: Home & errands Data & analysis

Useful for: Personal and household

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Hermes AgentIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/NousResearch/hermes-agent/blob/main/skills/apple/findmy/SKILL.md ↗

Attributed to: Hermes Agent

Official recipe

Original action type: computer_action
What the source supports: Select an owner-registered device or item in Find My, read its location from UI captures and optionally compile timestamped observations into a route history.
Source outcome limits: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: The source restricts tracking to devices or items the user owns; required screen-recording and account permissions are prerequisites.
Named tools: Find My on macOS; AppleScript or Peekaboo; screenshots; vision_analyze
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: check Canadian account/device support and location privacy; never infer consent to track family members or employees from ownership of a tag.
Recommended approval boundaries: Approve location access and any repeated recording; scope to the owner’s property, avoid tracking people, and control where screenshots are processed or retained.