A recurring series rarely breaks on the first issue. It breaks on the fifth. The topic is picked, the format works, two issues are out — and every issue after that starts from scratch: remember what you already covered, rebuild the source list, force it all back into the same shape.
A channel takes that part off you. It is a standing brief: topic, audience and angle described once, after which issues come out on their own — daily, weekly, monthly or on your word. This skill sets up that channel, runs an issue and brings you the draft — you publish it yourself, from the channel page.
What this skill does: creates a channel and runs its issues
From your description the skill assembles a standing brief — not a one-off task but an instruction to an editor for every future issue: what to write about, for whom, and what counts as new. It then creates the channel, sets the schedule and immediately runs the first issue, so the channel is something you can read rather than an abstraction.
Once a channel exists, the skill keeps working with it: it lists your channels and their schedules, edits the brief or the cadence, pauses and resumes, runs an extra issue off-schedule, and shows a draft in full for review.
How it works
- The skill pulls topic, audience and angle out of your request and turns them into a standing brief. Whatever you did not specify takes the defaults: private channel, draft issues, run on request.
- It creates the channel and starts the first issue right away. Preparing one takes a few minutes — the channel researches the topic and writes the issue.
- It shows you the draft when you ask: the title, what the issue covers, and the full text if you want to read it end to end.
- The rest is yours: the draft waits on the channel page, where the Publish button lives.
The skill sets up a public channel only when you explicitly ask for one, and agrees the name for its address first. Scheduled issues are prepared overnight, around 00:30 Moscow time, so the issue is ready by morning.
What you get
A private channel lives in your account under Channels: its page, its issue history and its controls. A public channel additionally gets its own address on sey.kz — an issue page, an index of all the channel's issues, and RSS and JSON feeds you can subscribe to in a reader. The pages are closed to search robots, so publishing is a way to hand out a link, not a way into search results.
A draft always comes before publication until you switch the channel to automatic mode yourself. Which means a channel cannot publish something you have not seen — by default it prepares the issue and waits. The skill deliberately cannot publish: consent to publish is you pressing the button next to a draft you have read — or, once, switching the channel to automatic mode.
When to use it
It fits anything that should come out regularly and in one shape: a news roundup for your niche, a weekly competitor review, a project diary, a series for a newsletter or a Telegram channel, a reporting column for a client. It pays off most when a topic has to run for months: the channel remembers what earlier issues covered and does not retell the same thing in new words.
A one-off question does not need a channel — ordinary chat handles that. A channel starts paying for itself around the second or third issue, when the standing brief means you no longer explain the task from scratch each time.
Publishing, deleting a channel and pulling a published issue are deliberately not part of the skill: readers see the result of all three, so those buttons stay on the channel page, where a person makes the call.