agentleFS
Sign inStart free
posteverywhereposteverywhere/copilot-plugin/skills/approval-workflow/SKILL.md

approval-workflow

Skill0 starsChanged 28 days agoMITView on GitHub

Draft social media posts for someone else to review before they go live in PostEverywhere. Use when the user works in a team or agency, needs a client, manager or colleague to approve posts, says "send these for review", "what's waiting for approval", "make the changes they asked for", or "they approved it, schedule it".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 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.

  • 6

    Very specific

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

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

    Find the accounts: Call list_accounts and confirm which accounts the posts are for.

    line 12
  2. Very specific:

    Save them as drafts: Call create_post with draft: true, or bulk_create_posts with draft: true on each.

    line 14
  3. Very specific:

    Call list_posts with status: "draft" (or list_posts_advanced with status: "draft" and search for a word in the post).

    line 19
  4. Very specific:

    Call update_post with the post_id and the new content, platform_content, media_ids, account_ids or scheduled_for.

    line 25
  5. Distinctive:

    When the user says a post is approved, repeat the post id, accounts and time, so both of you are sure it is the right one.

    line 30
  6. Very specific:

    Call schedule_post with the post_id and scheduled_for (with timezone), or publish_now: true if they want it out now.

    line 31
  7. Very specific:

    Ask the user whether to rewrite it (update_post) or remove it.

    line 36
  8. Distinctive:

    Only schedule the posts the user said are approved.

    line 40

≈ “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

Approval workflow

Posts wait as drafts until the right person says yes. Approval is the user telling you, in this conversation, that a post is approved. Never treat silence, or your own judgement, as approval.

Create posts for review

  1. Find the accounts. Call list_accounts and confirm which accounts the posts are for.
  2. Write the posts (see schedule-social-posts for the platform rules).
  3. Save them as drafts. Call create_post with draft: true, or bulk_create_posts with draft: true on each. You may set scheduled_for on a draft: it only suggests a time and publishes nothing.
  4. Share them for review. Drafts appear in the PostEverywhere app, where a reviewer with access to the workspace can read them. Also give the user a short list to send: post id, accounts, suggested time and the full text.

See what is waiting

  1. Call list_posts with status: "draft" (or list_posts_advanced with status: "draft" and search for a word in the post).
  2. Show each draft: id, accounts, suggested time and the first line. Use get_post for the full text and media.

Apply requested changes

  1. The user tells you what the reviewer asked for. Change only that.
  2. Call update_post with the post_id and the new content, platform_content, media_ids, account_ids or scheduled_for.
  3. Show the changed post again and ask if it now has approval.

Schedule after approval

  1. When the user says a post is approved, repeat the post id, accounts and time, so both of you are sure it is the right one.
  2. Call schedule_post with the post_id and scheduled_for (with timezone), or publish_now: true if they want it out now.
  3. Report the post id, accounts and time. For "publish now", call get_post_results after a short wait.

If a post is rejected

Ask the user whether to rewrite it (update_post) or remove it. Delete a draft with delete_post only when the user asks.

Be careful

  • Only schedule the posts the user said are approved. If they approve "the first three", confirm which three by id.
  • schedule_post only works on drafts. To change a post that is already scheduled, use update_post.

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