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/synthesis-patterns.md

Recurring patterns

Apply these patterns during full audits (both experiments and flags). Each pattern looks for a cluster of related findings that together suggest a bigger problem.

Experiment setup gaps

Trigger: 3+ experiments have PROCESS-category findings (missing hypothesis, no metrics, no conclusion).

Message:

Multiple experiments lack key setup steps (hypothesis, metrics, or conclusions). This suggests the team may benefit from an experiment setup checklist or template.

Flag hygiene debt

Trigger: 5+ flags have CLEANUP-category findings (stale drafts, fully rolled out, orphaned experiment flags).

Message:

There are many flags that could be cleaned up. Consider scheduling a flag cleanup session to remove stale flags from the codebase and reduce unnecessary flag evaluations.

Experiment-flag disconnection

Trigger: At least one experiment has a "stopped with active flag" finding AND at least one has a "mid-run flag change" finding.

Message:

Some experiments have flags that were modified during their run, and others were stopped but their flags are still active. This suggests the experiment-flag lifecycle is not well-coordinated. Consider establishing a post-experiment cleanup process.

Reporting patterns

When a pattern triggers:

  1. Add a "Recurring patterns" section after individual findings.
  2. List each triggered pattern with its message.
  3. These are always INFO severity — they are observations, not individual findings.