Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .claude/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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.
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 microbus-io/fabric --skill remove-feature -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .agents/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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 microbus-io/fabric --skill remove-feature -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .cursor/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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.
--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 microbus-io/fabric --skill remove-feature -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .gemini/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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.
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 microbus-io/fabric --skill remove-feature -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .github/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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 microbus-io/fabric --skill remove-feature -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "remove-feature" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/remove-feature into .opencode/skills/remove-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature", 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
remove-feature
GitHub stars
172
Token cost
~686 tokens
SKILL.md length
290 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0
At a glance
TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice.
Works in 6 steps: Remove the Declaration from definition.go → Remove the Handler from service.go → Remove the Test from service_test.go → …
User asks to remove
Calls go
Drop an endpoint
What it does
Remove Feature is an agent skill from microbus-io/fabric. TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice.
Its SKILL.md is about 690 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 Microservices. The repository describes itself as: Microbus is the only fabric where every agentic workflow runs on a true microservice substrate - giving your workflows security, scale, observability, and prompt-driven authoring. The licence is Apache-2.0.
When your agent uses it
User asks to remove
Drop an endpoint
Event from a microservice
Example prompts
“/remove-feature”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit fb98098. 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:
go
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
Remove Feature loads about 686 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 290 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~33
When it runs· the whole SKILL.md, loaded when a task matches
~686
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.
Download SKILL.mdSave it as .claude/skills/remove-feature/SKILL.md (or your agent's skills folder).
name
remove-feature
description
TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice.
CRITICAL: Read and analyze this microservice before starting. Do NOT explore or analyze other microservices. The instructions in this skill are self-contained to this microservice.
CRITICAL: A feature lives by hand in myserviceapi/definition.go (its define.* var and In/Out structs), service.go (its handler), and service_test.go (its test). Remove it from those, then run cmd/genservice.
Workflow
Copy this checklist and track your progress:
Removing a feature of a microservice:
- [ ] Step 1: Remove the declaration from definition.go
- [ ] Step 2: Remove the handler from service.go
- [ ] Step 3: Remove the test from service_test.go
- [ ] Step 4: Remove unused custom types
- [ ] Step 5: Generate the boilerplate
- [ ] Step 6: Housekeeping
Search for MARKER: FeatureName within the microservice's directory to locate the feature's hand-written code. The markers in the generated files can be ignored - those files are regenerated in Step 5.
Step 1: Remove the Declaration from definition.go
Delete the feature's define.* var (the whole var FeatureName = define.X{ ... } block) and its In/Out struct types from myserviceapi/definition.go. These all carry // MARKER: FeatureName.
Step 2: Remove the Handler from service.go
Delete the feature's handler in service.go (carrying // MARKER: FeatureName):
A function, web, task, inbound event, or ticker has a handler method.
A workflow has a graph builder method.
A callback config has an OnChangedFeatureName method; an observable metric has an OnObserveFeatureName method.
An outbound event, a non-callback config, and a non-observable metric have no handler in service.go; also remove any call sites that trigger the event or record the metric.
Step 3: Remove the Test from service_test.go
Delete the feature's test function (e.g. TestMyService_FeatureName) from service_test.go.
Step 4: Remove Unused Custom Types
If the removed feature used non-primitive custom types defined in the myserviceapi directory, and those types are no longer used elsewhere by the microservice, remove their definitions.
Step 5: Generate the Boilerplate
From the microservice's directory, run the generator. It regenerates client.go, intermediate.go, mock.go, mock_test.go, and manifest.yaml without the removed feature.
shell
go run github.com/microbus-io/fabric/cmd/genservice .
Then verify the microservice compiles with go vet ./... from the project root.
Remove Feature 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.
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…
Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.
TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice. Remove Feature is an agent skill from microbus-io/fabric. TRIGGER when user asks to remove, delete, or drop an endpoint, config, metric, ticker, or event from a microservice.
When should I use Remove Feature?
Remove Feature fits situations like: user asks to remove; drop an endpoint; event from a microservice.
How do I install Remove Feature in Claude Code?
Run `npx skills add microbus-io/fabric --skill remove-feature -a claude-code`. Or copy the skill folder (.claude/skills/microbus/remove-feature in microbus-io/fabric) into .claude/skills/remove-feature in your project. Claude Code loads it when a task matches its description.
How do I install Remove Feature in Codex?
Run `npx skills add microbus-io/fabric --skill remove-feature -a codex`. Or copy the skill folder (.claude/skills/microbus/remove-feature in microbus-io/fabric) into .agents/skills/remove-feature in your project. Codex loads it when a task matches its description.
Can I use Remove Feature 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 microbus-io/fabric --skill remove-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remove-feature, .gemini/skills/remove-feature, .github/skills/remove-feature and .opencode/skills/remove-feature in your project.
What does Remove Feature need to run?
Going by SKILL.md and its folder, Remove Feature needs the command-line tools its instructions call (go).
Does Remove Feature 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 Remove Feature 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 Remove Feature use?
Remove Feature 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 Remove Feature use?
About 686 tokens (SKILL.md is roughly 2.7k 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 Remove Feature?
Skills that share tags, products or a category with Remove Feature: Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Golang Pro (antoniopaya22/go-rest-template, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Remove Feature?
microbus-io (a GitHub organization) maintains it in microbus-io/fabric, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on September 28, 2026.
Source: microbus-io/fabric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.