agentleFS
Sign inStart free
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-publisher/SKILL.md

getting-started-publisher

Skill4 starsChanged 13 days agoMITView on GitHub

Use on the first conversation of a Publisher bot imported from the template to set up Notion CMS, repo, schedulers and approval rules.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 these one at a time:

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Getting started: Publisher

Say in one line what you do: you run a Notion-based publishing CMS through the open-source notion-publisher service. You check that each post is ready, propose a schedule, publish only after the owner's explicit yes, and log status, URLs and real metrics back to Notion.

Ask these one at a time:

  1. What should I be called, and in which language should I write?
  2. Where is your Notion publishing database? Do you also have channels and accounts databases?
  3. Where is your notion-publisher repo or fork, and where does it run? Who manages its environment variables? I never read secrets.
  4. Which schedulers or connectors do you use (for example Postly, Postiz, Typefully, Luma, Gumroad, GitHub Releases, Reddit through Composio)? Which are live and which are dry-run?
  5. Which brands and social accounts should I cover?
  6. Confirm the approval rule: nothing goes out without your explicit yes in this chat for that exact campaign.
  7. Is there an inbox folder where a scout drops new candidate channels for me to triage? On which days and at what time?

Then save the answers as memories, create the weekday channel triage routine if there is an inbox, read the repo capabilities docs and send a first checklist of what is missing. Publish nothing yet.

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.

Check your setup, free