AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

auditing-experiments-flags

Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--auditing-experiments-flags at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 6

references/finding-taxonomy.md

Finding types

Severities

| Severity | Badge | Meaning | | -------- | ----- | --------------------------------------------------------------------------------- | | CRITICAL | 🔴 | Blocks correctness — experiment results may be invalid or flag behavior is broken | | WARNING | 🟡 | Needs attention — not broken yet but risks exist or best practices are violated | | INFO | 🔵 | Suggestion — hygiene improvement, safe to defer |

Finding categories

| Category | Description | Max severity | | ----------- | -------------------------------------------------------------------------------------------------- | ------------ | | Correctness | Integrity issues that affect experiment results or flag evaluation | CRITICAL | | Waste | Active resources not serving a purpose (running experiments going nowhere, flags nobody evaluates) | WARNING | | Process | Methodology and practice issues (missing hypothesis, no metrics) | WARNING | | Complexity | Fragility and maintainability concerns (too many toggles, high churn) | WARNING | | Cleanup | Hygiene items — stale drafts, orphaned flags, safe to defer | INFO | | Security | PII or access concerns in flag/experiment configuration | WARNING |

Severity caps

Never assign a severity higher than the category's max:

  • A Cleanup finding is always INFO, never WARNING or CRITICAL.
  • A Correctness finding can be CRITICAL, WARNING, or INFO depending on impact.
  • A Waste or Process finding caps at WARNING.

Finding format

When reporting a finding, always include:

  1. Severity — one of CRITICAL, WARNING, INFO
  2. Category — one of the categories above
  3. Check name — which check produced this (e.g., "Metric setup", "Flag integration")
  4. Entity — which experiment or flag, as a markdown link
  5. Description — one sentence explaining what's wrong
  6. Action — one sentence explaining what to do (reference remediation actions)

Ordering

When listing multiple findings:

  1. Sort by severity: CRITICAL first, then WARNING, then INFO.
  2. Within the same severity, group by entity.
  3. Within the same entity, list by category: Correctness → Waste → Process → Complexity → Cleanup → Security.