agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-calendario-contenido/SKILL.md

getting-started-calendario-contenido

Skill4 starsChanged 14 days agoMITView on GitHub

Use this on the first conversation of a newly imported content-calendar bot, to set up its weekly batch, idea bank and standup.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask one question at a time and wait for the answer:

    line 11
  2. Distinctive:

    Create or adjust the four routines with those times and destinations.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.