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).

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill body for a destructive/batch operation, with strong validation checkpoints and feedback loops. The only minor weakness is slight redundancy between the workflow steps and the Important notes.

Suggestions

Trim redundancy: the "Cohorts are remapped automatically", "Scheduled changes copy with cohort remap too", and auth/access notes partly restate guidance from steps 3-4 — consolidate so each fact appears once.

Consider shortening the "Important notes" section by folding the auth-requirement bullets (feature_flag:write scope, editor access, per-target access) into a single compact "Prerequisites" checklist.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains what a feature flag is — but a few "Important notes" entries restate guidance from the workflow steps and could be trimmed further.

4 / 5

Actionability

Gives exact MCP tool names, required and optional fields, concrete default values (disable_copied_flag: true, copy_schedule: false), and per-target success/failure handling with no real gaps in executable guidance.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation (mandatory dependencies-check in step 3), a confirmation gate before a destructive operation (step 4), and a retry/skip/fix feedback loop for failures (step 6).

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the skill is single-purpose and well-organized into clear sections (When to use / exclusions / Workflow / notes / example / tools) with appropriately concise inline content and no nested references.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

A strong, specific description that states concrete capabilities, explicit trigger conditions, and safe defaults. It is comprehensive yet concise with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Copy a feature flag", "cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults" — giving comprehensive coverage of the capability surface rather than vague verbs.

5 / 5

Completeness

Explicitly answers both what (copy a flag across same-org projects, with named sub-capabilities) and when (a clear "Use when the user wants to..." clause listing concrete triggers).

5 / 5

Trigger Term Quality

Captures natural user phrasings with strong synonym coverage — "duplicate a flag", "promote a flag from staging to production", "sync flags across projects", "replicate a flag configuration" — the terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — copying PostHog feature flags across projects — with distinct triggers unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

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.

Validation — 16 / 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.