Menu
Biotrackr health data schema, metric extraction patterns, and analysis techniques for Fitbit activity data
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Blazor component architecture, Razor component patterns, Radzen UI library, and Blazor-specific UX patterns. Use when: building Blazor components, structuring Razor component hierarchy, using Radzen components, implementing Blazor forms, managing component state, Blazor rendering modes, Blazor layout design.
Ensure .NET/C# code meets best practices for the solution/project.
Quality gate review with structured findings and verdict. Use when: reviewing a completed implementation phase, checking spec compliance, convention adherence, test coverage, and issuing APPROVE or REQUEST_CHANGES verdicts.
Generate phased implementation blueprint with parallel research subagents. Use when: a clarified specification is ready for architecture planning, creating task tables, scoring complexity, and defining implementation phases.
Execute one implementation phase with progress tracking and verification. Use when: implementing tasks from an SDD plan, logging discoveries, updating task tables, and running build/test verification per phase.
Encode learnings from completed SDD cycles into the agent harness. Use when: a review has been approved and learnings need to be extracted, classified, and encoded into instruction files, copilot-instructions, or AGENTS.md.
| name | health-data-analysis |
| description | Biotrackr health data schema, metric extraction patterns, and analysis techniques for Fitbit activity data |
Biotrackr health data arrives as a JSON object with an items array. Each item represents one day:
{
"items": [
{
"date": "2026-04-05",
"activity": {
"activities": [
{
"name": "Strength training",
"calories": 665,
"duration": 5271000,
"steps": 4972,
"startTime": "06:57",
"distance": 2.52
}
],
"summary": {
"steps": 15732,
"caloriesOut": 4049,
"activityCalories": 2341,
"fairlyActiveMinutes": 47,
"veryActiveMinutes": 78,
"lightlyActiveMinutes": 234,
"sedentaryMinutes": 567,
"distances": [{"activity": "total", "distance": 12.02}],
"floors": 238,
"restingHeartRate": 51
}
}
}
],
"totalCount": 7,
"note": "Optional note about missing data"
}
item["activity"]["summary"]["steps"]item["activity"]["summary"]["caloriesOut"]item["activity"]["summary"]["activityCalories"]fairlyActiveMinutes + veryActiveMinutes (combine both fields)distances array where activity == "total": next(d["distance"] for d in distances if d["activity"] == "total")item["activity"]["summary"]["floors"]item["activity"]["summary"]["restingHeartRate"]Activity durations in the data are in milliseconds. Convert to minutes by dividing by 60000:
duration_minutes = round(activity["duration"] / 60000)
Standard daily goals for achievement tracking:
| Goal | Target | Field |
|---|---|---|
| Steps | ≥ 10,000 | steps |
| Distance | ≥ 8.0 km | total distance |
| Active Minutes | ≥ 30 min | fairlyActiveMinutes + veryActiveMinutes |
| Calories | ≥ 2,500 kcal | caloriesOut |
Goal achievement per day = count of how many of the 4 goals were met.
Identify these standout categories across the reporting period:
max(days, key=lambda d: d["steps"])max(days, key=lambda d: d["caloriesOut"])max(days, key=lambda d: d["activeMinutes"])max(days, key=lambda d: d["goals_met"])duration across all daysCalculate these summary statistics:
note field indicates gaps).len(items)), not 7.