Agent skill

Add Feature Flag

by cadence-workflow in cadence-workflow/cadence-web

Add a new boolean feature flag (dynamic config key) to cadence-web.

Apache-2.0Auto-check: notesBackend & APIs

Install Add Feature Flag

skills CLI

$ npx skills add cadence-workflow/cadence-web --skill add-feature-flag -a claude-code

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

GitHub CLI

$ gh skill install cadence-workflow/cadence-web add-feature-flag --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/cadence-workflow/cadence-web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-feature-flag .claude/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .claude/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag

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 cadence-workflow/cadence-web --skill add-feature-flag -a codex

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

GitHub CLI

$ gh skill install cadence-workflow/cadence-web add-feature-flag --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/add-feature-flag .agents/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .agents/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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 cadence-workflow/cadence-web --skill add-feature-flag -a cursor

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

GitHub CLI

$ gh skill install cadence-workflow/cadence-web add-feature-flag --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/add-feature-flag .cursor/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .cursor/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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/cadence-workflow/cadence-web.git --path .agents/skills/add-feature-flag

--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 cadence-workflow/cadence-web --skill add-feature-flag -a gemini-cli

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

GitHub CLI

$ gh skill install cadence-workflow/cadence-web add-feature-flag --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/cadence-workflow/cadence-web.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/add-feature-flag .gemini/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .gemini/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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 cadence-workflow/cadence-web add-feature-flag

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 cadence-workflow/cadence-web --skill add-feature-flag -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/add-feature-flag .github/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .github/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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 cadence-workflow/cadence-web --skill add-feature-flag -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 cadence-workflow/cadence-web add-feature-flag --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/cadence-workflow/cadence-web.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/add-feature-flag .opencode/skills/add-feature-flag && 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 "add-feature-flag" agent skill from https://github.com/cadence-workflow/cadence-web/tree/master/.agents/skills/add-feature-flag into .opencode/skills/add-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-feature-flag", 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: add-feature-flag
GitHub stars: 436
Token cost: ~1.1k tokens
SKILL.md length: 302 words
Files: 1
Skills in repo: 2
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Add a new boolean feature flag (dynamic config key) to cadence-web.

Works in 5 steps: Resolver —… → Register —… → Zod schema —… → …
Set up a feature flag
SKILL.md covers Naming, Files to touch, Consuming the flag and When the feature ships, plus 1 more section
Calls npm and curl

What it does

Add Feature Flag is an agent skill from cadence-workflow/cadence-web. Add a new boolean feature flag (dynamic config key) to cadence-web. Use when asked to add, create, or set up a feature flag, config flag, or ENABLED toggle.

Its SKILL.md is about 1.1k 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 Backend & APIs, covering GraphQL. It works with webpack. The repository describes itself as: Web UI for visualizing workflows on Cadence. The licence is Apache-2.0.

When your agent uses it

Set up a feature flag
Tasks that involve GraphQL

Example prompts

“/add-feature-flag”

Workflow steps

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

Resolver — src/config/dynamic/resolvers/.ts
Register — src/config/dynamic/dynamic.config.ts
Zod schema — src/config/dynamic/resolvers/schemas/resolver-schemas.ts
Test fixture — src/utils/config/fixtures/resolved-config-values.ts
Resolver test (only if the resolver has logic)

What it can do on your machine

Read from SKILL.md and the folder at commit 2586761. 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
Shell commands in SKILL.md call:
- npm
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and curl, which can reach the network depending on how they are called.
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

Add Feature Flag loads about 1.1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 302 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:117

AME>=true` under `### Feature flags` in `.env`

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 cadence-workflow/cadence-web at commit 2586761, republished under its Apache-2.0 licence (© cadence-workflow). 302 words, ~1,084 tokens.

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

name: add-feature-flag
description: Add a new boolean feature flag (dynamic config key) to cadence-web. Use when asked to add, create, or set up a feature flag, config flag, or `*_ENABLED` toggle.

Add a feature flag

Feature flags are dynamic config entries whose resolver returns boolean. Completeness is enforced by TypeScript — the fixture and the Zod schema map are typed against dynamicConfigs, so a missing entry fails npm run typecheck.

Reference example: WORKFLOW_DIAGNOSTICS_ENABLED (added in the same 4 files below).

Naming

Key: UPPER_SNAKE_CASE, ending in _ENABLED — e.g. WORKFLOW_DIAGNOSTICS_ENABLED
Env var: CADENCE_ + key — e.g. CADENCE_WORKFLOW_DIAGNOSTICS_ENABLED
Resolver file: kebab-case of the key — e.g. workflow-diagnostics-enabled.ts
Resolver function: camelCase of the key — e.g. workflowDiagnosticsEnabled

Files to touch

Add the new entry directly after a related existing flag in each file (not alphabetically).

1. Resolver — `src/config/dynamic/resolvers/<flag-name>.ts`

/**
 * Returns whether <feature> is enabled.
 *
 * To enable, set the CADENCE_<FLAG_NAME> env variable to `true`.
 * For further customization, override the implementation of this resolver.
 *
 * @returns {Promise<boolean>} Whether <feature> is enabled.
 */
export default async function <flagName>(): Promise<boolean> {
  return process.env.CADENCE_<FLAG_NAME> === 'true';
}

Default export, async, returns Promise<boolean>.
Off by default; forks override the resolver.
If the flag depends on another flag, import and call that resolver rather than re-reading its env var (see workflow-diagnostics-in-history-enabled.ts). Check the cheap env var first.
If the flag needs args (e.g. { cluster, domain }), add <flag-name>.types.ts with a <FlagName>ResolverParams type (see cron-list-enabled.types.ts).

2. Register — `src/config/dynamic/dynamic.config.ts`

Three edits:

// import (alphabetical by file path)
import <flagName> from './resolvers/<flag-name>';

// type block
<FLAG_NAME>: ConfigAsyncResolverDefinition<undefined, boolean, 'request', true>;

// runtime block
<FLAG_NAME>: {
  resolver: <flagName>,
  evaluateOn: 'request',
  isPublic: true,
},

Replace undefined with the args type if the resolver takes args. isPublic: true is what exposes the key to the client via /api/config.

3. Zod schema — `src/config/dynamic/resolvers/schemas/resolver-schemas.ts`

<FLAG_NAME>: {
  args: z.undefined(), // or z.object({ cluster: z.string(), domain: z.string() })
  returnType: z.boolean(),
},

4. Test fixture — `src/utils/config/fixtures/resolved-config-values.ts`

<FLAG_NAME>: false,

The getConfigValue auto-mock reads from this, so server-side tests see the new key automatically.

5. Resolver test (only if the resolver has logic)

Skip for a plain env-var check. If the resolver combines conditions, calls another resolver, or takes args, add src/config/dynamic/resolvers/__tests__/<flag-name>.node.ts. Mirror batch-actions-ui-enabled.node.ts: jest.mock the imported resolvers, save/restore the env var in beforeEach/afterEach.

Consuming the flag

Client:

const { data: isEnabled } = useSuspenseConfigValue('<FLAG_NAME>');
// or non-suspense: useConfigValue('<FLAG_NAME>', args?)

Server (route handlers): await getConfigValue('<FLAG_NAME>').

Client tests mock the endpoint:

render(<Component />, {
  endpointsMocks: [
    {
      path: '/api/config',
      httpMethod: 'GET',
      mockOnce: false,
      httpResolver: async () => HttpResponse.json(true),
    },
  ],
});

When the feature ships

Once the UI lands:

Add a row to the Feature flags table in README.md
Add a commented # CADENCE_<FLAG_NAME>=true under ### Feature flags in .env

Verify

bash

npm run typecheck                                  # proves fixture + schema are complete
npm run test:unit:node <flag-name>.node.ts         # if you added a resolver test
npm run test:unit:node -- src/route-handlers/get-config src/utils/config src/config/dynamic
npm run lint

Optional live check: npm run dev, then curl 'http://localhost:8088/api/config?configKey=<FLAG_NAME>' → false; rerun with CADENCE_<FLAG_NAME>=true npm run dev → true.

Files

Just SKILL.md in .agents/skills/add-feature-flag of cadence-workflow/cadence-web.

Open the folder on GitHubat commit 2586761

Compare with similar skills

Add Feature Flag 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.

Add Feature Flag compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Add Feature Flag this skillcadence-workflow/cadence-web	436	—	~1.1k	Automated safety check: Notes	Apache-2.0	yesterday
Nodejs Backend Patternsever-works/ever-works	162	18 repos	~4k	Automated safety check: Pass	AGPL-3.0	today
API DesignerJeffallan/claude-skills	12k	1 repos	~2k	Automated safety check: Pass	MIT	6 days ago
GraphQL Operations with CodegenChrisWiles/claude-code-showcase	6.1k	3 repos	~1.5k	Automated safety check: Pass	None	9 mo ago
Supabasecurvenote/curvenote	170	5 repos	~2.2k	Automated safety check: Pass	Custom licence	11 days ago
API Design Principlesjh941213/my-cc-harness	126	18 repos	~3.4k	Automated safety check: Pass	None	2 mo ago

Similar skills

Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
162 GitHub starsUsed in 18 repos~4k tokens
Backend & APIsAuto-check passed
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
12k GitHub starsUsed in 1 repo~2k tokens
Backend & APIsAuto-check passed
GraphQL Operations with Codegen
ChrisWiles/claude-code-showcase
Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.
6.1k GitHub starsUsed in 3 repos~1.5k tokens
Backend & APIsAuto-check passed
Supabase
curvenote/curvenote
A skill your agent uses when doing ANY task involving Supabase.
170 GitHub starsUsed in 5 repos~2.2k tokens
Backend & APIsAuto-check passed
API Design Principles
jh941213/my-cc-harness
REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.
126 GitHub starsUsed in 18 repos~3.4k tokens
Backend & APIsAuto-check passed
API And Interface Design
dzhalaevd/Donatello
Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.
135 GitHub starsUsed in 8 repos~2.6k tokens
Backend & APIsAuto-check passed

Questions about Add Feature Flag

What does Add Feature Flag do?

Add a new boolean feature flag (dynamic config key) to cadence-web. Add Feature Flag is an agent skill from cadence-workflow/cadence-web. Add a new boolean feature flag (dynamic config key) to cadence-web.

When should I use Add Feature Flag?

Add Feature Flag fits situations like: set up a feature flag; tasks that involve GraphQL.

How do I install Add Feature Flag in Claude Code?

Run `npx skills add cadence-workflow/cadence-web --skill add-feature-flag -a claude-code`. Or copy the skill folder (.agents/skills/add-feature-flag in cadence-workflow/cadence-web) into .claude/skills/add-feature-flag in your project. Claude Code loads it when a task matches its description.

How do I install Add Feature Flag in Codex?

Run `npx skills add cadence-workflow/cadence-web --skill add-feature-flag -a codex`. Or copy the skill folder (.agents/skills/add-feature-flag in cadence-workflow/cadence-web) into .agents/skills/add-feature-flag in your project. Codex loads it when a task matches its description.

Can I use Add Feature Flag 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 cadence-workflow/cadence-web --skill add-feature-flag -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-feature-flag, .gemini/skills/add-feature-flag, .github/skills/add-feature-flag and .opencode/skills/add-feature-flag in your project.

What does Add Feature Flag need to run?

Going by SKILL.md and its folder, Add Feature Flag needs the command-line tools its instructions call (npm and curl).

Does Add Feature Flag access the network?

SKILL.md contains no URLs. Its commands use npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Feature Flag safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Add Feature Flag use?

Add Feature Flag 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 Add Feature Flag use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Add Feature Flag?

Skills that share tags, products or a category with Add Feature Flag: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars) and Supabase (curvenote/curvenote, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Feature Flag?

cadence-workflow (a GitHub organization) maintains it in cadence-workflow/cadence-web, which has 436 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.

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

Add Feature Flag

Install Add Feature Flag

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Add a feature flag

Naming

Files to touch

1. Resolver — `src/config/dynamic/resolvers/<flag-name>.ts`

2. Register — `src/config/dynamic/dynamic.config.ts`

3. Zod schema — `src/config/dynamic/resolvers/schemas/resolver-schemas.ts`

4. Test fixture — `src/utils/config/fixtures/resolved-config-values.ts`

5. Resolver test (only if the resolver has logic)

Consuming the flag

When the feature ships

Verify

Files

Compare with similar skills

Similar skills

Nodejs Backend Patterns

API Designer

GraphQL Operations with Codegen

Supabase

API Design Principles

API And Interface Design

More from cadence-workflow/cadence-web

React Joyride

Questions about Add Feature Flag

Install Add Feature Flag

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Add a feature flag

Naming

Files to touch

1. Resolver — src/config/dynamic/resolvers/<flag-name>.ts

2. Register — src/config/dynamic/dynamic.config.ts

3. Zod schema — src/config/dynamic/resolvers/schemas/resolver-schemas.ts

4. Test fixture — src/utils/config/__fixtures__/resolved-config-values.ts

5. Resolver test (only if the resolver has logic)

Consuming the flag

When the feature ships

Verify

Files

Compare with similar skills

Similar skills

Nodejs Backend Patterns

API Designer

GraphQL Operations with Codegen

Supabase

API Design Principles

API And Interface Design

More from cadence-workflow/cadence-web

React Joyride

Related

Questions about Add Feature Flag

1. Resolver — `src/config/dynamic/resolvers/<flag-name>.ts`

2. Register — `src/config/dynamic/dynamic.config.ts`

3. Zod schema — `src/config/dynamic/resolvers/schemas/resolver-schemas.ts`

4. Test fixture — `src/utils/config/fixtures/resolved-config-values.ts`