Neura Market Logo

Arc Fulcra Sleep Detective

Retired Fulcra sleep-analysis skill. Route new work to fulcra-context and keep all sleep, biometric, calendar, and location reads explicit, bounded, and user...

Arc from Fulcra.ai

@arc-claw-bot

What This Skill Does

Retired Fulcra sleep-analysis skill that has been merged into the broader Fulcra skill family. Directs all new sleep, biometric, calendar, and location reads to the `fulcra-context` skill and all writes to `fulcra-annotations`, with strict privacy boundaries and consent requirements.

Replaces the need to maintain separate experimental sleep-analysis scripts by routing all sleep, biometric, and context reads to a single maintained skill with explicit user consent and bounded data access.

When to Use It

  • Route a user's sleep analysis request to `fulcra-context` instead of using this retired skill
  • Check whether Fulcra sleep data is fresh enough for a user's question before reading metrics
  • Read only the smallest set of sleep and recovery metrics needed for a user's request
  • Add calendar, location, or activity context only when the user explicitly asks for correlation
  • Interpret sleep data with concise uncertainty and note when data is missing or stale
  • Direct a user to `fulcra-annotations` when they want to record a sleep event or annotation

Install

$ openclaw skills install @arc-claw-bot/fulcra-sleep-detective

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:

  1. Ask for consent unless the user has already granted it for the current request.
  2. Read only the smallest metric set and time window needed.
  3. Prefer summaries, trends, and aggregates over raw records.
  4. Do not retain, export, screenshot, publish, or forward Fulcra records without explicit approval for that exact destination.
  5. Do not run background monitoring, scheduled polling, proactive alerts, or persistent files from this retired skill.
  6. 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:

  1. Confirm the request and time window.
  2. Check whether Fulcra data is fresh enough for the question.
  3. Read only the needed sleep and recovery metrics.
  4. Add calendar, location, medication, supplement, nutrition, or activity context only if the user asked for that correlation or explicitly approves it.
  5. 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

Top skills in this category

Google Docs

@hith3sh

Google Docs API integration with managed OAuth. Search, read, create, and update Google Docs documents. Use this skill when users want to read document text,...

327.1k

Monday.com

@byungkyu

Monday.com API integration with managed OAuth. Manage boards, items, columns, groups, and workspaces using GraphQL. Use this skill when users want to create, update, or query Monday.com boards and items, manage tasks, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login; default to read and list calls, and confirm every write or new connection with the user.

716k

Ollama Local

@timverhoogt

Manage and use local Ollama models. Use for model management (list/pull/remove), chat/completions, embeddings, and tool-use with local LLMs. Covers OpenClaw sub-agent integration and model selection guidance.

117.2k

google-docs

@byungkyu

Google Docs API integration with managed OAuth. Create documents, insert text, apply formatting, and manage content. Use this skill when users want to interact with Google Docs. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login; default to read and list calls, and confirm every write or new connection with the user.

89.0k

Cinematic Script Writer

@praveenspeaks

Create professional cinematic scripts for AI video generation with character consistency and cinematography knowledge. Use when the user wants to write a cinematic script, create story contexts with characters, generate image prompts for AI video tools (Midjourney, Sora, Veo), or needs cinematography guidance (camera angles, lighting, color grading). Also use for character consistency sheets, voice profiles, anachronism detection, and saving scripts to Google Drive.

97.6k