[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAARCK5CHQZ8H1YA76FXQR":3,"skill-same:01M7DAARCK5CHQZ8H1YA76FXQR":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M7DAARCK5CHQZ8H1YA76FXQR","findmy",null,"Track Apple devices\u002FAirTags via FindMy.app on macOS.","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fhermes\u002Fskills\u002Fapple\u002Ffindmy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: findmy\ndescription: \"Track Apple devices\u002FAirTags via FindMy.app on macOS.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [macos]\nmetadata:\n  hermes:\n    tags: [FindMy, AirTag, location, tracking, macOS, Apple]\n---\n\n# Find My (Apple)\n\nTrack Apple devices and AirTags via the FindMy.app on macOS. Since Apple doesn't\nprovide a CLI for FindMy, this skill uses AppleScript to open the app and\nscreen capture to read device locations.\n\n## Prerequisites\n\n- **macOS** with Find My app and iCloud signed in\n- Devices\u002FAirTags already registered in Find My\n- Screen Recording permission for terminal (System Settings → Privacy → Screen Recording)\n- **Optional but recommended**: Install `peekaboo` for better UI automation:\n  `brew install steipete\u002Ftap\u002Fpeekaboo`\n\n## When to Use\n\n- User asks \"where is my [device\u002Fcat\u002Fkeys\u002Fbag]?\"\n- Tracking AirTag locations\n- Checking device locations (iPhone, iPad, Mac, AirPods)\n- Monitoring pet or item movement over time (AirTag patrol routes)\n\n## Method 1: AppleScript + Screenshot (Basic)\n\n### Open FindMy and Navigate\n\n```bash\n# Open Find My app\nosascript -e 'tell application \"FindMy\" to activate'\n\n# Wait for it to load\nsleep 3\n\n# Take a screenshot of the Find My window\nscreencapture -w -o \u002Ftmp\u002Ffindmy.png\n```\n\nThen use `vision_analyze` to read the screenshot:\n```\nvision_analyze(image_url=\"\u002Ftmp\u002Ffindmy.png\", question=\"What devices\u002Fitems are shown and what are their locations?\")\n```\n\n### Switch Between Tabs\n\n```bash\n# Switch to Devices tab\nosascript -e '\ntell application \"System Events\"\n    tell process \"FindMy\"\n        click button \"Devices\" of toolbar 1 of window 1\n    end tell\nend tell'\n\n# Switch to Items tab (AirTags)\nosascript -e '\ntell application \"System Events\"\n    tell process \"FindMy\"\n        click button \"Items\" of toolbar 1 of window 1\n    end tell\nend tell'\n```\n\n## Method 2: Peekaboo UI Automation (Recommended)\n\nIf `peekaboo` is installed, use it for more reliable UI interaction:\n\n```bash\n# Open Find My\nosascript -e 'tell application \"FindMy\" to activate'\nsleep 3\n\n# Capture and annotate the UI\npeekaboo see --app \"FindMy\" --annotate --path \u002Ftmp\u002Ffindmy-ui.png\n\n# Click on a specific device\u002Fitem by element ID\npeekaboo click --on B3 --app \"FindMy\"\n\n# Capture the detail view\npeekaboo image --app \"FindMy\" --path \u002Ftmp\u002Ffindmy-detail.png\n```\n\nThen analyze with vision:\n```\nvision_analyze(image_url=\"\u002Ftmp\u002Ffindmy-detail.png\", question=\"What is the location shown for this device\u002Fitem? Include address and coordinates if visible.\")\n```\n\n## Workflow: Track AirTag Location Over Time\n\nFor monitoring an AirTag (e.g., tracking a cat's patrol route):\n\n```bash\n# 1. Open FindMy to Items tab\nosascript -e 'tell application \"FindMy\" to activate'\nsleep 3\n\n# 2. Click on the AirTag item (stay on page — AirTag only updates when page is open)\n\n# 3. Periodically capture location\nwhile true; do\n    screencapture -w -o \u002Ftmp\u002Ffindmy-$(date +%H%M%S).png\n    sleep 300  # Every 5 minutes\ndone\n```\n\nAnalyze each screenshot with vision to extract coordinates, then compile a route.\n\n## Limitations\n\n- FindMy has **no CLI or API** — must use UI automation\n- AirTags only update location while the FindMy page is actively displayed\n- Location accuracy depends on nearby Apple devices in the FindMy network\n- Screen Recording permission required for screenshots\n- AppleScript UI automation may break across macOS versions\n\n## Rules\n\n1. Keep FindMy app in the foreground when tracking AirTags (updates stop when minimized)\n2. Use `vision_analyze` to read screenshot content — don't try to parse pixels\n3. For ongoing tracking, use a cronjob to periodically capture and log locations\n4. Respect privacy — only track devices\u002Fitems the user owns\n","# Find My (Apple)\n\nTrack Apple devices and AirTags via the FindMy.app on macOS. Since Apple doesn't\nprovide a CLI for FindMy, this skill uses AppleScript to open the app and\nscreen capture to read device locations.\n\n## Prerequisites\n\n- **macOS** with Find My app and iCloud signed in\n- Devices\u002FAirTags already registered in Find My\n- Screen Recording permission for terminal (System Settings → Privacy → Screen Recording)\n- **Optional but recommended**: Install `peekaboo` for better UI automation:\n  `brew install steipete\u002Ftap\u002Fpeekaboo`\n\n## When to Use\n\n- User asks \"where is my [device\u002Fcat\u002Fkeys\u002Fbag]?\"\n- Tracking AirTag locations\n- Checking device locations (iPhone, iPad, Mac, AirPods)\n- Monitoring pet or item movement over time (AirTag patrol routes)\n\n## Method 1: AppleScript + Screenshot (Basic)\n\n### Open FindMy and Navigate\n\n```bash\n# Open Find My app\nosascript -e 'tell application \"FindMy\" to activate'\n\n# Wait for it to load\nsleep 3\n\n# Take a screenshot of the Find My window\nscreencapture -w -o \u002Ftmp\u002Ffindmy.png\n```\n\nThen use `vision_analyze` to read the screenshot:\n```\nvision_analyze(image_url=\"\u002Ftmp\u002Ffindmy.png\", question=\"What devices\u002Fitems are shown and what are their locations?\")\n```\n\n### Switch Between Tabs\n\n```bash\n# Switch to Devices tab\nosascript -e '\ntell application \"System Events\"\n    tell process \"FindMy\"\n        click button \"Devices\" of toolbar 1 of window 1\n    end tell\nend tell'\n\n# Switch to Items tab (AirTags)\nosascript -e '\ntell application \"System Events\"\n    tell process \"FindMy\"\n        click button \"Items\" of toolbar 1 of window 1\n    end tell\nend tell'\n```\n\n## Method 2: Peekaboo UI Automation (Recommended)\n\nIf `peekaboo` is installed, use it for more reliable UI interaction:\n\n```bash\n# Open Find My\nosascript -e 'tell application \"FindMy\" to activate'\nsleep 3\n\n# Capture and annotate the UI\npeekaboo see --app \"FindMy\" --annotate --path \u002Ftmp\u002Ffindmy-ui.png\n\n# Click on a specific device\u002Fitem by element ID\npeekaboo click --on B3 --app \"FindMy\"\n\n# Capture the detail view\npeekaboo image --app \"FindMy\" --path \u002Ftmp\u002Ffindmy-detail.png\n```\n\nThen analyze with vision:\n```\nvision_analyze(image_url=\"\u002Ftmp\u002Ffindmy-detail.png\", question=\"What is the location shown for this device\u002Fitem? Include address and coordinates if visible.\")\n```\n\n## Workflow: Track AirTag Location Over Time\n\nFor monitoring an AirTag (e.g., tracking a cat's patrol route):\n\n```bash\n# 1. Open FindMy to Items tab\nosascript -e 'tell application \"FindMy\" to activate'\nsleep 3\n\n# 2. Click on the AirTag item (stay on page — AirTag only updates when page is open)\n\n# 3. Periodically capture location\nwhile true; do\n    screencapture -w -o \u002Ftmp\u002Ffindmy-$(date +%H%M%S).png\n    sleep 300  # Every 5 minutes\ndone\n```\n\nAnalyze each screenshot with vision to extract coordinates, then compile a route.\n\n## Limitations\n\n- FindMy has **no CLI or API** — must use UI automation\n- AirTags only update location while the FindMy page is actively displayed\n- Location accuracy depends on nearby Apple devices in the FindMy network\n- Screen Recording permission required for screenshots\n- AppleScript UI automation may break across macOS versions\n\n## Rules\n\n1. Keep FindMy app in the foreground when tracking AirTags (updates stop when minimized)\n2. Use `vision_analyze` to read screenshot content — don't try to parse pixels\n3. For ongoing tracking, use a cronjob to periodically capture and log locations\n4. Respect privacy — only track devices\u002Fitems the user owns\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":35,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28},[29,30,31,32,33,34],"FindMy","AirTag","location","tracking","macOS","Apple",[36],"macos","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","upstream\u002Fhermes\u002Fskills\u002Fapple\u002Ffindmy","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill findmy",{"tool":51,"command":52},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill findmy",{"tool":54,"command":55},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill findmy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fhermes\u002Fskills\u002Fapple\u002Ffindmy\u002FSKILL.md",true,[],[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]