mcpbeat Sign in

Session Lifecycle Agent Skill

Session state, stream state, pause and resume behavior, and device availability monitoring

752 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
339
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/facebook/meta-wearables-dat-android --skill session-lifecycle

The instruction itself

9 sections, as written by the author

Session Lifecycle (Android)

Manage session and stream state in DAT SDK integrations.

Create a Session with Wearables.createSession(...), start it, then attach capabilities such as camera streaming. Session lifecycle and stream lifecycle are related but distinct.

Session states

| State | Meaning | App action |

|-------|---------|------------|

| IDLE | Session created, not started yet | Call session.start() |

| STARTING | Connecting to the device | Show loading UI |

| STARTED | Session active and ready for capabilities | Add or use capabilities |

| PAUSED | Session temporarily suspended | Keep state, wait for resume or stop |

| STOPPING | Session is shutting down | Stop user work and wait |

| STOPPED | Session ended | Release resources and create a new session if needed |

Observe session state

val session = Wearables.createSession(AutoDeviceSelector()).getOrElse { error ->
    throw IllegalStateException(error.description)
}
session.start()

lifecycleScope.launch {
    session.state.collect { state ->
        when (state) {
            DeviceSessionState.STARTED -> onStarted()
            DeviceSessionState.PAUSED -> onPaused()
            DeviceSessionState.STOPPED -> onStopped()
            else -> Unit
        }
    }
}

Stream state

Camera streaming has its own state flow after you attach a stream:

STOPPED -> STARTING -> STARTED -> STREAMING -> STOPPING -> STOPPED -> CLOSED
lifecycleScope.launch {
    camera.stream.state.collect { state ->
        // React to camera capability state changes
    }
}

Common transitions

The SDK may pause or stop a session when:

  • Another experience takes over the device
  • The user removes or folds the glasses
  • Bluetooth connectivity drops
  • The user unregisters the app or revokes needed access

Pause and resume

When a session is paused:

  • The device connection may remain active
  • Attached capabilities stop doing useful work
  • Your app should wait for the next observed session state instead of trying to force a restart

Device availability

lifecycleScope.launch {
    Wearables.devices.collect { devices ->
        // Update the list of available devices
    }
}

Use Wearables.devices and device metadata to decide when it is sensible to create a new session after a stop.

Checklist

  • [ ] Handle all DeviceSessionState values you care about
  • [ ] Observe stream state separately from session state
  • [ ] Release resources only after stop or close
  • [ ] Recreate sessions after terminal stops instead of reusing dead ones
  • [ ] Surface typed SessionError and StreamError failures

Other skills for the same job

different authors, same section of the catalogue
MCP Deploy Manage Agents
by github
vendor ×1

Skill converted from mcp-deploy-manage-agents.prompt.md

2k tokens
Cloud Claw Launch Agent
by internet-court
×1

Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.

1k tokens
Hosted Agents V2 Py
by lingxling
×1

Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.

2k tokens
Cloudflare MCP Server
by ComeOnOliver
×1

Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.

49k tokens scripts
When Chaining Agent Pipelines Use Stream Chain
by ComeOnOliver
×1

Chain agent outputs as inputs in sequential or parallel pipelines for data flow orchestration

5k tokens
Clone Audit Mrlv3nl4
by nexu-io

Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.

2k tokens
Hermes Tweet
by wshobson

> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated tweet actions. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing guarded tweet actions. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.

2k tokens
Arize Evaluator
by github
vendor

Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.

10k tokens

How to use it

Copy the folder

Take facebook/meta-wearables-dat-android-session-lifecycle from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.