← ClaudeAtlas

socialseal-management-reportinglisted

Use this skill when the user asks for an executive, leadership, board, client, or senior-stakeholder summary of SocialSeal results. Convert detailed tracking/readout evidence into a concise business-language update with scope, decisions, risks, examples, and next priorities rather than repeating the full analysis.
OpenSealAI/agent-skills · ★ 0 · Data & Documents · score 65
Install: claude install-skill OpenSealAI/agent-skills
# 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 ##