Agent skill

Feature Flags Authoring

Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper.

Apache-2.0Auto-check passedFrontend & Design

Install Feature Flags Authoring

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .claude/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .claude/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .agents/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .agents/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .cursor/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .cursor/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/PackmindHub/packmind.git --path .claude/skills/feature-flags-authoring

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .gemini/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .gemini/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .github/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .github/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PackmindHub/packmind --skill feature-flags-authoring -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind feature-flags-authoring --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/feature-flags-authoring .opencode/skills/feature-flags-authoring && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "feature-flags-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/feature-flags-authoring into .opencode/skills/feature-flags-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-authoring", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: feature-flags-authoring
GitHub stars: 317
Token cost: ~1.5k tokens
SKILL.md length: 608 words
Files: 1
Skills in repo: 35
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper.

Works in 4 steps: Register it in @packmind/feature-flags → Gate the frontend → Gate the backend → …
The user wants to create a new feature flag
SKILL.md covers Where things live, Add a flag, Edit a flag and Remove a flag, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Flags Authoring is an agent skill from PackmindHub/packmind. Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper. Use when the user wants to create a new feature flag, gate a feature behind a flag, open or restrict a flag to a domain/email, change a flag audience, retire or delete a flag, or asks how the feature-flag system is wired. This is the developer how-to counterpart to the feature-flags-audit skill.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.

When your agent uses it

The user wants to create a new feature flag
Gate a feature behind a flag
Restrict a flag to a domain/email
Change a flag audience

Example prompts

“/feature-flags-authoring”

Requirements

A credential in MY_FEATURE_KEY

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Register it in @packmind/feature-flags
Gate the frontend
Gate the backend
(Optional) Env override

What it can do on your machine

Read from SKILL.md and the folder at commit 67de8a2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Flags Authoring loads about 1.5k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 608 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~109
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PackmindHub/packmind at commit 67de8a2, republished under its Apache-2.0 licence (© PackmindHub). 608 words, ~1,492 tokens.

Download SKILL.mdSave it as .claude/skills/feature-flags-authoring/SKILL.md (or your agent's skills folder).

name: feature-flags-authoring
description: Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper. Use when the user wants to create a new feature flag, gate a feature behind a flag, open or restrict a flag to a domain/email, change a flag audience, retire or delete a flag, or asks how the feature-flag system is wired. This is the developer how-to counterpart to the feature-flags-audit skill.

Feature Flags Authoring

A developer how-to for the full lifecycle of a Packmind feature flag: add, edit, remove. Flags gate a feature by email domain (or exact email). The same decision function runs on frontend and backend, so behavior never diverges. Follow the steps below exactly — every flag touches three places.

For inventorying existing flags, orphan detection, and audience audits, use the feature-flags-audit skill instead. This skill changes flags; that one scans them.

Where things live

Shared registry — @packmind/feature-flags (pure, env:shared, browser-safe). The single source of truth:
- registry.ts — the *_FEATURE_KEY constants, DEFAULT_FEATURE_DOMAIN_MAP (Record<string, readonly string[]> mapping each flag's string value to allowed entries), and the FeatureFlagKey union.
- isFeatureFlagEnabled.ts — the pure evaluator: isFeatureFlagEnabled({ featureKeys, featureDomainMap, userEmail }).
Frontend gate — <PMFeatureFlag> from @packmind/ui (or a direct isFeatureFlagEnabled(...) call). The keys, DEFAULT_FEATURE_DOMAIN_MAP, and isFeatureFlagEnabled are re-exported from @packmind/ui for back-compat, so existing consumers can import from either place.
Backend gate — isFeatureEnabled(flag, { userEmail }), a plain async helper from @packmind/node-utils. It resolves the env kill-switch first, then defers to the shared email-domain rule. It is NOT a port and has no DI — import it and call it.
Env kill-switch — FF_<SCREAMING_SNAKE> (e.g. FF_CHANGE_PROPOSALS_IN_WEBAPP). on/all/true force the flag on; off/none/false force it off; unset or empty falls through to the email-domain map.

Two flags exist today: 'change-proposals-in-webapp' and 'orga-space-management'.

Add a flag

1. Register it in `@packmind/feature-flags`

Add the key constant, the audience entry, and extend the union. Do all three — a constant with no map entry is never enabled for anyone; a map entry with no union member can't be typed at call sites.

// registry.ts
export const MY_FEATURE_KEY = 'my-feature' as const;

export type FeatureFlagKey =
  | 'change-proposals-in-webapp'
  | 'orga-space-management'
  | 'my-feature';

export const DEFAULT_FEATURE_DOMAIN_MAP: Record<string, readonly string[]> = {
  // ...
  'my-feature': ['@packmind.com'], // domains keep the `@`; exact emails have no leading `@`
};

2. Gate the frontend

Wrap the UI that should appear only when the flag is on:

tsx

import { PMFeatureFlag } from '@packmind/ui';
import { MY_FEATURE_KEY, DEFAULT_FEATURE_DOMAIN_MAP } from '@packmind/feature-flags';

<PMFeatureFlag
  featureKeys={[MY_FEATURE_KEY]}
  featureDomainMap={DEFAULT_FEATURE_DOMAIN_MAP}
  userEmail={currentUser.email}
>
  {/* gated UI */}
</PMFeatureFlag>

For a branch (route, tab, boolean), call isFeatureFlagEnabled({ featureKeys: [MY_FEATURE_KEY], featureDomainMap: DEFAULT_FEATURE_DOMAIN_MAP, userEmail }) directly.

3. Gate the backend

Inside a member use case, command.user.email is available. Branch on the helper:

import { isFeatureEnabled } from '@packmind/node-utils';
import { MY_FEATURE_KEY } from '@packmind/feature-flags';

if (await isFeatureEnabled(MY_FEATURE_KEY, { userEmail: command.user.email })) {
  // new path
} else {
  // old path
}

4. (Optional) Env override

Set FF_MY_FEATURE=on to force the flag on everywhere, or FF_MY_FEATURE=off to force it off, regardless of the domain map. Leave unset to defer to the map. Document the var in the deploy config if you rely on it.

Show full SKILL.md (263 more words)Show less

Edit a flag

Change the allowed audience in DEFAULT_FEATURE_DOMAIN_MAP — add or remove domains (@company.com) or exact emails (user@company.com). This is the only place audience lives; the frontend and backend both read it.

Remember: the FF_* env kill-switch overrides the map at runtime. If a flag looks stuck on or off in an environment, check the env var before editing the map.

Remove a flag

In @packmind/feature-flags: delete the *_FEATURE_KEY constant, its DEFAULT_FEATURE_DOMAIN_MAP entry, and its FeatureFlagKey union member.
Delete every call site:
- Frontend: remove the <PMFeatureFlag> wrappers (keep the children — the UI ships unconditionally now) and any isFeatureFlagEnabled branches.
- Backend: remove the isFeatureEnabled branches, keeping the winning branch inline.
Drop any FF_<SCREAMING_SNAKE> env var from deploy config.
Run the feature-flags-audit skill to confirm no orphaned keys, map entries, or call sites remain.

Conventions

Audience is email-domain only (Proposal A). No org, plan, team, or percentage targeting exists yet — do not describe or build it.
Never log an email in clear text. If you log a flag decision, mask the email (first 6 chars + *) or, better, log only the flag key and the boolean outcome.
Keep @packmind/feature-flags pure and browser-safe. No env:node imports (no @packmind/node-utils, no Configuration.getConfig, no process.env). It ships to the browser bundle.
The backend gate is a plain helper call, not an injected port. Import isFeatureEnabled and call it directly; do not add a port/adapter/registry.

Files

Just SKILL.md in .claude/skills/feature-flags-authoring of PackmindHub/packmind.

Open the folder on GitHubat commit 67de8a2

Compare with similar skills

Feature Flags Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature Flags Authoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Feature Flags Authoring this skillPackmindHub/packmind	317	—	~1.5k	Automated safety check: Pass	Apache-2.0	today
Web Artifacts Builderanthropics/skills	180k	41 repos	~769	Automated safety check: Pass	Apache-2.0	today
React Doctormakeplane/plane	61k	12 repos	~657	Automated safety check: Pass	AGPL-3.0	today
Impeccablebestofjs/bestofjs	3.1k	27 repos	~2.6k	Automated safety check: Pass	MIT	4 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Web Interface Guidelines Reviewervercel-labs/openreview	1.7k	97 repos	~308	Automated safety check: Pass	None	7 mo ago

Similar skills

Web Artifacts Builder
anthropics/skills
Official
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
180k GitHub starsUsed in 41 repos~769 tokens
Frontend & DesignAuto-check passed
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
61k GitHub starsUsed in 12 repos~657 tokens
Frontend & DesignAuto-check passed
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 27 repos~2.6k tokens
Frontend & DesignAuto-check passed
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Web Interface Guidelines Reviewer
vercel-labs/openreview
Official
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
1.7k GitHub starsUsed in 97 repos~308 tokens
Frontend & DesignAuto-check passed
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
4.9k GitHub starsUsed in 10 repos~865 tokens
Frontend & DesignAuto-check passed

More from PackmindHub/packmind

All 35 skills in this repo

Michel CLI Demo Recorder
PackmindHub/packmind
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.
317 GitHub stars~3.4k tokensUpdated today
Auto-check passed
Michel UI Demo Recorder
PackmindHub/packmind
Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.
317 GitHub stars~6.4k tokensUpdated today
Auto-check passed
Packmind Create Skill
PackmindHub/packmind
Guide for creating effective skills. An agent skill from PackmindHub/packmind.
317 GitHub stars~3.5k tokensUpdated today
Auto-check: notes
Doc Audit
PackmindHub/packmind
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.
317 GitHub stars~2.4k tokensUpdated today
Auto-check passed
Feature Sprint
PackmindHub/packmind
Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.
317 GitHub stars~1.9k tokensUpdated today
Auto-check passed
Michel Packmind Engineer Review
PackmindHub/packmind
Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…
317 GitHub stars~2.7k tokensUpdated today
Auto-check passed

Questions about Feature Flags Authoring

What does Feature Flags Authoring do?

Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper. Feature Flags Authoring is an agent skill from PackmindHub/packmind. Add, edit, or remove a Packmind feature flag across the shared registry, the frontend gate, and the backend helper.

When should I use Feature Flags Authoring?

Feature Flags Authoring fits situations like: the user wants to create a new feature flag; gate a feature behind a flag; restrict a flag to a domain/email; change a flag audience.

How do I install Feature Flags Authoring in Claude Code?

Run `npx skills add PackmindHub/packmind --skill feature-flags-authoring -a claude-code`. Or copy the skill folder (.claude/skills/feature-flags-authoring in PackmindHub/packmind) into .claude/skills/feature-flags-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Feature Flags Authoring in Codex?

Run `npx skills add PackmindHub/packmind --skill feature-flags-authoring -a codex`. Or copy the skill folder (.claude/skills/feature-flags-authoring in PackmindHub/packmind) into .agents/skills/feature-flags-authoring in your project. Codex loads it when a task matches its description.

Can I use Feature Flags Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PackmindHub/packmind --skill feature-flags-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-flags-authoring, .gemini/skills/feature-flags-authoring, .github/skills/feature-flags-authoring and .opencode/skills/feature-flags-authoring in your project.

What does Feature Flags Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Flags Authoring is instructions for the agent only. Our summary lists: A credential in MY_FEATURE_KEY.

Does Feature Flags Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feature Flags Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature Flags Authoring use?

Feature Flags Authoring is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature Flags Authoring use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Feature Flags Authoring?

Skills that share tags, products or a category with Feature Flags Authoring: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Flags Authoring?

PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

Source: PackmindHub/packmind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Feature Flags Authoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Feature Flags Authoring

Where things live

Add a flag

1. Register it in @packmind/feature-flags

2. Gate the frontend

3. Gate the backend

4. (Optional) Env override

Edit a flag

Remove a flag

Conventions

See also

Files

Compare with similar skills

Similar skills

More from PackmindHub/packmind

Related

Questions about Feature Flags Authoring

1. Register it in `@packmind/feature-flags`