Read and write health and fitness data from the Apple Health store. Covers authorization, queries, writing samples, background delivery, and workout sessions. Targets Swift 6.3 / iOS 26+.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhealthkitExecute the skills CLI command in your project's root directory to begin installation:
Fetches healthkit from dpearson2699/swift-ios-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate healthkit. Access via /healthkit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
372
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
372
stars
Read and write health and fitness data from the Apple Health store. Covers authorization, queries, writing samples, background delivery, and workout sessions. Targets Swift 6.3 / iOS 26+.
NSHealthShareUsageDescription (read) and NSHealthUpdateUsageDescription (write) to Info.plistAlways check availability before accessing HealthKit. iPad and some devices do not support it.
import HealthKit
let healthStore = HKHealthStore()
guard HKHealthStore.isHealthDataAvailable() else {
// HealthKit not available on this device (e.g., iPad)
return
}
Create a single HKHealthStore instance and reuse it throughout your app. It is thread-safe.
Request only the types your app genuinely needs. App Review rejects apps that over-request.
func requestAuthorization() async throws {
let typesToShare: Set<HKSampleType> = [
HKQuantityType(.stepCount),
HKQuantityType(.activeEnergyBurned)
]
let typesToRead: Set<HKObjectType> = [
HKQuantityType(.stepCount),
HKQuantityType(.heartRate),
HKQuantityType(.activeEnergyBurned),
HKCharacteristicType(.dateOfBirth)
]
try await healthStore.requestAuthorization(
toShare: typesToShare,
read: typesToRead
)
}
The app can only determine if it has not yet requested authorization. If the user denied access, HealthKit returns empty results rather than an error -- this is a privacy design.
let status = healthStore.authorizationStatus(
for: HKQuantityType(.stepCount)
)
switch status {
case .notDetermined:
// Haven't requested yet -- safe to call requestAuthorization
break
case .sharingAuthorized:
// User granted write access
break
case .sharingDenied:
// User denied write access (read denial is indistinguishable from "no data")
break
@unknown default:
break
}
Use HKSampleQueryDescriptor (async/await) for one-shot reads. Prefer descriptors over the older callback-based HKSampleQuery.
func fetchRecentHeartRates() async throws -> [HKQuantitySample] {
let heartRateType = HKQuantityType(.heartRate)
let descriptor = HKSampleQueryDescriptor(
predicates: [.quantitySample(type: heartRateType)],
sortDescriptors: [SortDescriptor(\.endDate, order: .reverse)],
limit: 20
)
let results = try await descriptor.result(for: healthStore)
return results
}
// Extracting values from samples:
for sample in results {
let bpm = sample.quantity.doubleValue(
for: HKUnit.count().unitDivided(by: .minute())
)
print("\(bpm) bpm at \(sample.endDate)")
}
Use HKStatisticsQueryDescriptor for aggregated single-value stats (sum, average, min, max).
func fetchTodayStepCount() async throws -> Double? {
let calendar = Calendar.current
let startOfDay = calendar.startOfDay(for: Date())
let endOfDay = calendar.date(byAdding: .day, value: 1, to: startOfDay)!
let predicate = HKQuery.predicateForSamples(
withStart: startOfDay, end: endOfDay
)
let stepType = HKQuantityType(.stepCount)
let samplePredicate = HKSamplePredicate.quantitySample(
type: stepType, predicate: predicate
)
let query = HKStatisticsQueryDescriptor(
predicate: samplePredicate,
options: .cumulativeSum
)
let result = try await query.result(for: healthStore)
return result?.sumQuantity()?.doubleValue(for: .count())
}
Options by data type:
.cumulativeSum.discreteAverage, .discreteMin, .discreteMaxUse HKStatisticsCollectionQueryDescriptor for time-series data grouped into intervals -- ideal for charts.
func fetchDailySteps(forLast days: Int) async throws -> [(date: Date, steps: Double)] {
let calendar = Calendar.current
let endDate = calendar.startOfDay(
for: calendar.date(byAdding: .day, value: 1, to: Date())!
)
let startDate = calendar.date(byAdding: .day, value: -days, to: endDate)!
βMake data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
βSave 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- βΊClaude Desktop or compatible AI client
- βΊAccess to product documentation and roadmap tools (Jira, Notion, etc.)
- βΊUnderstanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- βΊStakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- β Not validating competitive researchβverify facts before sharing
- β Accepting user stories without involving engineering team
- β Over-relying on frameworks without qualitative judgment
- β Not customizing outputs to company culture and communication style
- β Skipping stakeholder validation of generated requirements
Best Practices
β Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
β Don't
- βDon't publish competitive analysis without fact-checking
- βDon't finalize user stories without engineering review
- βDon't make prioritization decisions solely on AI scoring
- βDon't skip customer validation of generated requirements
- βDon't ignore company-specific context and culture
π‘ Pro Tips
- β
Provide context: company goals, constraints, customer feedback
- β
Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- β
Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- β
Use skill for 70% generation + 30% customization to company needs
When to Use This
β Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
β Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
452mattpocock/skills
Productivitysame categorypremortem
202parcadei/continuous-claude-v3
Productivitysame categorydeslop
129cursor/plugins
Productivitysame categoryframer-motion
109pproenca/dot-skills
Productivitysame categorytravel-planner
101ailabs-393/ai-labs-claude-skills
Productivitysame categorywrite-a-prd
100mattpocock/skills
Productivitysame categoryReviews
4.4β
β
β
β
β
54 reviews- MMia Wangβ
β
β
β
β
Dec 28, 2024
healthkit has been reliable in day-to-day use. Documentation quality is above average for community skills.
- MMia Liβ
β
β
β
β
Dec 28, 2024
Keeps context tight: healthkit is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAnika Okaforβ
β
β
β
β
Dec 24, 2024
healthkit fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
- LLuis Harrisβ
β
β
β
β
Dec 16, 2024
healthkit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- BBenjamin Shahβ
β
β
β
β
Dec 8, 2024
Solid pick for teams standardizing on skills: healthkit is focused, and the summary matches what you get after install.
- EEvelyn Thompsonβ
β
β
β
β
Nov 27, 2024
We added healthkit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- XXiao Menonβ
β
β
β
β
Nov 23, 2024
Keeps context tight: healthkit is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNia Martinβ
β
β
β
β
Nov 19, 2024
healthkit fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
- RRahul Santraβ
β
β
β
β
Nov 15, 2024
healthkit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNia Bhatiaβ
β
β
β
β
Nov 15, 2024
healthkit has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 54
1 / 6Discussion
Comments β not star reviews- No comments yet β start the thread.