Agent skill

Remove SQL Fields

TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

Apache-2.0Auto-check passedBackend & APIs

Install Remove SQL Fields

skills CLI

$ npx skills add microbus-io/fabric --skill remove-sql-fields -a claude-code

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

GitHub CLI

$ gh skill install microbus-io/fabric remove-sql-fields --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/microbus-io/fabric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .claude/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .claude/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields

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-sql-fields -a codex

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

GitHub CLI

$ gh skill install microbus-io/fabric remove-sql-fields --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .agents/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .agents/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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-sql-fields -a cursor

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

GitHub CLI

$ gh skill install microbus-io/fabric remove-sql-fields --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .cursor/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .cursor/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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/microbus-io/fabric.git --path .claude/skills/sequel/remove-sql-fields

--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-sql-fields -a gemini-cli

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

GitHub CLI

$ gh skill install microbus-io/fabric remove-sql-fields --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/microbus-io/fabric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .gemini/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .gemini/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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 microbus-io/fabric remove-sql-fields

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-sql-fields -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .github/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .github/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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-sql-fields -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 microbus-io/fabric remove-sql-fields --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sequel/remove-sql-fields .opencode/skills/remove-sql-fields && 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 "remove-sql-fields" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/sequel/remove-sql-fields into .opencode/skills/remove-sql-fields/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-sql-fields", 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-sql-fields
GitHub stars: 172
Token cost: ~1.1k tokens
SKILL.md length: 425 words
Files: 1
Skills in repo: 32
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

Works in 8 steps: Read Local CLAUDE.md File → Update the Type Definition of the Object → Update the Type Definition of the Query → …
User asks to remove
Calls go
Columns from a SQL CRUD microservices object

What it does

Remove SQL Fields is an agent skill from microbus-io/fabric. TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

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 SQL and Microservices. It works with SQL. 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
Columns from a SQL CRUD microservices object

Example prompts

“/remove-sql-fields”

Workflow steps

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

Read Local CLAUDE.md File
Update the Type Definition of the Object
Update the Type Definition of the Query
Update Database Schema
Remove Mappings of Column Names to Object Fields
Remove Query Conditions
Update Integration Tests
Housekeeping

What it can do on your machine

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 SQL Fields loads about 1.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 425 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~34
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 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 microbus-io/fabric at commit fb98098, republished under its Apache-2.0 licence (© microbus-io). 425 words, ~1,138 tokens.

Download SKILL.mdSave it as .claude/skills/remove-sql-fields/SKILL.md (or your agent's skills folder).

name: remove-sql-fields
description: TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

CRITICAL: Read and analyze this microservice before starting. Do NOT explore or analyze other microservices unless explicitly instructed to do so. The instructions in this skill are self-contained to this microservice.

IMPORTANT: MyNoun, MyNounKey, mynoun, and mynounapi are placeholders for the actual object, its key, directory, and API package of the microservice.

Workflow

Copy this checklist and track your progress:

Removing fields of the object:
- [ ] Step 1: Read Local CLAUDE.md File
- [ ] Step 2: Update the Type Definition of the Object
- [ ] Step 3: Update the Type Definition of the Query
- [ ] Step 4: Update Database Schema
- [ ] Step 5: Remove Mappings of Column Names to Object Fields
- [ ] Step 6: Remove Query Conditions
- [ ] Step 7: Update Integration Tests
- [ ] Step 8: Housekeeping

Step 1: Read Local `CLAUDE.md` File

Read the local CLAUDE.md file in the microservice's directory. It contains microservice-specific instructions that should take precedence over global instructions.

Step 2: Update the Type Definition of the Object

Find the type definition of the object in mynounapi/object.go. Remove the appropriate fields from the type definition of the struct. Remove the field's dv8 tags and any irrelevant code from the object's Validate method. Clean up any unused imports.

Step 3: Update the Type Definition of the Query

Find the type definition of the query in mynounapi/query.go. Remove the appropriate fields from the type definition of the struct. Remove the field's dv8 tags and any irrelevant code from the query's Validate method. Clean up any unused imports.

Step 4: Update Database Schema

Create a new migration script file in resources/sql with an incremental file name. IMPORTANT: Do not edit an existing migration file.

Refer to the older .sql migration files to identify what if any constraints were associated with the deprecated columns. Use ALTER TABLE statements to drop these constraints, if applicable.

sql

-- DRIVER: mysql
ALTER TABLE my_table DROP CONSTRAINT my_table_constraint_name;

-- DRIVER: pgx
ALTER TABLE my_table DROP CONSTRAINT my_table_constraint_name;

-- DRIVER: mssql
ALTER TABLE my_table DROP CONSTRAINT my_table_constraint_name;

Refer to the older .sql migration files to identify what if any indices were associated with the deprecated columns. Use DROP INDEX statements to drop these indices, if applicable.

sql

-- DRIVER: mysql
DROP INDEX my_table_idx_deprecated_field ON my_table;

-- DRIVER: pgx
DROP INDEX my_table_idx_deprecated_field;

-- DRIVER: mssql
DROP INDEX my_table_idx_deprecated_field ON my_table;

Append ALTER TABLE statements to drop the columns.

sql

-- DRIVER: mysql
ALTER TABLE my_table
	DROP COLUMN deprecated_field,
	DROP COLUMN unused_field;

-- DRIVER: pgx
ALTER TABLE my_table
	DROP COLUMN deprecated_field,
	DROP COLUMN unused_field;

-- DRIVER: mssql
ALTER TABLE my_table DROP COLUMN
	deprecated_field,
	unused_field;

-- DRIVER: sqlite
ALTER TABLE my_table DROP COLUMN deprecated_field;
-- DRIVER: sqlite
ALTER TABLE my_table DROP COLUMN unused_field;

IMPORTANT: SQLite only supports dropping one column per ALTER TABLE statement. Each column must be a separate statement prefixed with -- DRIVER: sqlite.

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

Step 5: Remove Mappings of Column Names to Object Fields

Update the mappings of the database column names to their corresponding object fields in mapColumnsOnInsert, mapColumnsOnUpdate and mapColumnsOnSelect in service.go. Remove mappings of deprecated columns to deprecated object fields.

Step 6: Remove Query Conditions

Remove the query conditions and searchable columns in prepareWhereClauses in service.go that correspond to the removed fields or columns.

Step 7: Update Integration Tests

Remove references to the deprecated fields in service_test.go, including in the NewObject constructor and TestMyNoun_ColumnMappings.

Remove references to the deprecated fields in mynounapi/object_test.go and mynounapi/query_test.go.

Step 8: Housekeeping

Follow the housekeeping skill. Removing fields changes only the hand-written domain code (object.go, query.go, service.go, resources/sql), not definition.go, so the boilerplate regeneration is a no-op; the Version bump and go vet still apply.

Files

Just SKILL.md in .claude/skills/sequel/remove-sql-fields of microbus-io/fabric.

Open the folder on GitHubat commit fb98098

Compare with similar skills

Remove SQL Fields 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.

Remove SQL Fields compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Remove SQL Fields this skillmicrobus-io/fabric	172	—	~1.1k	Automated safety check: Pass	Apache-2.0	10 days ago
Google BigqueryLeoYeAI/openclaw-master-skills	2.2k	—	~4.1k	Automated safety check: Pass	MIT	2 mo ago
Debug Using Debugbarhexlet-volunteers/hexlet-sicp	114	1 repos	~1.5k	Automated safety check: Pass	AGPL-3.0	3 days ago
Databricksrocky-data/rocky	304	—	~2k	Automated safety check: Pass	Apache-2.0	today
Datajunction QueryDataJunction/dj	161	—	~2k	Automated safety check: Pass	MIT	today
Aurora Dsqlaws/agent-toolkit-for-aws	2.8k	—	~9.6k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Google Bigquery
LeoYeAI/openclaw-master-skills
Google BigQuery API integration with managed OAuth. An agent skill from LeoYeAI/openclaw-master-skills.
2.2k GitHub stars~4.1k tokensUpdated 2 mo ago
Backend & APIsAuto-check passed
Debug Using Debugbar
hexlet-volunteers/hexlet-sicp
Inspect what a Laravel request actually did — queries, exceptions, timing, cache, auth, views — by reading the profiling data Laravel Debugbar already captured, via Artisan commands.
114 GitHub starsUsed in 1 repo~1.5k tokens
Backend & APIsAuto-check passed
Databricks
rocky-data/rocky
Databricks REST API and SQL reference for Rocky's warehouse adapter.
304 GitHub stars~2k tokensUpdated today
Backend & APIsAuto-check passed
Datajunction Query
DataJunction/dj
Activate this skill for querying DataJunction (DJ) — finding nodes, generating SQL, fetching metric data, exploring lineage, visualizing results — via the DJ UI, MCP tools, or REST/GraphQL APIs.
161 GitHub stars~2k tokensUpdated today
Backend & APIsAuto-check passed
Aurora Dsql
aws/agent-toolkit-for-aws
Official
Provisions and manages Aurora DSQL clusters, connects via psql or DSQL Connectors, manages schemas, runs queries, migrates from MySQL, diagnoses query plans, and develops apps on serverless…
2.8k GitHub stars~9.6k tokensUpdated today
Backend & APIsAuto-check passed
Pp Jobber
mvanhorn/printing-press-library
Read-only Jobber CLI for offline analysis — every GraphQL surface synced to SQLite, every relationship queryable.
2.1k GitHub stars~3k tokensUpdated yesterday
Backend & APIsAuto-check: notes

Questions about Remove SQL Fields

What does Remove SQL Fields do?

TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object. Remove SQL Fields is an agent skill from microbus-io/fabric. TRIGGER when user asks to remove, drop, or delete fields, properties, or columns from a SQL CRUD microservice's object.

When should I use Remove SQL Fields?

Remove SQL Fields fits situations like: user asks to remove; columns from a SQL CRUD microservices object.

How do I install Remove SQL Fields in Claude Code?

Run `npx skills add microbus-io/fabric --skill remove-sql-fields -a claude-code`. Or copy the skill folder (.claude/skills/sequel/remove-sql-fields in microbus-io/fabric) into .claude/skills/remove-sql-fields in your project. Claude Code loads it when a task matches its description.

How do I install Remove SQL Fields in Codex?

Run `npx skills add microbus-io/fabric --skill remove-sql-fields -a codex`. Or copy the skill folder (.claude/skills/sequel/remove-sql-fields in microbus-io/fabric) into .agents/skills/remove-sql-fields in your project. Codex loads it when a task matches its description.

Can I use Remove SQL Fields 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-sql-fields -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-sql-fields, .gemini/skills/remove-sql-fields, .github/skills/remove-sql-fields and .opencode/skills/remove-sql-fields in your project.

What does Remove SQL Fields need to run?

Going by SKILL.md and its folder, Remove SQL Fields needs the command-line tools its instructions call (go).

Does Remove SQL Fields 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 SQL Fields 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 SQL Fields use?

Remove SQL Fields 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 SQL Fields use?

About 1.1k tokens (SKILL.md is roughly 4.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 Remove SQL Fields?

Skills that share tags, products or a category with Remove SQL Fields: Google Bigquery (LeoYeAI/openclaw-master-skills, 2.2k stars), Debug Using Debugbar (hexlet-volunteers/hexlet-sicp, 114 stars), Databricks (rocky-data/rocky, 304 stars) and Datajunction Query (DataJunction/dj, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Remove SQL Fields?

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.

Install Remove SQL Fields

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

Workflow

Step 1: Read Local CLAUDE.md File

Step 2: Update the Type Definition of the Object

Step 3: Update the Type Definition of the Query

Step 4: Update Database Schema

Step 5: Remove Mappings of Column Names to Object Fields

Step 6: Remove Query Conditions

Step 7: Update Integration Tests

Step 8: Housekeeping

Files

Compare with similar skills

Similar skills

More from microbus-io/fabric

Related

Questions about Remove SQL Fields

Step 1: Read Local `CLAUDE.md` File