Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Connect agents to Apple Health exports with MCP setup, schema validation, and privacy-safe analysis.
Connect agents to Apple Health exports with MCP setup, schema validation, and privacy-safe analysis.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines.
User wants agents to read Apple Health data for trends, summaries, or SQL analysis. Agent handles export validation, MCP server wiring, and safe query/report flows without exposing private health records.
Memory lives in ~/apple-health/. See memory-template.md for setup. ~/apple-health/ |-- memory.md # Status, client integration state, latest export path |-- integrations.md # Connected MCP clients and validation notes |-- query-log.md # Reusable SQL/report prompts and known-good outputs `-- archive/ # Retired paths and old troubleshooting notes
Use these files on demand instead of overloading the main instructions. TopicFileSetup processsetup.mdMemory templatememory-template.mdMCP client wiringmcp-config.mdQuery recipesquery-recipes.mdFallback CLI pathsfallback-cli.md
Start by clarifying one of these modes: csv-export using Apple Health CSV exports and MCP not-now if user is only planning and does not want setup yet Never imply direct HealthKit API access from terminal agents. This skill works from exported data.
Require a real export folder before configuration: Must exist locally and be readable Must include files matching HKQuantityTypeIdentifier*.csv, HKCategoryTypeIdentifier*.csv, or HKWorkoutActivityType*.csv Must not be an empty unzip folder If validation fails, stop and fix data path first.
Before wiring MCP, verify runtime: node -v should be an LTS line (18, 20, or 22) If npx @neiltron/apple-health-mcp fails with missing duckdb.node, switch to LTS Node and retry Confirm HEALTH_DATA_DIR is available as an absolute path Do not continue while runtime is incompatible.
Use the MCP server command from mcp-config.md: Command: npx Args: [@neiltron/apple-health-mcp] Env: HEALTH_DATA_DIR=/absolute/path/to/export Never continue with placeholders or relative paths that are not verified.
First run schema discovery (health_schema) and map available tables. Only then run health_query or health_report. If table names differ from expectation, adapt SQL to discovered schema instead of forcing guessed names.
Every analytical query should include time bounds and clear units. Prefer rolling windows (last 7d, 30d, 90d) and compare at most two windows at once. Avoid unbounded full-history scans unless user explicitly asks.
Log last export timestamp in memory and warn when data is stale. If user needs current-day insights, request a new iPhone export before claiming "latest" trends.
Assuming live HealthKit access from CLI agents -> setup fails because only exported data is available Using wrong export path in MCP env -> server starts but returns no data Running SQL before schema discovery -> queries fail on wrong table names Unbounded queries on large exports -> slow analysis and noisy output Reporting "today" metrics from stale export -> inaccurate recommendations Running MCP package on non-LTS Node -> DuckDB native module errors can break startup
EndpointData SentPurposehttps://registry.npmjs.orgPackage install metadata onlyDownload MCP server packagehttps://raw.githubusercontent.comPublic markdown onlyRead validated fallback skill docshttps://apps.apple.comManual app download trafficInstall CSV export app on iPhone No health record rows should be sent externally by default.
Data that leaves your machine: Package install requests to npm Optional app download traffic from App Store Data that stays local: Apple Health CSV exports MCP query outputs and summaries Skill memory in ~/apple-health/ This skill does NOT: Access iCloud Health data directly Bypass Apple permission prompts Upload health CSVs unless the user asks for that explicitly
By using this skill, you rely on third-party tooling (@neiltron/apple-health-mcp and the chosen iPhone export app). Only install and run if you trust those tools.
Install with clawhub install <slug> if user confirms: health - General health guidance boundaries and framing ios - iOS-specific setup and platform troubleshooting sleep - Sleep trend interpretation workflows api - Reliable API and integration debugging habits swift - HealthKit-side implementation context when app code is involved
If useful: clawhub star apple-health Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.