daily_skill

This skill helps you manage Daily data interactions including meetings, rooms, recordings, and participants by leveraging Membrane CLI automation.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill daily

  • _meta.json263 B
  • SKILL.md5.7 KB

Overview

This skill integrates with Daily to manage meetings, participants, recordings, transcriptions, rooms, and related entities using Membrane as the connector. It streamlines common Daily operations so you can create tokens, list rooms, fetch recordings, and control participants without handling OAuth or credential refresh yourself. Use it when you need programmatic access to Daily data and real-time call resources.

How this skill works

The skill uses the Membrane CLI and its connector for Daily to discover and run pre-built actions or proxy raw Daily API requests. Membrane handles authentication, token refresh, pagination, and common error cases; you create a connection once and then list or run actions by connectionId. When actions are insufficient you can proxy arbitrary HTTP requests through Membrane with automatic auth injection.

When to use it

  • Create or update Daily rooms and room configuration programmatically.
  • Generate or validate meeting tokens for users to join calls.
  • List meetings, recordings, participants, and room presence for analytics or reporting.
  • Eject participants or control live meeting behavior during sessions.
  • Download, list, or delete recordings and access temporary download links.
  • Proxy custom Daily API calls not covered by the pre-built actions.

Best practices

  • Install and authenticate the Membrane CLI once; prefer actions over raw requests to save work and avoid token handling.
  • Run membrane action list with an intent to discover existing actions before writing custom requests.
  • Never store or ask for Daily API keys locally; create and use a Membrane connection so credentials stay managed server-side.
  • Pass structured JSON input when running actions to avoid parsing errors and to match action input schemas.
  • Use Membrane proxy for edge cases, but prefer pre-built actions for pagination and consistent error handling.

Example use cases

  • Create a meeting token for a user session and return it to a web client for immediate join.
  • List recent meetings with participant counts and attach analytics to CRM records.
  • Fetch a recording access link to provide a temporary download to a user or service.
  • Eject a disruptive participant from an active room as part of moderation tooling.
  • Automate room lifecycle: create rooms for events and delete them after the event ends.

FAQ

No. Membrane manages authentication and credential refresh; you create a connection via the CLI and do not handle raw API keys.

Can I call Daily endpoints not covered by pre-built actions?

Yes. Use membrane request with the connectionId to proxy arbitrary HTTP calls to the Daily API; Membrane injects auth headers automatically.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
daily skill by openclaw/skills | VeilStrat