agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/reviewing-social-performance/SKILL.md

reviewing-social-performance

Skill0 starsChanged 9 days agoMITView on GitHub

Reports how social posts performed in Postify: posts delivered, delivery rate, failures, per-channel stats, and the best times to post on each platform. Use when the user asks 'how did last month go', 'which channel performs best', 'show my social media analytics', 'how many posts went out', 'why did posts fail', 'when should I post on Instagram', or wants a social media performance report. Read-only.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the workspace's delivery analytics and turn them into a short, honest report.

    line 9
  2. 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
  3. Very specific:

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

    line 15
  4. Very specific:

    If there were failures, call postify:list_posts filtered to failed for the window and list them with their channel and datetime so the user …

    line 30
  5. Very specific:

    Call postify:suggest_optimal_time for each platform the user publishes on and give the top suggestion per platform.

    line 31
  6. Distinctive:

    Only report numbers the tools returned.

    line 36
  7. Distinctive:

    Do not compare the user to industry benchmarks.

    line 37

≈ “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/reviewing-social-performance/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Postify performance review

Read the workspace's delivery analytics and turn them into a short, honest report.

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:get_analytics: workspace analytics for delivered posts: post counts, delivery rate, per-channel stats, for a date range.
  • postify:suggest_optimal_time: suggested posting times per platform from the workspace's own publish history. No model call, no external data.
  • postify:list_posts: to name the specific posts behind a number when the user asks "which ones".

Workflow

  1. Agree the window (default: the last 30 days). Call postify:get_analytics for it.
  2. Report in this order: total posts delivered, delivery rate, failed posts, then a per-channel table sorted by volume.
  3. If there were failures, call postify:list_posts filtered to failed for the window and list them with their channel and datetime so the user can act.
  4. Call postify:suggest_optimal_time for each platform the user publishes on and give the top suggestion per platform.
  5. Close with at most three concrete next steps drawn from the numbers.

Rules

  • Only report numbers the tools returned. If a metric is missing, say it is not available in Postify analytics.
  • Do not compare the user to industry benchmarks; there are none in the data.
  • This skill only reads. Never call postify:create_draft, postify:reschedule_post, postify:publish_now, or postify:delete_post from it.

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.