Automate daily briefings into personal Spotify podcasts with OpenClaw and the Save to Spotify CLI
A developer on the OpenClaw team built a personal briefing pipeline that produces a private Spotify podcast episode every morning. The setup uses OpenClaw's skill system and the newly released Save to Spotify CLI, which is open-source and available on ClawHub.
How it works
- OpenClaw runs daily at 7am.
- It pulls overnight Slack threads, GitHub notifications, and calendar events.
- Summarizes everything into a structured briefing (top 5 items, ordered by urgency).
- Generates a transcript and renders it as mp3 audio.
- Calls the Save to Spotify CLI to upload the mp3 as a private episode.
By the time the developer is on their commute, the episode is in their Spotify library. They listen at 1.5x speed and are caught up before their first meeting.
Installation and setup
The skill is published on ClawHub under @spotify/save-to-spotify. One install — no manual manifest wiring. Under the hood, the project exposes a skill manifest under agents/skills/, and your OpenClaw agent picks it up automatically.
The project is open source: github.com/spotify/save-to-spotify
Tips from production use
- Give OpenClaw a strict format — the developer uses "top 5 things, in order of urgency".
- Write summaries aimed at audio: short sentences, no bulleted asides.
- Timeline mode is useful for referencing external links, screenshots, diagrams.
This pipeline replaced the developer's morning Slack-scrolling ritual entirely.
📖 Read the full source: r/openclaw
👀 See Also
Atlarix v5.1 adds cloud tiers while maintaining local AI coding support
Atlarix v5.1.0 introduces Compass cloud tiers for immediate use while maintaining full Ollama and LM Studio support. The IDE uses a persistent SQLite graph called Blueprint to provide precise context to local models.
Building a Geological Clock with Claude Code: Single HTML + Three.js
A product designer built eona.earth, a geological clock that maps Earth's 4.5 billion years onto 12 hours, using Claude Code, Three.js, and custom WebGL shaders — all as a single HTML file with no build step.
Repowise: Pre-computed codebase context for Claude Code cuts token usage and task time in half
Repowise indexes your codebase into four layers (dependency graph, git signals, doc wiki, ADRs) and exposes eight MCP tools to Claude Code, reducing a 30-file archaeology session to 5 MCP calls and 2 minutes.
Auto-optimize: A Claude Code Plugin for Autonomous Performance Optimization
A developer built auto-optimize, a Claude Code plugin that autonomously runs profile → plan → benchmark loops to optimize code performance. In one test, it achieved a 27% faster hash table across all benchmark scenarios in about 3 hours.