CtrlK
BlogDocsLog inGet started
Tessl Logo

copying-flags-across-projects

Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean yet information-dense: it gives an explicitly sequenced 6-step workflow, names exact tool calls and parameters with safe defaults, and includes validation/confirmation checkpoints plus a per-target retry loop for the batch operation. It assumes Claude's competence throughout and avoids explaining background concepts, with no bundle files needed given the clear single-file organization.

DimensionReasoningScore

Conciseness

Every section earns its tokens with non-obvious PostHog-specific detail (e.g. 'gated by an INTERNAL viewset and * consent does not satisfy it') and never pads with concepts Claude already knows about feature flags.

3 / 3

Actionability

Names exact tool calls and exact required/optional fields — 'posthog:feature-flags-copy-flags-create' with 'feature_flag_key', 'from_project', 'target_project_ids', 'disable_copied_flag', 'copy_schedule' — plus concrete defaults, making the guidance copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

A clear 6-step sequence with explicit checkpoints — preview before copy, confirm safe-default options, per-target success/failed reporting, and a retry/skip/fix feedback loop for failed targets — satisfying the batch/destructive feedback-loop requirement.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single file is organized into well-signaled sections (When to use, Does not cover, Workflow, Important notes, Example, Available tools) with no dangling or nested references.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete, and clearly distinct: it names concrete sub-capabilities (cohort remapping, encrypted payloads, scheduled changes, safe defaults), provides an explicit 'Use when' clause with multiple natural phrasings, and carves out a clear PostHog-specific niche. It uses third-person voice throughout with no first/second-person phrasing to penalize.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities beyond the core copy — 'cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes)' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states both what it does ('Copy a feature flag from one PostHog project...') and when to use it via an explicit 'Use when...' trigger clause, so neither what nor when is merely implied.

3 / 3

Trigger Term Quality

The 'Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace' clause covers several natural phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to a distinct niche — cross-project PostHog feature-flag duplication with its own trigger phrasings — and even redirects cleanup to a sibling skill, making misfires unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.