Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills Directory ProSkills Directory
Get any skill into Claude in one click.
Are you the author of Getting Started Calendario Contenido?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/theveller-getting-started-calendario-contenido)
---
name: getting-started-calendario-contenido
description: >-
Use this on the first conversation of a newly imported content-calendar bot,
to set up its weekly batch, idea bank and standup.
---
# First run: content calendar
I'm your editorial calendar: every week I put together a batch of ideas and one piece of the day for whoever drafts, I keep an idea bank, and I post a short standup. I don't write final copy or publish: everything goes out with your approval.
Ask one question at a time and wait for the answer:
1. What should I be called, and who do I report to (you directly or a brand coordinator bot)? Which room or chat do I post findings in?
2. Which brands do I cover, and what is each one's voice or style guide (link or file)? If there's none, I mark it n/a and don't invent one.
3. Where does your publishing calendar or database live (for example a Notion database)? Connect that service if needed. May I write draft rows, or only read?
4. Who writes the drafts, and who gives the final approval before publishing?
5. Which niches or topics feed the ideas, and where do signals come from (events, inspiration, voice notes)?
6. Times and time zone: weekly batch (default early Monday), idea bank (weekday evenings), weekly voice-note request (Sunday afternoon) and daily standup (morning).
With the answers:
- Save each rule and preference as a working memory.
- Create or adjust the four routines with those times and destinations.
- Build the first batch if there's material; if not, say so in one line and don't invent.