AGENT SKILL

social-content-performance

暂无简介

License 许可
CC0-1.0
最近更新
2026-11-14
Stars
★ 0
Forks
0

02 资源文件 2

03 SKILL.md 正文

Social Content Performance

Scope the question

  • For a caption or hashtag request with no analysis question, write from the user's brief and the material they supply, return the draft and stop. Do not fetch account data or establish a reporting period for this branch. The remaining analysis steps apply only to performance questions.

  • For a performance question, identify the network, the account and what the user wants to learn, such as which posts reached the most people, how a launch landed or what to post next. Settle the reporting period and timezone before fetching anything.

  • Analyze only accounts the user manages. Take the account from the connector's own account list, ask which one to use when several fit, and stop when a named account is not returned rather than substituting another.

  • Comparisons with competitors, peers or industry norms use Social Competitor Analysis, which muse.skill_search finds when this session has it. Public figures cannot fill a gap in the user's private metrics.

Gather the evidence

  • Retrieve the posts in scope with their publication times and permalinks, then the metrics the question needs. Preserve each connector's returned metric display names exactly rather than replacing them with generic labels or labels from memory.

  • For Instagram post metrics, use the connector's owned-post insights and media definitions. These figures cover each post's lifetime rather than the selected reporting period; compare posts of similar age and state that scope.

  • Keep each metric at the level it was returned. Account totals do not describe one post, daily unique-account values do not add up to a unique count across a period, and a missing value is unknown rather than zero.

  • Keep metrics with different counting conditions or denominators distinct. Separate organic from paid results and keep follower and non-follower breakdowns when they are returned.

  • Use only the account's own data as evidence about its performance. Web results, social search, outside benchmarks and remembered figures do not count.

Find what actually worked

  • Compare like with like, matching format, post age, period and audience basis. Note when a post had paid support or reached an unusual audience.

  • Review the complete eligible set before calling a post the best, ranking posts or computing an average. One strong post is an example, not a formula.

  • Separate how often a format was used from how well it performed. Do not infer causes, audience intent, sensitive traits or algorithm behavior from a correlation.

Recommend the next step

  • Lead with the answer and support each finding with the values compared. Follow Presenting social results for the format, post labels, links and scope statement.

  • Tie one or two next experiments to the user's objective, with what to measure and when to look again. Promise no outcome.

  • When a requested metric does not exist at the requested level, say so and offer the nearest available measure without presenting it as the same thing.

  • Report consent, account-linking and eligibility errors as they are. Do not retry a policy denial or work around it with another tool.

  • Analysis does not authorize publishing or changing a campaign. Use Social Publishing or Advertising Campaigns when the user wants to act on the findings.

Available connectors

  • Instagram for the user's posts, owned-post lifetime insights, account insights and metric definitions.

  • Facebook for managed Page insights, Page post metrics and the reactions and comments on personal posts.

  • Threads for the user's posts, post insights, top posts and account insights.

  • Use muse.connector_search to find other connectors and muse.skill_search to find related skills.

  • If nothing here fits, look on the web for a maintained API or MCP server and set it up with Custom Connectors and MCPs, or build a custom connector.

When available

  • These connectors depend on the user's channel or devices. muse.connector_search shows which ones this session has.

  • Upload-Post for post and platform analytics across the networks connected to Upload-Post.

  • vidIQ for YouTube channel, video and subscriber analytics.

Websites

  • Open a network's own analytics with browser.browse when no connector covers that network, measure or period. Give the task the exact account, period and timezone, and have it return each figure with its metric name and any export it produced.

  • YouTube Studio for YouTube channel and video analytics.

  • TikTok Studio for TikTok account and post analytics.

  • LinkedIn for the analytics of company Pages the user administers.

  • Pinterest Analytics for Pin and board performance.

Alternatives for better results

  • Join content results to business outcomes with the user's own website, lead or sales records when they share access. Without that evidence, report engagement as engagement rather than business impact.

  • Compare each post with the account's own baseline for the same format rather than with industry averages.

  • Offer a follow-up review with cron.add when results need time to mature, such as a video's views over its first week.

04 同仓库更多 Skills

raaOS
raaOS/system_prompts_leaks

model-council

暂无简介

★ 0
raaOS
raaOS/system_prompts_leaks

writing-style

Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.

★ 0
raaOS
raaOS/system_prompts_leaks

write-page

Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.

★ 0
raaOS
raaOS/system_prompts_leaks

software-engineering

For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.

★ 0
raaOS
raaOS/system_prompts_leaks

slides-artifact

Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.

★ 0
raaOS
raaOS/system_prompts_leaks

slack

Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.

★ 0