← freddyCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to freddy
Snapshot Sep 30, 2026 · 22:46 UTC · version 2.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "connect-a-source",
"description": "Use when the user wants to connect a wearable, ring, CGM, training platform, or gym log to freddy, or asks why a newly connected source shows no data yet. Not for disconnecting or for querying data.",
"included_files": [],
"skill_md_contents": "---\nname: connect-a-source\ndescription: Use when the user wants to connect a wearable, ring, CGM, training platform, or gym log to freddy, or asks why a newly connected source shows no data yet. Not for disconnecting or for querying data.\n---\n\n# Connect a source\n\nThis skill uses the freddy app's MCP tools (get_profile, list_metrics, query_metrics, connect_source, sync_source). Follow the workflow below.\n\nHelp me connect a new data source to freddy.\n\n1. Call get_profile to see what is already connected.\n2. If I haven't named a source, ask which one I want to connect.\n3. Call connect_source with that provider. OAuth sources return a URL for me to open in a browser; API-key sources and phone sources (Apple Health, Health Connect) return instructions to finish on the freddy dashboard or phone app — relay those instructions to me clearly and never ask me to paste credentials into this chat.\n4. Once I confirm I have authorized, data starts syncing automatically and the first backfill can take a few minutes. If nothing is showing after a couple of minutes, call sync_source to force a pull. If query_metrics says data is still hydrating, tell me it is on the way rather than concluding there is no data.\n"
}SHA-256: 8056b2b1ed6cd4002946c56b1ecc7d883751ace5c25ba21eb72ac9b750424a2f