--- name: meta-analytics-stinger description: "Calculate Meta social and paid metrics, compare periods, track goals and supply evidence-aware optimization calculations. Use for reports and numerical analysis." license: AGPL-3.0-or-later compatibility: "Claude Code, Cursor, ChatGPT Codex, Claude Cowork; Python 3.11+" metadata: hive-tier: specialist paired-drone: meta-analytics-wasp-drone hive-drone: meta-analytics-wasp-drone domain: meta-analytics version: "1.0.0" --- # Meta Analytics Stinger Produce reproducible numerical results with source lineage, compatible definitions and explicit limits. [README](README.md) maps the procedures and actual CLIs. ## Procedure 1. Resolve selected Foundation, brand/profile/account identity and accepted contracts. Record dates, currency, attribution, source and desired outcome. 2. Read [calculation policy](references/calculation-policy.md) and the registry. Ask the provider owner to collect only authorized reads with full source/completeness metadata. 3. Normalize saved evidence using [the CLI contract](references/cli-contract.md). Preserve zero, missing, withheld, unsupported, failed, partial and immature states. 4. Compute from compatible components. Reject mixed scopes/currencies, duplicate sources, non-additive sums and mismatched cohort or period bases. 5. Follow [reporting](guides/report-results.md), [comparison](guides/compare-performance.md) or [goal tracking](guides/track-goals.md). Do not invent business targets or benchmark percentiles. 6. For experiments/budgets/rules, use [optimization calculations](guides/review-optimization-calculations.md) and the pinned method. Keep descriptive differences separate from qualified inference. 7. Validate result/source reconciliation. Hand the same JSON to the artifact owner and report actual paths, numerical inputs, coverage/maturity and limitations. Return recommendations to existing execution owners. ## Boundaries Analytics owns metric/benchmark/method/rubric definitions and shared numerical calculations. The provider adapter owns collection; Social Audit owns assessments and the scorer; artifact tooling owns workbooks/charts; Advertising Optimization owns diagnosis. This skill performs no provider mutation, account setup, paid support or approval issuance. ## Research [Distillation](references/research/distillation.md) and [conflicts](references/research/conflicts.md) ground the documented source behavior. Raw research stays source-only; installed runtime never depends on it. ## Related owners - [Paired Drone](../../agents/meta-analytics-wasp-drone.md). - [Social Audit](../meta-social-audit-stinger) for evidence and human-reviewed criteria. - Installed Foundation/Doctor for identity/access; Advertising Optimization for decisions; existing execution owners for approved changes. ## 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-social-audit-stinger](../meta-social-audit-stinger) - Evidence classification and scored social reviews. ## 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.