agentsclimarketplace
Sign in

Socialseal management reporting

Skill OpenSealAI/agent-skills/skills/socialseal-management-reporting

Use this skill when creating senior stakeholder summaries from SocialSeal tracking and readout data. It converts detailed discoverability evidence into a concise business-language update with decisions, risks, and next priorities.From its SKILL.md

Install
npx -y skills add OpenSealAI/agent-skills --skill socialseal-management-reporting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, 487 tokens by cl100k_base, as published. Nobody here has run it

SocialSeal Management Reporting

Overview

Management reporting is not the full analysis. It is the decision layer: what changed, why it matters, what decision is needed, and what happens next.

Inputs

  • performance readout
  • priority recommendations
  • goals/KPIs or success criteria
  • examples that make the finding tangible
  • risks or decisions needing stakeholder input

Workflow

  1. Write the headline first. One sentence with the overall state and decision implication.
  2. Select 3-5 metrics. Discoverability, keyword coverage, SOV, owned/creator split, or priority topic movement.
  3. Translate to business language. Define terms briefly; avoid internal tool jargon and internal IDs. Cite examples by video title/URL, @handle, and "keyword" [market, platform].
  4. Use examples sparingly. 2-3 examples that show the pattern, not a dump of links.
  5. State decisions and risks. Budget, production capacity, market focus, tracking gaps, or approval needs.
  6. List next priorities. What the team will do before the next report.

Output

  • one-page summary or slide-ready narrative
  • metric snapshot
  • 2-3 evidence examples
  • decision/risk section
  • next priorities

Do / Don't

Do:

  • lead with the answer
  • keep scope and date visible
  • explain metrics in plain language
  • include next action and owner where known

Don't:

  • include every table from the readout
  • use internal IDs or system terms
  • bury caveats
  • turn the summary into a pitch deck

Troubleshooting

  • If the summary is too long, move method and detail to appendix.
  • If stakeholders may question the data, add a one-line scope note near the metrics: the figures are exact observations of tracked social search, scoped to high-ranking videos for the tracked queries (not whole-market demand). See references/evidence-and-confidence.md.
  • If no decision follows, the report is probably still analysis, not management reporting.

Verification Checklist

  • Headline answer is clear.
  • Metrics are limited and defined.
  • Scope/date range are visible.
  • Risks and decisions are explicit.
  • Next priorities are concrete.

What ships with it: 1 file

4.2 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,452. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.