Compose a personalized morning briefing whose tone and depth adapt to last night's sleep quality.
Coding
Arc Fulcra Sleep Detective
Try itRetired Fulcra sleep-analysis skill. Route new work to fulcra-context and keep all sleep, biometric, calendar, and location reads explicit, bounded, and user...
What it does
Retired Fulcra sleep-analysis skill. Route new work to fulcra-context and keep all sleep, biometric, calendar, and location reads explicit, bounded, and user-approved.
The skill document
Fulcra Sleep Detective
This skill is retired. Its earlier experimental scripts were merged into the broader Fulcra skill family and are no longer shipped here.
Use fulcra-context for current sleep, biometric, activity, calendar, location, and metric-catalog reads. Use fulcra-annotations only when the user explicitly asks to record an event or create an annotation.
Current Routing
- Sleep analysis, recovery context, readiness, and trends: use
fulcra-context. - Writes, check-ins, ratings, notes, and annotation buttons: use
fulcra-annotations. - Cross-agent coordination, handoffs, and team state: use
fulcra-agent-teams. - Persistent agent memory workflows: use
fulcra-memory. - Lightweight event tracking: use
fulcra-tracking.
Privacy Boundary
Sleep and biometric data are sensitive personal context. Calendar and location data can identify people, places, routines, and private obligations. Before using any Fulcra data:
- Ask for consent unless the user has already granted it for the current request.
- Read only the smallest metric set and time window needed.
- Prefer summaries, trends, and aggregates over raw records.
- Do not retain, export, screenshot, publish, or forward Fulcra records without explicit approval for that exact destination.
- Do not run background monitoring, scheduled polling, proactive alerts, or persistent files from this retired skill.
- Use synthetic data for public examples, demos, tests, and documentation unless the user explicitly approves real data for that artifact.
Safe Setup
For new work, install or use fulcra-context and follow its current onboarding flow.
CLI-first environments:
uv tool run fulcra-api --help
uv tool run fulcra-api auth login --get-auth-url
uv tool run fulcra-api user-info
Restricted environments:
https://mcp.fulcradynamics.com/mcp
Never print, paste, log, or share access tokens, refresh tokens, credential files, raw private records, or direct capability URLs.
First Useful Flow
When a user asks about sleep, do this with fulcra-context:
- Confirm the request and time window.
- Check whether Fulcra data is fresh enough for the question.
- Read only the needed sleep and recovery metrics.
- Add calendar, location, medication, supplement, nutrition, or activity context only if the user asked for that correlation or explicitly approves it.
- Answer with concise interpretation and uncertainty. Say when data is missing or stale.
Deprecated Commands
The old commands sleep-theory, sleep-alert, sleep-context, and sleep-insights are retired. Do not invoke or recreate them from this package. Use bounded fulcra-context reads instead.
Links
- Fulcra Platform:
- Developer Docs:
- Current Context Skill:
- Annotation Skill:
Related skills
Deliver a personalized morning briefing that combines objective data (last night's sleep, today's calendar, weather) with how the user actually said they fee...
Track sleep vs optimal, calculate accumulated sleep debt, and suggest evidence-based recovery schedules. Chronotype detection, quality-weighted sleep tracking, ASCII charts, and caffeine/alcohol impact monitoring.
Read user-consented Fulcra context data — biometrics, sleep, activity, calendar, location — via the CLI or hosted MCP server.
Run a short, warm, conversational morning check-in that captures how the user is *actually* feeling -- mood, energy, social battery, physical state, and inte...
Analyze how the user's meeting load correlates with how their days actually feel -- using their own evening-debrief and morning check-in history -- and recom...