agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/managing-content-calendar/SKILL.md

managing-content-calendar

Skill0 starsChanged 9 days agoMITView on GitHub

Reviews and reorganizes the social media content calendar in Postify: lists scheduled, draft, published, and failed posts, finds gaps in the posting schedule, and reschedules a post after confirmation. Use when the user asks 'what's scheduled next week', 'show my upcoming posts', 'move Friday's post to Monday 9am', 'reschedule this post', 'where are the gaps in my posting schedule', 'which posts failed', or wants a social media planner or posting calendar overview. Never publishes or deletes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every tool in this skill comes from the postify MCP server, the Postify connector, and is written here as postify:<tool>.

    line 13
  2. Very specific:

    Tools listed by name: call them directly, for example postify:list_posts.

    line 15
  3. Very specific:

    Call postify:list_channels once so you know which platforms exist.

    line 30
  4. Very specific:

    Call postify:get_schedule for the window the user cares about (default: today through the next 7 days).

    line 31
  5. Very specific:

    Never call postify:publish_now or postify:delete_post from this skill.

    line 38
  6. Very specific:

    If postify:list_posts returns nothing, say so plainly and offer the drafting-social-posts skill.

    line 40

≈ “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
<!-- Generated from plugins/postify/skills/managing-content-calendar/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Postify content calendar

Work the user's Postify calendar through the postify MCP server. All tools operate on the organization behind the connected account.

Connecting and calling the tools

Every tool in this skill comes from the postify MCP server, the Postify connector, and is written here as postify:<tool>.

  • Tools listed by name: call them directly, for example postify:list_posts.
  • Only postify:search_tools and postify:execute_typescript listed (Code Mode, the default): call postify:search_tools first, then call each tool inside postify:execute_typescript as external_<tool> (for example external_list_posts); the program must return its result. Scopes, confirmations and gates are identical on both surfaces.
  • "Tool not found": switch to the Code Mode route instead of retrying the direct call. If postify:search_tools does not return the tool either, its OAuth scope was not granted; the user reconnects Postify and approves that scope.
  • No postify tools at all: Postify is not connected yet. Follow the setup-postify skill.

Tools you will use

  • postify:list_posts: posts with id, status (draft, scheduled, published, failed), scheduled datetime, and target channels. Filter by status or date range when the tool offers it.
  • postify:get_schedule: scheduled posts in a date window (from, to, limit up to 50).
  • postify:get_post: the full content of one post when the list summary is not enough.
  • postify:list_channels: connected social accounts (platform, handle, connection status). Use it to name channels correctly instead of guessing.
  • postify:reschedule_post: move a scheduled post to a new datetime. Content is unchanged.

Workflow

  1. Call postify:list_channels once so you know which platforms exist.
  2. Call postify:get_schedule for the window the user cares about (default: today through the next 7 days). Use postify:list_posts when the user also wants drafts, published, or failed posts.
  3. Present the calendar grouped by day, then by channel. Show status and local time. Mark failed posts first.
  4. For gaps, compare against the user's stated cadence (ask once if unknown) and list the empty days per channel.
  5. To move a post, confirm the post id and the new time with the user, then call postify:reschedule_post. Echo the new datetime back.

Rules

  • Never call postify:publish_now or postify:delete_post from this skill. Moving and reviewing only.
  • Times: the server returns ISO 8601 datetimes. Convert to the user's timezone when you present them and say which timezone you used.
  • If postify:list_posts returns nothing, say so plainly and offer the drafting-social-posts skill.

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.