---
name: meta-social-audit-stinger
description: "Audit Facebook, Instagram and Threads presence with evidence, human-reviewed judgments, deterministic scores and coverage. Use for social audits and re-audits."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork; Python 3.9+"
metadata:
  hive-tier: specialist
  paired-drone: meta-social-audit-wasp-drone
  hive-drone: meta-social-audit-wasp-drone
  domain: meta-social-audit
  version: "1.0.0"
---

# Meta Social Audit Stinger

Review the selected brand's social presence against a versioned product rubric and deliver evidence-linked findings, score/coverage/bounds, and a correction tracker. [README](README.md) maps the full procedure.

## When to use

Use for `audit-my-social`, a scored `audit-my-feed` handoff, or a re-audit after approved corrections. Foundation resolves brand/profile/account identity first.

## Procedure

1. Read [the audit guide](guides/audit-social.md), selected rubric and [evidence rules](references/evidence-classification.md).
2. Declare platform/window/sample and approved brand/calendar targets. Collect only the scoped evidence through accepted read operations; retain completeness and freshness.
3. Score observable criteria against their anchors. Missing access, uninspected media and unreviewed judgments stay unknown. Known zero remains known.
4. Obtain human review of subjective/mixed assessments. An agent/script never promotes its own proposal into a known subjective score.
5. Use the shared Analytics scorer with the [local assessment record](references/assessment-record.md) and [scoring math](references/scoring-math.md). No known evidence means no score; under 80% coverage remains provisional.
6. Deliver findings with rubric/source/run versions, evidence limitations and owners. Route changes to existing execution owners; an audit does not edit, publish, install pixels or change campaigns.
7. Follow [re-audit](guides/re-audit.md) only after the owner supplies observed correction evidence.

## Related owners

- [Meta Analytics](../meta-analytics-stinger): metric definitions, deterministic calculations, rubric JSONs and reporting.
- [Paired Drone](../../agents/meta-social-audit-wasp-drone.md): scoped audit execution.
- Social Media Doctor: installed Foundation owner for access, account identity and sync readiness.
- Content/Publishing, Tracking and Advertising: installed owners for reviewed corrections.

## Research and limits

[Distillation](references/research/distillation.md) and [conflicts](references/research/conflicts.md) ground provider/accessibility facts. This is a sampled review, not a full WCAG/legal-conformance or AI-authorship determination. Raw research is source-only; runtime does not require it.

## Critical Directive

- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
  - [meta-analytics-stinger](../meta-analytics-stinger) - Metric definitions, evidence-aware calculations and report artifacts.

## Ship Gate

Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.