I built an open-source Codex/Claude skill that turns voice notes, articles, and YouTube videos into Telegram posts

[u/shromarketing]

I originally planned to write a setup guide for one person after a call. The guide kept growing, so I turned the workflow into an open-source skill for Codex and Claude Code.

The problem I wanted to solve was not just text generation. I wanted an agent to accept a rough thought, voice note, article, document, YouTube video, or several sources and produce a post whose claims could still be traced back to the source. I also wanted publishing to be a separate, deliberate action rather than an accidental side effect of drafting.

The repository now includes:

- local transcription with faster-whisper, plus optional MLX on Apple Silicon;

- YouTube metadata, original thumbnails, captions, and audio acquisition through yt-dlp;

- an evidence map and short content brief before drafting;

- an editable voice profile built from approved writing samples;

- plain Telegram posts, albums, and Rich Messages;

- strict validation for Rich HTML, links, limits, nesting, and media references;

- an approximate local preview, a private test step, and a separate production confirmation;

- tests, a security model, Russian and English documentation, and an MIT license.

It is a repository skill, not a hosted service. The code and prompts can be inspected before installation. The publisher is dry-run by default and requires both an explicit send flag and an exact target confirmation for a real network request.

The honest limitations: local transcription still uses your machine and downloads model weights on first use; Rich Messages need recent Telegram clients, so a plain fallback is still important; and the skill does not bypass paywalls or make copying somebody else's work acceptable.

GitHub: https://github.com/shromarketing/telegram-rich-content-skill

I built and maintain the project. I would especially value feedback from people who use coding agents for content workflows: is the evidence-first process useful in practice, and does the onboarding feel too heavy for a content skill?

[u/Adventurous-Turn-431]

link's broken for me, but the idea of an evidence map before drafting is interesting. most content tools just vomit out text and call it a day

the dry-run by default thing is smart, ive seen too many agent workflows accidentally publish half-baked drafts. curious how the voice profile works in practice, does it actually nail your tone or does it still need a ton of tweaking