Telegram

Comprehensive AI writing cleanup based on Wikipedia's WikiProject AI Cleanup guidelines. Catches 24+ distinct patterns including inflated symbolism, em dash overuse, rule of three, copula avoidance, and sycophantic tone.

Set up a lightweight weekly digest around your stack and interests. A nice starter automation because it shows OpenClaw doing recurring research without requiring a huge workflow or lots of context.

A personal, local-first AI assistant that automates small daily tasks—organizing files, setting reminders, and monitoring system events—without touching sensitive data or taking risky actions without your approval.

Run any recurring class program without the admin headache. Track what you covered each session, keep notes on individual students, manage upcoming events, and get an automatic briefing before class — all through a dedicated Telegram sub-agent. Works for martial arts, music lessons, dance, tutoring, fitness, and more.

A workflow to create a brand for your product or client using Gemini and OpenAI to generate images, with KiloClaw managing the prompts, analyzing results, and iterating until every brand element comes together.

Monitors your key tables for freshness, row counts, and schema changes on a schedule. Alerts you via Slack or Telegram before business hours when something looks off — so you're never blindsided by a stakeholder asking "why is the dashboard blank?"

When a pipeline fails, paste the error log and get a plain-English diagnosis with the likely root cause, affected downstream systems, and a suggested fix. Helps you get from stack trace to next step fast.

Monitors your source databases, APIs, and third-party integrations for schema changes — new columns, removed columns, type changes, enum value additions — and alerts you before the downstream breakage happens.

Audio slowly drifts out of sync or randomly desyncs in your timeline when footage is variable frame rate — common with iPhone footage, screen recordings, and some OBS workflows. This recipe catches VFR clips at ingest, transcodes them to constant frame rate, and quarantines the originals so drift never reaches your edit.

Choppy playback, laggy scrubbing, and unusable timelines — even on strong machines — often comes down to editing long-GOP or heavy codecs at high resolution without proxies. This recipe generates proxies automatically whenever new camera originals appear, so every project starts edit-ready instead of debug-ready.

Media cache and disk caches balloon over time, causing storage emergencies and performance regressions. This recipe turns cache cleanup from a panic action into a controlled, scheduled maintenance job — for Adobe Premiere Pro, After Effects, and similar tools.

Resolve's render cache and CacheClip folders can grow extremely large and fill disks mid-project with no warning. This recipe monitors cache growth, alerts at thresholds, and provides Resolve-safe cleanup steps so you never lose work to a full disk.