Release A2a
a2aproject/a2a-java
Guide maintainers through the multi-step release process — version bump, CI verification, tagging, Maven Central deployment, SNAPSHOT bump, and versioned documentation.
A skill your agent uses when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts…
Install 057 Design Feature Toggles
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 057-design-feature-toggles --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/057-design-feature-toggles .claude/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.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/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .claude/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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 install https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-togglesType 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.
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 057-design-feature-toggles --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/057-design-feature-toggles .agents/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .agents/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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.
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 057-design-feature-toggles --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/057-design-feature-toggles .cursor/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .cursor/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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 https://github.com/jabrena/plinth.git --path skills/057-design-feature-toggles--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 057-design-feature-toggles --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/057-design-feature-toggles .gemini/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.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/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .gemini/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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.
$ gh skill install jabrena/plinth 057-design-feature-togglesInstalls 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).
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/057-design-feature-toggles .github/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.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/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .github/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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.
$ npx skills add jabrena/plinth --skill 057-design-feature-toggles -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 057-design-feature-toggles --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/057-design-feature-toggles .opencode/skills/057-design-feature-toggles && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "057-design-feature-toggles" agent skill from https://github.com/jabrena/plinth/tree/main/skills/057-design-feature-toggles into .opencode/skills/057-design-feature-toggles/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "057-design-feature-toggles", 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
057-design-feature-toggles- GitHub stars
- 447
- Token cost
- ~1.1k tokens
- SKILL.md length
- 485 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts…
- Cleaning up feature toggles
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Runtime configuration gates
What it does
057 Design Feature Toggles is an agent skill from jabrena/plinth. Use when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts, experiments, or temporary compatibility switches in Java enterprise systems. This should trigger for requests such as Design a feature toggle strategy; Review this feature flag; Add a kill switch safely; Test toggle on and off paths; Clean up an expired feature toggle; Plan controlled rollout and rollback behavior. Part of Plinth Toolkit
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/057-design-feature-toggles.md`).
It sits in DevOps & Cloud, covering Deployment. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- Cleaning up feature toggles
- Runtime configuration gates
- Canary controls
- Staged rollouts
Example prompts
- “/057-design-feature-toggles”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. 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.
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
057 Design Feature Toggles loads about 1.1k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 485 words of instructions outside code blocks.
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 jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 485 words, ~1,132 tokens.
Download SKILL.mdSave it as
.claude/skills/057-design-feature-toggles/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 057-design-feature-toggles
- description
- Use when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts, experiments, or temporary compatibility switches in Java enterprise systems. This should trigger for requests such as Design a feature toggle strategy; Review this feature flag; Add a kill switch safely; Test toggle on and off paths; Clean up an expired feature toggle; Plan controlled rollout and rollback behavior. Part of Plinth Toolkit
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral, Sangwon Park
- metadata.version
- 0.19.0
Feature Toggles Design
Guide Java Enterprise developers through safe feature toggle design and lifecycle management. This is an interactive SKILL.
What is covered in this Skill?
- Deciding when a feature toggle is appropriate versus a branch, configuration change, deployment change, or parallel change
- Classifying release toggles, operational kill switches, experiment toggles, permission toggles, and migration toggles
- Designing typed toggle ownership, defaults, evaluation scope, fallback behavior, observability, and rollback controls
- Implementing toggles in Java services without scattering flag checks or creating hidden long-term complexity
- Reviewing toggles for release, rollback, security, privacy, concurrency, and maintenance risk
- Testing both enabled and disabled paths, configuration failure behavior, rollout rules, and cleanup readiness
Constraints
Use feature toggles as explicit, owned runtime control points rather than hidden conditional complexity.
- MUST read
references/057-design-feature-toggles.mdbefore applying feature toggle guidance - MUST classify the toggle type, owner, expected lifetime, default state, rollout audience, and removal trigger before recommending implementation
- MUST design safe defaults, fallback behavior, observability, and rollback behavior for runtime evaluation failures
- MUST keep toggle evaluation centralized, typed, and testable instead of scattering raw configuration lookups through business logic
- MUST include cleanup expectations for temporary toggles before implementation is considered complete
- MUST NOT use feature toggles to hide incomplete design decisions, weaken security controls, or leave permanent branches without explicit ownership
When to use this skill
- Design a feature toggle strategy
- Review this feature flag implementation
- Add a kill switch safely
- Plan a canary or staged rollout in a Java service
- Test toggle on and off paths
- Clean up an expired feature toggle
- Decide whether this runtime behavior change needs a toggle
Show full SKILL.md (222 more words)Show less
Workflow
- Classify the Toggle Need
Read references/057-design-feature-toggles.md, then identify the runtime behavior change, rollout risk, rollback expectation, affected users, operational owner, and whether a feature toggle is the smallest safe control mechanism.
- Design the Toggle Contract
Define the toggle type, stable name, typed decision API, default state, evaluation context, fallback behavior, audit needs, metrics, logs, and cleanup trigger. Prefer one decision point per behavior over repeated raw flag checks.
- Plan Implementation Boundaries
Place toggle evaluation near an application service, adapter, strategy selector, or request boundary. Keep domain code explicit, avoid secret or personal data in rules, and preserve consistent decisions across a request, transaction, message, or batch item.
- Review Release and Rollback Safety
Check whether disabled behavior preserves the current production contract, enabled behavior has rollout guardrails, operational teams can disable the behavior quickly, and cleanup will not break old deployments, data, or integrations.
- Test and Observe Both Paths
Test disabled, enabled, fallback, configuration failure, rollout targeting, and cleanup scenarios. Add metrics, logs, alerts, or dashboards that show toggle state, decision volume, error rate, latency impact, and kill-switch activation.
- Report the Toggle Plan
Report the decision, toggle contract, implementation boundary, test matrix, observability plan, rollout and rollback steps, cleanup owner, removal trigger, skipped checks, and remaining risks.
Reference
For detailed guidance, examples, and constraints, see references/057-design-feature-toggles.md.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/057-design-feature-toggles of jabrena/plinth.
- SKILL.md
- references/057-design-feature-toggles.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
057 Design Feature Toggles 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 057 Design Feature Toggles this skilljabrena/plinth | 447 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Release A2aa2aproject/a2a-java | 504 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Oci Functions Deployoracle/skills | 877 | — | ~4.6k | Automated safety check: Pass | UPL-1.0 | |
| Writing Extension Devuiquarkusio/quarkus | 16k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Azure Sre AgentMicrosoftDocs/Agent-Skills | 776 | — | ~2.7k | Automated safety check: Pass | CC-BY-4.0 | |
| TrueLicense Maven Central Releasechristian-schlichtherle/truelicense | 399 | — | ~846 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Oci Functions Deploy
oracle/skills
Build, configure, scaffold, and deploy OCI Functions from a local machine using a dependency-first, Fn-context-guided flow with argv-safe mutation execution, nonce-scoped confirmations, and a…
Writing Extension Devui
quarkusio/quarkus
How to add a Dev UI page to a Quarkus extension: deployment processors, runtime-dev JSON-RPC services, and Lit web components.
- Official
Azure Sre Agent
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Sre Agent development including troubleshooting, best practices, decision making, architecture & design patterns, security, configuration, integrations & coding patterns…
TrueLicense Maven Central Release
christian-schlichtherle/truelicense
Documents how TrueLicense is published to Maven Central from a version tag, the plugin constraints behind it and how to rehearse a release locally.
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Works with
Categories
Questions about 057 Design Feature Toggles
What does 057 Design Feature Toggles do?
A skill your agent uses when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts…. 057 Design Feature Toggles is an agent skill from jabrena/plinth. Use when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts, experiments, or temporary compatibility switches in Java enterprise systems.
When should I use 057 Design Feature Toggles?
057 Design Feature Toggles fits situations like: cleaning up feature toggles; runtime configuration gates; canary controls; staged rollouts.
How do I install 057 Design Feature Toggles in Claude Code?
Run `npx skills add jabrena/plinth --skill 057-design-feature-toggles -a claude-code`. Or copy the skill folder (skills/057-design-feature-toggles in jabrena/plinth) into .claude/skills/057-design-feature-toggles in your project. Claude Code loads it when a task matches its description.
How do I install 057 Design Feature Toggles in Codex?
Run `npx skills add jabrena/plinth --skill 057-design-feature-toggles -a codex`. Or copy the skill folder (skills/057-design-feature-toggles in jabrena/plinth) into .agents/skills/057-design-feature-toggles in your project. Codex loads it when a task matches its description.
Can I use 057 Design Feature Toggles 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 jabrena/plinth --skill 057-design-feature-toggles -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/057-design-feature-toggles, .gemini/skills/057-design-feature-toggles, .github/skills/057-design-feature-toggles and .opencode/skills/057-design-feature-toggles in your project.
What does 057 Design Feature Toggles need to run?
SKILL.md names no scripts, command-line tools or credentials: 057 Design Feature Toggles is instructions for the agent only.
Does 057 Design Feature Toggles 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 057 Design Feature Toggles 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 057 Design Feature Toggles use?
057 Design Feature Toggles is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 057 Design Feature Toggles use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.
What are the alternatives to 057 Design Feature Toggles?
Skills that share tags, products or a category with 057 Design Feature Toggles: Release A2a (a2aproject/a2a-java, 504 stars), Oci Functions Deploy (oracle/skills, 877 stars), Writing Extension Devui (quarkusio/quarkus, 16k stars) and Azure Sre Agent (MicrosoftDocs/Agent-Skills, 776 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 057 Design Feature Toggles?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.