Agent skill

SQL Portability

Analyse whether a SQL query is portable across database implementations using sqlglot transpilation.

Custom licenceAuto-check passedDatabases

Install SQL Portability

skills CLI

$ npx skills add HL7/sql-on-fhir --skill sql-portability -a claude-code

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

GitHub CLI

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

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 HL7/sql-on-fhir --skill sql-portability -a codex

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

GitHub CLI

$ gh skill install HL7/sql-on-fhir sql-portability --agent codex

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

Manual copy

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

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

GitHub CLI

$ gh skill install HL7/sql-on-fhir sql-portability --agent cursor

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

Manual copy

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

--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 HL7/sql-on-fhir --skill sql-portability -a gemini-cli

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

GitHub CLI

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

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 HL7/sql-on-fhir --skill sql-portability -a github-copilot

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

Manual copy

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

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

Manual copy

$ git clone --depth 1 https://github.com/HL7/sql-on-fhir.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sql-portability .opencode/skills/sql-portability && 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 "sql-portability" agent skill from https://github.com/HL7/sql-on-fhir/tree/main/.claude/skills/sql-portability into .opencode/skills/sql-portability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-portability", 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: sql-portability
GitHub stars: 150
Token cost: ~512 tokens
SKILL.md length: 186 words
Files: 2 (incl. scripts)
Skills in repo: 1
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Analyse whether a SQL query is portable across database implementations using sqlglot transpilation.

Works in 5 steps: Original SQL — show the query as provided. → Source dialect — the dialect used to… → Compatibility matrix — table with… → …
Checking SQL compatibility
SKILL.md covers Running the analysis, Interpreting results and Presenting the report
Runs Python scripts from its folder; calls uv

What it does

SQL Portability is an agent skill from HL7/sql-on-fhir. Analyse whether a SQL query is portable across database implementations using sqlglot transpilation. Use this skill when checking SQL compatibility, cross-database portability, dialect differences, or when reviewing SQL on FHIR ViewDefinition queries for implementation-specific issues. Trigger keywords include "sql portability", "dialect", "cross-database", "transpile", "compatible", "portable SQL", "database compatibility".

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/sql_portability.py`).

It sits in Databases, covering SQL and Clinical and healthcare research. It works with SQL. The repository describes itself as: This project provides the source for the SQL on FHIR Implementation Guide.

When your agent uses it

Checking SQL compatibility
Cross-database portability
Dialect differences
Reviewing SQL on FHIR ViewDefinition queries for implementation-specific issues

Example prompts

“sql portability”
“dialect”
“cross-database”
“/sql-portability”

Requirements

Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Original SQL — show the query as provided.
Source dialect — the dialect used to parse input.
Compatibility matrix — table with columns: Dialect, Status, Notes.
Key findings — summarise which constructs caused modifications or failures, common patterns across dialects, and overall portability…
Recommendations — suggest alternative SQL constructs that would improve portability, where applicable. Focus on changes relevant to SQL on…

What it can do on your machine

Read from SKILL.md and the folder at commit e3e1d3c. 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 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, 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

SQL Portability loads about 512 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 186 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 186 words (~512 tokens).

“Analyse SQL portability by transpiling a query through multiple database dialects using sqlglot.”

— opening of SKILL.md by HL7, Custom licence

name: sql-portability

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (scripts) in .claude/skills/sql-portability of HL7/sql-on-fhir.

SKILL.md
scripts/sql_portability.py

Open the folder on GitHubat commit e3e1d3c

Compare with similar skills

SQL Portability 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.

SQL Portability compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
SQL Portability this skillHL7/sql-on-fhir	150	—	~512	Automated safety check: Pass	Custom licence	2 days ago
Imaging Data CommonsK-Dense-AI/scientific-agent-skills	48k	1 repos	~7.8k	Automated safety check: Pass	MIT	3 days ago
Imaging Data Commonsmajiayu000/claude-skill-registry	666	1 repos	~4.7k	Automated safety check: Pass	MIT	today
Evolving The Data ModelTriliumNext/Trilium	38k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	today
Orchardcore Data MigrationOrchardCMS/OrchardCore	8.2k	—	~1.7k	Automated safety check: Pass	BSD-3-Clause	today
SQL Optimization Patternsynulihao/AgentSkillOS	617	11 repos	~3.3k	Automated safety check: Pass	None	7 mo ago

Similar skills

Imaging Data Commons
K-Dense-AI/scientific-agent-skills
Queries and downloads public cancer imaging data from NCI Imaging Data Commons.
48k GitHub starsUsed in 1 repo~7.8k tokens
DatabasesAuto-check passed
Imaging Data Commons
majiayu000/claude-skill-registry
Query and download NCI Imaging Data Commons (IDC) cancer radiology and pathology datasets via the idc-index Python client.
666 GitHub starsUsed in 1 repo~4.7k tokens
DatabasesAuto-check passed
Evolving The Data Model
TriliumNext/Trilium
A skill your agent uses when adding a DB migration or a new column/field to a Becca entity in Trilium ("add a migration", "new column on notes/attributes", "ALTER TABLE", "add a field to…
38k GitHub stars~2.1k tokensUpdated today
DatabasesAuto-check passed
Orchardcore Data Migration
OrchardCMS/OrchardCore
Creates and updates OrchardCore data migrations (DataMigration classes with CreateAsync/UpdateFromX).
8.2k GitHub stars~1.7k tokensUpdated today
DatabasesAuto-check passed
SQL Optimization Patterns
ynulihao/AgentSkillOS
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries.
617 GitHub starsUsed in 11 repos~3.3k tokens
DatabasesAuto-check passed
Stmo
SAP/project-foxhound
Official
Manage Redash queries and dashboards on Mozilla's STMO (sql.telemetry.mozilla.org) using stmo-cli.
180 GitHub starsUsed in 2 repos~1.8k tokens
DatabasesAuto-check passed

Works with

Questions about SQL Portability

What does SQL Portability do?

Analyse whether a SQL query is portable across database implementations using sqlglot transpilation. SQL Portability is an agent skill from HL7/sql-on-fhir. Analyse whether a SQL query is portable across database implementations using sqlglot transpilation.

When should I use SQL Portability?

SQL Portability fits situations like: checking SQL compatibility; cross-database portability; dialect differences; reviewing SQL on FHIR ViewDefinition queries for implementation-specific issues.

How do I install SQL Portability in Claude Code?

Run `npx skills add HL7/sql-on-fhir --skill sql-portability -a claude-code`. Or copy the skill folder (.claude/skills/sql-portability in HL7/sql-on-fhir) into .claude/skills/sql-portability in your project. Claude Code loads it when a task matches its description.

How do I install SQL Portability in Codex?

Run `npx skills add HL7/sql-on-fhir --skill sql-portability -a codex`. Or copy the skill folder (.claude/skills/sql-portability in HL7/sql-on-fhir) into .agents/skills/sql-portability in your project. Codex loads it when a task matches its description.

Can I use SQL Portability 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 HL7/sql-on-fhir --skill sql-portability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sql-portability, .gemini/skills/sql-portability, .github/skills/sql-portability and .opencode/skills/sql-portability in your project.

What does SQL Portability need to run?

Going by SKILL.md and its folder, SQL Portability needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does SQL Portability access the network?

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

Is SQL Portability 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does SQL Portability use?

SQL Portability has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does SQL Portability use?

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

Skills that share tags, products or a category with SQL Portability: Imaging Data Commons (K-Dense-AI/scientific-agent-skills, 48k stars), Imaging Data Commons (majiayu000/claude-skill-registry, 666 stars), Evolving The Data Model (TriliumNext/Trilium, 38k stars) and Orchardcore Data Migration (OrchardCMS/OrchardCore, 8.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SQL Portability?

HL7 (a GitHub organization) maintains it in HL7/sql-on-fhir, which has 150 GitHub stars. The repository was last updated on October 6, 2026.

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

Install SQL Portability

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Imaging Data Commons

Imaging Data Commons

Evolving The Data Model

Orchardcore Data Migration

SQL Optimization Patterns

Stmo

Related

Questions about SQL Portability