Agent skill

Add SQL Microservice

by microbus-io in microbus-io/fabric

TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

Apache-2.0Auto-check passedBackend & APIs

Install Add SQL Microservice

skills CLI
$ npx skills add microbus-io/fabric --skill add-sql-microservice -a claude-code

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

GitHub CLI
$ gh skill install microbus-io/fabric add-sql-microservice --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/add-sql-microservice .claude/skills/add-sql-microservice && 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/

Facts

Skill name
add-sql-microservice
GitHub stars
172
Token cost
~2k tokens
SKILL.md length
965 words
Files
13
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

  • Works in 9 steps: Determine the Noun and Hostname → Create a Directory Structure for the New… → Copy Template Files → …
  • User asks to create a CRUD microservice
  • Runs Go scripts from its folder; calls go
  • Database-backed service

What it does

Add SQL Microservice is an agent skill from microbus-io/fabric. TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files (for example `busstop/CLAUDE.md` and `busstop/PROMPTS.md`).

It sits in Backend & APIs, covering Microservices and SQL. It works with SQL, Microsoft SQL Server, MySQL and PostgreSQL. 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 create a CRUD microservice
  • Database-backed service
  • A service to persist/store objects in SQL (MySQL

Example prompts

  • “/add-sql-microservice”

Workflow steps

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

  1. Determine the Noun and Hostname
  2. Create a Directory Structure for the New Microservice
  3. Copy Template Files
  4. Find and Replace
  5. Generate the Boilerplate
  6. Add to Main App
  7. Add to Config File
  8. Housekeeping
  9. Propose Object Fields

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

    Ships script files (Go), which the agent can run.

    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

Add SQL Microservice loads about 2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 965 words of instructions outside code blocks.

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

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). 965 words, ~1,996 tokens.

Download SKILL.mdSave it as .claude/skills/add-sql-microservice/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
add-sql-microservice
description
TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

CRITICAL: 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.

IMPORTANT: Do not remove the Example field or code related to it from the code since it is required by various tests.

IMPORTANT: Read .claude/rules/sequel.txt for SQL CRUD conventions before proceeding.

CRITICAL: The busstop template ships only the hand-written source files - mynounapi/definition.go (the API spec), the domain types, service.go, the tests, and resources/. After the copy, cmd/genservice produces the boilerplate (Step 5).

Workflow

Copy this checklist and track your progress:

Creating a new microservice:
- [ ] Step 1: Determine the Noun and Hostname
- [ ] Step 2: Create a Directory Structure for the New Microservice
- [ ] Step 3: Copy Template Files
- [ ] Step 4: Find and Replace
- [ ] Step 5: Generate the Boilerplate
- [ ] Step 6: Add to Main App
- [ ] Step 7: Add to config file
- [ ] Step 8: Housekeeping
- [ ] Step 9: Propose Object Fields
Step 1: Determine the Noun and Hostname

Determine the singular noun representing the object being persisted, for example, "User", "Notebook", "Sales Order", etc. In subsequent steps, mynoun is used as a placeholder for the lowercase form of this noun with spaces removed (e.g. user, notebook, salesorder).

Determine the hostname by following the name-microservice skill (e.g. mynoun.path.some.myproject). A CRUD store's leading segment is normally the object noun, and may fold in crud when the microservice is dedicated purely to persistence (e.g. orderscrud).

Step 2: Create a Directory Structure for the New Microservice

Each microservice must be placed in a separate directory. Create a new directory for the new microservice. For the directory name, use mynoun with only lowercase letters a through z, for example, user, notebook or salesorder.

In smaller projects, place the new directory under the root directory of the project. In larger projects, consider using a nested directory structure to group similar microservices together.

shell
mkdir -p mynoun
Step 3: Copy Template Files

The .claude/skills/sequel/add-sql-microservice/busstop directory contains the canonical implementation code for the noun BusStop. Use cp or a similar tool to copy verbatim the content of the busstop template directory to the microservice's directory mynoun. Do not read the files.

The directory structure should look like this.

myproject/
└── mynoun/
    ├── busstopapi/
    └── resources/

IMPORTANT: File names in the following steps are relative to the new microservice directory mynoun, unless indicated otherwise.

Rename the directory busstopapi to mynounapi.

The directory structure should look like this.

myproject/
└── mynoun/
    ├── mynounapi/
    └── resources/
Step 4: Find and Replace

CRITICAL: This step must be scoped to the microservice directory only. Do not perform it on the project root.

Use sed or a similar tool to perform the following case-sensitive find-and-replace operations on ALL files in the microservice directory. Do not read the files.

Perform these replacements in order:

  1. Replace github.com/microbus-io/fabric/busstop with the package path of this microservice, e.g. github.com/mycompany/myproject/mynoun
  2. Replace busstopapi with the name of the API directory mynounapi
  3. Replace busstop.hostname with the hostname of this microservice
  4. Replace BusStop with the singular noun of this microservice in PascalCase, i.e. MyNoun
  5. Replace bus stops with the plural noun of this microservice in lower case (with spaces between words), i.e. my nouns
  6. Replace bus stop with the singular noun of this microservice in lower case (with spaces between words), i.e. my noun
  7. Replace busstop with the singular noun of this microservice in lowercase (no spaces between words), i.e. mynoun
  8. Replace bus_stop with the singular noun of this microservice in snake_case, i.e. my_noun
  9. Replace bus-stop with the singular noun of this microservice in kebab-case, i.e. my-noun
  10. Replace _CIPHER_KEY_____________________ with a unique 32-character random base64 string (characters A-Z, a-z, 0-9, +, /)
  11. Replace _CIPHER_NONCE___________________ with a 32-character random base64 string (characters A-Z, a-z, 0-9, +, /)
  12. Replace _SEQUENCE_ with an 8-character random hexadecimal string

IMPORTANT: The cipher key and nonce are base64 and may contain the / character, so a sed substitution using the default / delimiter (s/old/new/) can break. Use an alternate delimiter that cannot appear in base64, e.g. sed 's|_CIPHER_KEY_____________________|...|g', or apply those two replacements with a tool that takes the replacement as a literal argument rather than parsing it.

Run go fmt on the microservice directory to reformat the Go source files.

Show full SKILL.md (321 more words)Show less
Step 5: Generate the Boilerplate

From the new microservice's directory, run the generator. It reads mynounapi/definition.go and writes mynounapi/client.go, intermediate.go, mock.go, mock_test.go, and manifest.yaml.

shell
go run github.com/microbus-io/fabric/cmd/genservice .

Then, from the project root, bring the module's dependencies up to date and verify the microservice compiles:

shell
go mod tidy
go vet ./...

Run go mod tidy first: a SQL CRUD microservice pulls the sequel package and the database drivers, which may not yet be in go.sum, which makes go vet fail with missing go.sum entry until the module is tidied.

Step 6: Add to Main App

Find main/main.go relative to the project root. Add the new microservice to the app in the main function. Add the appropriate import statement at the top of the file.

go
import (
	// ...
	"github.com/mycompany/myproject/mynoun"
)

func main() {
	// ...
	app.Add(
		// HINT: Add solution microservices here
		mynoun.NewService(),
	)
	// ...
}
Step 7: Add to Config File

Look for config.local.yaml at the root of the project. If the file does not exist, create it.

If a value already exists for SQLDataSourceName under all in config.local.yaml, skip the remainder of this step.

Add the data source name secrets under all.

yaml
all:
  # SQLDataSourceName: root:root@tcp(127.0.0.1:3306)/microbus
  # SQLDataSourceName: postgres://postgres:postgres@127.0.0.1:5432/microbus
  # SQLDataSourceName: sqlserver://sa:Password123@127.0.0.1:1433?database=microbus
Step 8: Housekeeping

Follow the housekeeping skill.

Step 9: Propose Object Fields

Ask the user if they'd like you to propose a design for the microservice. If the user declines, skip the remainder of this step.

Use any of the context provided by the user and propose a list of fields that the object should include, with the following properties. You may engage the user and ask for additional information if needed.

  • Name
  • Description
  • Go data type, e.g. string, int, time.Time, etc.
  • Validation rules such as whether or not the field is required, maximum length (if string), acceptable range (if numeric), etc.
  • Whether or not it is a unique identifier of the object

Do not recommend CreatedAt or UpdatedAt timestamp fields. These are already built-in.

Save the proposed design to DESIGN.md, then show it to the user. Ask the user if they'd like you to implement any of the proprosals. Do not implement without explicit approval from the user.

© microbus-io, 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 12 other files in .claude/skills/sequel/add-sql-microservice of microbus-io/fabric.

  • SKILL.md
  • busstop/CLAUDE.md
  • busstop/PROMPTS.md
  • busstop/busstopapi/definition.go
  • busstop/busstopapi/object.go
  • busstop/busstopapi/object_test.go
  • busstop/busstopapi/objectkey.go
  • busstop/busstopapi/query.go
  • busstop/busstopapi/query_test.go
  • busstop/resources/embed.go
  • busstop/resources/sql/1.sql
  • busstop/service.go
  • busstop/service_test.go

Open the folder on GitHubat commit fb98098

Compare with similar skills

Add SQL Microservice 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 SQL Microservice compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add SQL Microservice this skillmicrobus-io/fabric172—~2kAutomated safety check: PassApache-2.0
Database Migrations SQL Migrationsrmyndharis/antigravity-skills1.7k2 repos~577Automated safety check: NotesMIT
SQL ProJeffallan/claude-skills12k—~1.3kAutomated safety check: PassMIT
SQL Optimizationgithub/awesome-copilot40k2 repos~2.3kAutomated safety check: PassMIT
SQL Code Reviewgithub/awesome-copilot40k1 repos~2.2kAutomated safety check: PassMIT
Cloud SQL Basicsgoogle/skills21k—~973Automated safety check: PassApache-2.0

Similar skills

  • Database Migrations SQL Migrations

    rmyndharis/antigravity-skills

    SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server

    1.7k GitHub starsUsed in 2 repos~577 tokens
    DatabasesAuto-check: notes
  • SQL Pro

    Jeffallan/claude-skills

    Optimizes SQL queries and designs schemas using CTEs, window functions, covering indexes and EXPLAIN ANALYZE, with notes on dialect differences between major databases.

    12k GitHub stars~1.3k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • SQL Optimization

    github/awesome-copilot

    Official

    Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server…

    40k GitHub starsUsed in 2 repos~2.3k tokens
    DatabasesAuto-check passed
  • SQL Code Review

    github/awesome-copilot

    Official

    Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle).

    40k GitHub starsUsed in 1 repo~2.2k tokens
    DatabasesAuto-check passed
  • Cloud SQL Basics

    google/skills

    Official

    This file generates or explains Cloud SQL resources. An agent skill from google/skills.

    21k GitHub stars~973 tokensUpdated today
    DatabasesAuto-check passed
  • Optimizing SQL

    ancoleman/ai-design-components

    Optimize SQL query performance through EXPLAIN analysis, indexing strategies, and query rewriting for PostgreSQL, MySQL, and SQL Server.

    526 GitHub stars~3k tokensUpdated 10 mo ago
    DatabasesAuto-check passed

More from microbus-io/fabric

All 33 skills in this repo
  • Add Config

    microbus-io/fabric

    TRIGGER when user asks to add or modify a configuration property or setting, or to make a value configurable.

    172 GitHub stars~2.3k tokensUpdated 9 days ago
    Auto-check passed
  • Add Function

    microbus-io/fabric

    TRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC, or a route that accepts typed arguments and returns typed results.

    172 GitHub stars~2.4k tokensUpdated 9 days ago
    Auto-check passed
  • Add Inbound Event

    microbus-io/fabric

    TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.

    172 GitHub stars~1.4k tokensUpdated 9 days ago
    Auto-check passed
  • Add Metric

    microbus-io/fabric

    TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.

    172 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check passed
  • Add Outbound Event

    microbus-io/fabric

    TRIGGER when user asks to fire, emit, or publish an event that other microservices can subscribe to.

    172 GitHub stars~1.7k tokensUpdated 9 days ago
    Auto-check passed
  • Add Python Function

    microbus-io/fabric

    TRIGGER when user asks to add a Python-backed function endpoint to an existing Python-backed microservice.

    172 GitHub stars~1.3k tokensUpdated 9 days ago
    Auto-check passed

Categories

Questions about Add SQL Microservice

What does Add SQL Microservice do?

TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL). Add SQL Microservice is an agent skill from microbus-io/fabric. TRIGGER when user asks to create a CRUD microservice, database-backed service, or a service to persist/store objects in SQL (MySQL, Postgres, MSSQL).

When should I use Add SQL Microservice?

Add SQL Microservice fits situations like: user asks to create a CRUD microservice; database-backed service; A service to persist/store objects in SQL (MySQL.

How do I install Add SQL Microservice in Claude Code?

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

How do I install Add SQL Microservice in Codex?

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

Can I use Add SQL Microservice 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 add-sql-microservice -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-sql-microservice, .gemini/skills/add-sql-microservice, .github/skills/add-sql-microservice and .opencode/skills/add-sql-microservice in your project.

What does Add SQL Microservice need to run?

Going by SKILL.md and its folder, Add SQL Microservice needs Go for the scripts in its folder and the command-line tools its instructions call (go).

Does Add SQL Microservice 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 Add SQL Microservice 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 Add SQL Microservice use?

Add SQL Microservice 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 SQL Microservice use?

About 2k tokens (SKILL.md is roughly 8k 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 SQL Microservice?

Skills that share tags, products or a category with Add SQL Microservice: Database Migrations SQL Migrations (rmyndharis/antigravity-skills, 1.7k stars), SQL Pro (Jeffallan/claude-skills, 12k stars), SQL Optimization (github/awesome-copilot, 40k stars) and SQL Code Review (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add SQL Microservice?

microbus-io (a GitHub organization) maintains it in microbus-io/fabric, which has 172 GitHub stars. The repository holds 33 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.