auditing-experiments-flags
/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.
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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 author description
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.
How it works
- Usage modes
- Output format
- Handling unavailable data
- Partial failures
- Reference files
SKILL.md preview
--- name: auditing-experiments-flags description: '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.' --- # Auditing experiments and feature flags This skill teaches you how to run configuration audits on experiments and feature flags. All checks use the experiment and feature flag read tools (`experiment-get`, `experiment-list`, `feature-flag-get-definition`, `feature-flag-get-all`) — no SQL queries are needed for Phase 1 checks. ## Usage modes ### Quick check (single entity) When the user asks about a specific experiment or flag: 1. Fetch the entity via `experiment-get` (experiment ID) or `feature-flag-get-definition` (numeric flag ID). 2. Apply the relevant checks from [experiment checks](./references/experiment-checks.md) or [flag checks](./references/flag-checks.md). 3. Report findings inline as markdown, grouped by severity (CRITICAL first, then WARNING, then INFO). 4. Include entity links as `[Experiment: name](/experiments/id)` or `[Flag: key](/feature_flags/id)`. ### Scoped audit (one domain) When the user asks to audit all experiments or all flags: 1. Bulk-fetch via `experiment-list` or `feature-flag-get-all`. 2. Run all checks for that domain against each entity. 3. Group findings by severity, then by entity. 4. Report as inline markdown. ### Full audit (comprehensive) When the user asks for a comprehensive audit of both experiments and flags: 1. Fetch all experiments via `experiment-list` and all flags via `feature-flag-get-all`. 2. Run all experiment checks and all flag checks. 3. Apply [recurring patterns](./references/synthesis-patterns.md) to identify patterns across multiple findings. 4. If there are more than 5 entities with findings, write them to a notebook for easier navigation. Otherwise report inline. Create the notebook from the project's own notebook tools. Run `search notebooks?-` to load them and read the titles. ## Output format For each finding, include: - **Severity badge**: `🔴 CRITICAL`, `🟡 WARNING`, or `🔵 INFO` - **Check name**: Which check produced this finding - **Entity link**: Markdown link to the entity - **What's wrong**: One-sentence description - **Action**: What to do about it (see [remediation actions](./references/remediation-actions.md)) Example: > 🟡 **WARNING** — Flag integration · [Experiment: checkout-redesign](/experiments/42) > The linked feature flag is inactive (paused). Traffic is not being split. > **Action**: Re-enable the flag or end the experiment. ## Handling unavailable data Some checks require activity logs (`feature-flags-activity-retrieve` for flags), which may not be available in every session. If activity log data is unavailable: - Skip `checkActivityHistory` (experiment check) entirely. - Skip the "toggle instability" and "never activated" sub-checks in flag lifecycle checks. - In your report, note which checks were skipped and why: > _Skipped: Activity history checks (activity logs not available via current tools)_ ## Partial failures If a fetch call fails for some entities: - Continue with the entities you could fetch. - Report which entities could not be assessed and why. - Do not silently omit entities from the audit. ## Reference files - [Experiment checks](./references/experiment-checks.md) — experiment configuration checks - [Flag checks](./references/flag-checks.md) — feature flag checks - [Finding types](./references/finding-taxonomy.md) — severity and category definitions - [Recurring patterns](./references/synthesis-patterns.md) — patterns across multiple findings - [Remediation actions](./references/remediation-actions.md) — what to do about each finding
Files in this package (6)
- SKILL.md 4 KB
- references/experiment-checks.md 9 KB
- references/finding-taxonomy.md 3 KB
- references/flag-checks.md 5 KB
- references/remediation-actions.md 5 KB
- references/synthesis-patterns.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · PostHog/skills | 100 | MIT |
| 420company/artemis | 95 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version a96b0ef44018 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100posthog
PostHog is an open-source product analytics platform: event tracking, funnels, retention, session replay, feature flags and experiments in one tool, on PostHog Cloud or self-hosted. Use when someone asks to "add product analytics", "track events with PostHog", "set up session… - 95cleaning-up-stale-feature-flags
Identify stale feature flags in a PostHog project and clean up the code that checks them. Use when the user wants to find, audit, or remove unused, fully rolled out, or abandoned feature flags, run a feature flag hygiene review or a weekly cleanup, reduce feature flag tech debt,… - 100cleaning-up-stale-feature-flags
Identify stale feature flags in a PostHog project and clean up the code that checks them. Use when the user wants to find, audit, or remove unused, fully rolled out, or abandoned feature flags, run a feature flag hygiene review or a weekly cleanup, reduce feature flag tech debt,… - 100posthog-core-workflow-b
Implement a safe PostHog feature-flag and experiment lifecycle with defaults, exposure integrity, rollout ownership, and cleanup. Use when releasing behind flags or running controlled experiments. Trigger with "PostHog feature flag", "PostHog experiment", or "A/B test". - 85posthog
Analyze product data and manage product tooling in PostHog. Use when the user wants product analytics or insights, HogQL/SQL queries, feature flags, experiments and A/B tests, error tracking, session replay, surveys, LLM analytics, dashboards, data warehouse, or PostHog documentation. - 100posthog
Session replays, product events, error tracking, feature flags and HogQL over a connected PostHog project. Use when the user asks what a user did before a bug, for a session recording or replay, for product analytics, for who an exception hit, or about a feature flag's rollout.