Axiom Health logo

Axiom Health

CommunityPopular
CharlesWiltgen
axiom-health

Use when working with HealthKit, WorkoutKit, health data, workouts, or fitness features on iOS or watchOS. Covers permissions, queries, background delivery, custom workouts, multidevice coordination.

Overview

PublisherCharlesWiltgen
RepositoryAxiom
Skill nameaxiom-health
Stars
1.2K
Forks
86
Bundled files
9
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by CharlesWiltgen on GitHub. Read the source before you install it.

Installation

Install the Axiom Health AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/CharlesWiltgen/Axiom/tree/main/axiom-codex/skills/axiom-health
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/CharlesWiltgen/Axiom.git /tmp/Axiom
mkdir -p .claude/skills
cp -r /tmp/Axiom/axiom-codex/skills/axiom-health .claude/skills/axiom-health
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Axiom Health in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Axiom Health on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Axiom Health is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

HealthKit and WorkoutKit

You MUST use this skill for ANY HealthKit or WorkoutKit development including authorization, data queries, background delivery, workout sessions, planned workouts, wellbeing APIs (State of Mind), Medications, and Health Records.

Quick Reference

Symptom / TaskReference
HealthKit framework model, HKHealthStore, data types, sample vs characteristic dataSee skills/fundamentals.md
Capability setup, requestAuthorization, purpose strings, read-asymmetry, privacySee skills/authorization-and-privacy.md
HKSampleQuery, Swift Concurrency query APIs, HKStatisticsCollectionQuery, sample writesSee skills/queries.md
Anchored queries, observer queries, HKDeletedObject, background-delivery entitlementSee skills/sync-and-background.md
HKWorkoutSession, HKLiveWorkoutBuilder, recovery, multi-device, iOS/iPadOS/watchOS workout trackingSee skills/workouts.md
Workout zones (heart-rate/power effort bands), live + retrospective OS27See skills/workouts.md
WorkoutKit custom/planned workouts, scheduling, swimming workouts, previewingSee skills/workoutkit.md
State of Mind, Medications API, symptom logging, menopausal state, wellbeing APIs OS27See skills/wellbeing-and-medications.md
Health Records (FHIR), Mobility Health App, motion-based healthSee skills/clinical-and-mobility.md

Cross-Suite Routes

These topics overlap with HealthKit/WorkoutKit but live in separate suites:

watchOS presentation
  • Watch-specific workout presentation (Always On, Smart Stack), complication surfaces → See axiom-watchos
  • Workout app structure on Apple Watch → See axiom-watchos (skills/platform-basics.md)
Concurrency
  • Swift 6 concurrency, actors, Sendable → See axiom-concurrency
  • HealthKit queries bridging to Swift Concurrency → skills/queries.md is the canonical example
SwiftUI
  • Charts rendering for health data → See axiom-swiftui
  • @Observable view models for health data → See axiom-swiftui
Data and sync
  • General cross-platform sync patterns (CloudKit, GRDB) → See axiom-data
  • HealthKit anchored/observer queries as a generalizable sync mechanism → skills/sync-and-background.md
Security and privacy
  • Keychain storage, encryption, data-protection entitlements → See axiom-security

Conflict Resolution

axiom-health vs axiom-watchos: For workout apps on Apple Watch:

  1. Use axiom-health for HKWorkoutSession lifecycle, HKLiveWorkoutBuilder, recovery APIs, multi-device mirroring — these are HealthKit concepts, not watch concepts
  2. Use axiom-watchos for watch-specific presentation: Always On display, Smart Stack placement, watchOS background mode coordination
  3. Both apply for a watch-native workout app — start with axiom-health for session lifecycle, then axiom-watchos for presentation

axiom-health vs axiom-concurrency: For HealthKit query patterns:

  1. Use axiom-health for which query type to choose and HealthKit-specific gotchas
  2. Use axiom-concurrency for general Swift 6 actor isolation rules that apply to query callbacks

axiom-health vs axiom-data: For change-tracked data synchronization:

  1. Use axiom-health for HKAnchoredObjectQuery, HKObserverQuery, HKDeletedObject
  2. Use axiom-data for application-level data sync across devices (CloudKit, GRDB, SwiftData)

Decision Tree

dot
digraph health {
    start [label="HealthKit / workout task" shape=ellipse];
    what [label="What area?" shape=diamond];

    start -> what;
    what -> "skills/fundamentals.md" [label="framework basics, data types"];
    what -> "skills/authorization-and-privacy.md" [label="permissions, purpose strings, privacy"];
    what -> "skills/queries.md" [label="reading data, rollups, writes"];
    what -> "skills/sync-and-background.md" [label="change tracking, background delivery"];
    what -> "skills/workouts.md" [label="HKWorkoutSession, live workouts"];
    what -> "skills/workoutkit.md" [label="planned/custom workouts"];
    what -> "skills/wellbeing-and-medications.md" [label="State of Mind, Medications"];
    what -> "skills/clinical-and-mobility.md" [label="Health Records, Mobility"];
    what -> "axiom-watchos" [label="watch-specific presentation"];
    what -> "axiom-concurrency" [label="general actor isolation rules"];
    what -> "axiom-swiftui" [label="Charts, data visualization"];
}

Resources

WWDC: 2019-218, 2020-10182, 2020-10184, 2020-10664, 2021-10009, 2021-10287, 2022-10005, 2023-10016, 2023-10023, 2024-10084, 2024-10109, 2025-321, 2025-322

Docs: /healthkit, /healthkit/about-the-healthkit-framework, /healthkit/authorizing-access-to-health-data, /healthkit/protecting-user-privacy, /healthkit/reading-data-from-healthkit, /healthkit/running-queries-with-swift-concurrency, /healthkit/executing-anchored-object-queries, /healthkit/executing-observer-queries, /healthkit/hkworkoutsession, /healthkit/hklivewobuilder, /workoutkit, /healthkit/accessing-health-records

Skills: axiom-watchos, axiom-concurrency, axiom-swiftui, axiom-data, axiom-security

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Axiom Health AI skill do?

Use when working with HealthKit, WorkoutKit, health data, workouts, or fitness features on iOS or watchOS. Covers permissions, queries, background delivery, custom workouts, multidevice coordination.

Why use Axiom Health on TypingMind?

Because you install it once and use it with any model. Axiom Health is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Axiom Health in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/CharlesWiltgen/Axiom/tree/main/axiom-codex/skills/axiom-health. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Axiom Health?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Axiom Health?

As many as you like. As long as a model supports skills, you can use Axiom Health with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Axiom Health AI skill free?

Yes. It is published on GitHub by CharlesWiltgen under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇